Skip to main content
Sidecar creates a managed SQL MCP connection from your existing Databricks integration. It uses the integration’s OAuth service principal and derives this endpoint:
Sidecar manages short-lived access tokens and OAuth renewal for Agent Console. You do not enter a separate MCP URL or PAT. Update the service-principal OAuth credentials through the Databricks integration.
The managed SQL MCP can execute writes allowed by the service principal. Restrict its Unity Catalog and warehouse permissions to the access agents need. MCP approval settings apply to the entire server.

Prerequisites

  • Account Admin permissions in Sidecar
  • A connected Databricks integration with a workspace host, OAuth client ID, and client secret
  • The service principal assigned to the workspace with Databricks SQL access
  • Permission to use the managed SQL MCP and an eligible SQL warehouse
  • Unity Catalog USE CATALOG, USE SCHEMA, and SELECT grants on the data agents should read
The workspace host must be the workspace hostname, not the account-console hostname. Follow the integration guide for the service principal and base grants. Consult Databricks MCP documentation for workspace availability and provider permissions.

Configure network access

Sidecar’s provisioning and health checks connect from 44.236.246.98/32. Agent Console connects directly from Anthropic, whose outbound IPv4 range is currently 160.79.104.0/21. Allow both in any Databricks workspace IP access list that applies to the service principal. Confirm Anthropic’s current outbound addresses before configuring access. A SQL warehouse connection test from Sidecar does not establish runtime MCP access from Anthropic.

Confirm the managed connection

  1. In Integrations → Databricks → Connection, save the integration’s OAuth credentials.
  2. Open the MCP tab. Sidecar normally creates the managed SQL MCP within two minutes.
  3. Review the status and discovered tools. If Setup is taking longer than expected appears, click Check again.
  4. Open Integrations → MCP Servers and confirm the Databricks row.
  5. Confirm the agent grant and job selection.
The managed MCP selects its SQL warehouse automatically. That warehouse can differ from the HTTP Path used by the warehouse integration. Check the warehouse used by the MCP when investigating permission errors.
Do not replace the native managed credential with a PAT. Use the integration’s Connection tab to change its OAuth credentials or workspace host. Authenticated Check now checks discover tools with the service-principal identity; they do not verify every table’s permissions.

Verify Agent Console access

Start a new manual run after confirming the grant and job selection. Ask the agent to use the Databricks MCP server for these read operations:
Replace the table placeholders with an existing table the service principal may read. In the run transcript, confirm successful MCP tool calls and the expected identity and data scope. Complete any required approval. An empty table can return zero rows successfully. See runtime verification.

Additional custom endpoints

For another Databricks MCP capability, use the exact endpoint and permissions from the provider’s documentation. You can register it as a custom server only if it accepts the custom connector’s static bearer authentication and Streamable HTTP transport. The custom connector does not perform OAuth refresh. If the endpoint requires OAuth, use a supported native connector or a compatible gateway. Follow the provider’s authentication requirements rather than assuming a PAT works for every Databricks-hosted MCP endpoint.

Troubleshooting

Save the OAuth Databricks integration and allow up to two minutes for setup. Click Check again on the MCP tab if setup is taking longer than expected. Contact support if the row remains missing; include the integration name and setup timestamp, without credentials.
Read the status detail. Check service-principal assignment, OAuth credential validity, managed SQL MCP permissions, and SQL warehouse access. Update credentials on the Connection tab and select Check now after correcting permissions.
Confirm the grant and job selection, then start a new run. Check workspace access rules for Anthropic’s outbound addresses, the warehouse selected by MCP, and Unity Catalog permissions on the exact table.