Databricks Workspace

Live

OAUTH 2.0

ANALYTICS

Analytics

Connect to Databricks Workspace APIs using a Service Principal with OAuth 2.0 client credentials to manage clusters, jobs, notebooks, SQL, and more.

  • Acts as the user: Every tool call runs as the authorizing user. Access and audit trail stay intact.
  • Credentials stay vaulted: AES-256 encrypted, resolved at request time, never stored in LLM context.
  • Scoped before every call: Per-user permissions enforced automatically. 90-day audit trail included.
Databricks Workspace
agent · Acme Q3
Run
Cluster Get in Databricks Workspace
S
databricksworkspace_cluster_get
85ms
Databricks Workspace agent
Get details of a specific databricks cluster by cluster id..
Sources: Databricks Workspace
databricksworkspacemcp
1 tool call
18:29
Message Claude...

Databricks Workspace tools for AI agents

CALL ANY TOOL
12 tools covering cluster.
databricksworkspace_cluster_get
Get details of a specific databricks cluster by cluster id.
Get details of a specific databricks cluster by cluster id.
Parameters
Name
Type
Required
Description
cluster_id
string
Required
The unique identifier of the cluster.
databricksworkspace_cluster_start
Start a terminated databricks cluster by cluster id.
databricksworkspace_cluster_terminate
Terminate a databricks cluster by cluster id. the cluster wi
databricksworkspace_clusters_list
List all clusters in the databricks workspace.
databricksworkspace_information_schema_columns
List columns for a table using information_schema.columns. r
databricksworkspace_information_schema_schemata
List all schemas within a catalog using information_schema.s
databricksworkspace_information_schema_table_constraints
List primary key and foreign key constraints for tables in a
databricksworkspace_information_schema_tables
List tables and views in a schema using information_schema.t
databricksworkspace_job_get
Get details of a specific databricks job by job id.
databricksworkspace_job_run_now
Trigger an immediate run of a databricks job by job id.
databricksworkspace_job_runs_list
List all job runs in the databricks workspace, optionally fi
databricksworkspace_jobs_list
List all jobs in the databricks workspace.
Build your Agent
Same auth pattern across every framework.
Python · LlamaIndex
from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="databricksworkspace")

mcp = MultiServerMCPClient({
"databricksworkspace": {
"url": "https://mcp.scalekit.com/databricksworkspace",
"headers": {"Authorization": "Bearer " + token}
}
})
tools = await mcp.get_tools()
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "databricksworkspace" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/databricksworkspace
// Pass: Authorization: Bearer + token
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "databricksworkspace" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/databricksworkspace
// Pass: Authorization: Bearer + token
from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="databricksworkspace")
# Connect to MCP at https://mcp.scalekit.com/databricksworkspace
# Pass: Authorization: Bearer + token
Try these prompts
Paste any prompt into your agent to get started.
Get started
Copy the prompt
Copied
List all schemas within a catalog using INFORMATION_SCHEMA.SCHEMATA?
Copy the prompt
Copied
List PRIMARY KEY and FOREIGN KEY constraints for tables in a schema using INFORMATION_SCHEMA.TABLE_CONSTRAINTS?
Advanced
Copy the prompt
Copied
List all schemas within a Unity Catalog in the Databricks workspace?
Copy the prompt
Copied
Fetch a specific result chunk for a paginated SQL statement result?
SEE HOW AUTH WORKS
User authorises once. Every agent call after uses their token with scope enforcement.
1
Authorize
Your user connects
Databricks Workspace
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Databricks Workspace
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Databricks Workspace
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Databricks Workspace
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other connectors.
SALES
Deal intelligence agent
Combine Gong, Attio, and Slack signals to surface deal risks and next-best actions. Updated after every call.
ENGINEERING
Engineering standup agent
Aggregate GitHub and GitLab activity, link to Jira, and post a daily standup digest to Slack. No async updates.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought.
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.
// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
One connector today. Ten tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions

Does the agent access Databricks Workspace as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Databricks Workspace OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Databricks Workspace?
Yes. Pass a tool name filter to listScopedTools so the analytics agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Databricks Workspace.

What happens when a user revokes Databricks Workspace access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Does the service principal respect Unity Catalog permissions?
Yes. Cluster, job, and SQL calls run under the connected service principal's grants, with Unity Catalog ACLs intact. Scalekit vaults the OAuth credential and scope-checks each tool call on top.

Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""databricksworkspace"": {
""url"": ""https://mcp.scalekit.com/databricksworkspace"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.databricksworkspace]
url = ""https://mcp.scalekit.com/databricksworkspace""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""databricksworkspace"": {
""url"": ""https://mcp.scalekit.com/databricksworkspace"",
""type"": ""http""
}
}
}