Use Databricks from Claude
Add the Databricks connection to a Space that runs Claude, then use it from every channel in that Space.
Connect Databricks once, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
Add the Databricks connection to a Space that runs Claude, then use it from every channel in that Space.
Add the Databricks connection to a Space that runs Codex, then use it from every channel in that Space.
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
Databricks runs the jobs, clusters, apps, and access controls behind a team's data and AI workloads, reachable through its REST APIs. In a type.com Space, a platform or data engineering team can ask Claude to add someone to a security group, spin up a new Databricks app, or deploy and remove apps without switching into the Databricks console.
Connect Databricks once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Add a user or group to a Databricks security group so the right people get access without manual console clicks.
Add the data-science group as a member of our prod-readers security group in Databricks.
Create a Databricks app for a new internal tool and then deploy it straight from a workspace path.
Create a new Databricks app called usage-dashboard and deploy it from the latest workspace source.
Remove an app or a custom LLM agent that is no longer needed, along with its associated data.
Delete the Databricks app named old-reporting-tool and confirm the service principal is removed too.
Grants a user or group membership in a Databricks security group for access control.
Removes a custom LLM agent built with Agent Bricks, along with its checkpoints and associated data.
Creates a new Databricks app with a unique name, for hosting a secure data or AI application on the serverless platform.
Removes an app and its provisioned service principal from the workspace.
Deploys an app from a workspace source path, provisioning the compute it needs to run.
Databricks provides REST APIs, SDKs, CLI, Terraform provider, SQL APIs, model serving, Unity Catalog, jobs, clusters, warehouses, notebooks, files, secrets, and account-management surfaces for data and AI platforms. Integrations typically use workspace host plus token or OAuth credentials.
Yes. Once a Databricks connection is shared with a Space, Claude can create, deploy, or remove apps and manage security group membership in a thread.
Databricks supports OAuth or a personal access token. An admin sets this up once on the connection and controls which Spaces can use it.
Yes. You can set up a type.com automation that redeploys or checks on a Databricks app at a set interval, posting the outcome to a channel.
Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.
Ip2LocationConnect Ip2Location to Claude in type.com to geolocate IP addresses, check credits, and investigate hosted domains in a thread.
Connect IP2Location.io to Claude in type.com to geolocate IPs, pull WHOIS records, and list hosted domains in one thread.
Ipdata.coConnect Ipdata.co to Claude in type.com to pull IP geolocation, ASN, carrier, and threat details from a shared thread.
Ipinfo.ioConnect Ipinfo.io to Claude in type.com to batch lookup IPs, find abuse contacts, and check carrier or city data in a thread.