Use Databricks MCP servers with external MCP clients

This page shows you how to connect to Databricks-managed MCP servers from popular external MCP clients like Cursor and Claude Desktop.

Prerequisites

• Generate a personal access token (PAT) from your Databricks workspace. See Databricks personal access token authentication.
• Ensure you are using a Databricks-managed MCP server. Custom MCP servers hosted on Databricks Apps do not support external clients.

Cursor

To use Databricks-managed MCP servers in Cursor, add the following configuration to your Cursor settings.

The example shows UC Functions, but you can adapt it for any managed MCP server URL path:

JSON

{
  "mcpServers": {
    "uc-function-mcp": {
      "type": "streamable-http",
      "url": "https://<your-workspace-hostname>/api/2.0/mcp/functions/{catalog_name}/{schema_name}",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      },
      "note": "Databricks UC function"
    }
  }
}

Claude Desktop

To use Databricks-managed MCP servers in Claude Desktop using mcp-remote, add the following configuration to your claude_desktop_config.json file.

The example shows UC Functions, but you can adapt it for any managed MCP server URL path:

JSON

{
  "mcpServers": {
    "uc-function-mcp": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://<your-workspace-hostname>/api/2.0/mcp/functions/{catalog_name}/{schema_name}",
        "--header",
        "Authorization: Bearer <YOUR_TOKEN>"
      ]
    }
  }
}

The configuration file can be found in the following locations by default:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

After updating the configuration, restart Claude Desktop for the changes to take effect.