Databricks Unity Catalog Server

Step 1: Add the following configuration to .cursor/mcp.json:

{
  "mcpServers": {
    "databricks": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "DATABRICKS_HOST",
        "-e",
        "DATABRICKS_TOKEN",
        "ghcr.io/revodatanl/databricks-mcp-server:latest"
      ],
      "env": {
        "DATABRICKS_HOST": "${env:DATABRICKS_HOST}",
        "DATABRICKS_TOKEN": "${env:DATABRICKS_TOKEN}"
      }
    }
  }
}

Note: You can either use environment variable references (${env:VARIABLE}) or hardcode the values as strings directly in the configuration.

Step 2: Create a .env file in your project root with your credentials:

DATABRICKS_HOST=your-workspace-url
DATABRICKS_TOKEN=your-access-token

Step 3: Restart Cursor to load the MCP server.

Step 4: Use the cursor rules to enhance your Databricks development workflow.

Learn more about MCP in Cursor

Step 1: Add the following configuration to .continue/mcpServers/databricks-mcp.yaml:

name: databricks_mcp_server
version: 0.1.3
schema: v1
mcpServers:
  - name: databricks_mcp_server
    command: docker
    args:
      - run
      - -i
      - --rm
      - -e
      - DATABRICKS_HOST=${{ inputs.DATABRICKS_HOST }}
      - -e
      - DATABRICKS_TOKEN=${{ inputs.DATABRICKS_TOKEN }}
      - ghcr.io/revodatanl/databricks-mcp-server:latest

Step 2: Set your credentials either:

• On the Continue.dev website (recommended for security)

• Or in a .env file in your project root:

  DATABRICKS_HOST=your-workspace-url
  DATABRICKS_TOKEN=your-access-token
  

Step 3: Restart your editor to load the MCP server.

Step 4: Use the Continue.dev rules to enhance your Databricks development workflow.

Learn more about MCP in Continue.dev