Skip to main content
Connect Databricks to Athena so each member can browse catalogs and run SQL against your warehouses as their own Databricks identity, and ask Genie One or a Genie space from an agent. Unity Catalog ACLs apply unchanged, and no personal access tokens are shared.

How to connect Databricks and add a Genie space as an MCP server

  1. Open Integrations
  2. Connect Databricks
  3. Sign in to Databricks
  4. Allow access
  5. Open MCP Servers
  6. Add a Direct HTTP server
  7. Pick your Genie space
  8. Test Setup
Setup is two steps, done by two different people: your Databricks account administrator registers an OAuth app connection, then an Olympus workspace admin saves that app once for the whole workspace. Members can only connect after both are done.

​
Step 1: Register an OAuth app in Databricks (account admin)

  1. Open the Databricks Account Console:
  2. Settings → App connections → Add connection. Name it e.g. Athena.
  3. Redirect URLs: add:
    You can add multiple redirect URLs if you use more than one Athena environment.
  4. Scopes: all-apis and offline_access. The second one is required so Athena can refresh tokens without re-prompting members. Databricks documents the ai-gateway scope for Genie One. If Test Setup on a Genie One server says the token needs ai-gateway, add that scope here too, then add it under OAuth scopes in step 2.
  5. Create. Databricks shows the Client ID and Client Secret exactly once; copy both immediately.
  6. Copy your Account ID as well (top-right user menu in the Account Console). This is the account UUID, not the workspace org-id.

​
Step 2: Enable Databricks in Athena (workspace admin, once)

An Olympus workspace admin or owner must add this on the Athena side for the entire workspace before individual members can connect. Members cannot configure it themselves, and the connect option stays hidden until it’s saved. Open Workspace Settings → Integrations, expand Databricks (Direct OAuth), click Add app, and fill in: Toggle the app on and Save app. You can add more than one app, for example one per Databricks workspace, and members pick which one to authorize against. Secrets are encrypted at rest and never returned to the browser.

​
Step 3: Members connect (each user)

  1. Go to Integrations and click Databricks → Connect.
  2. Sign in to Databricks in the popup and grant the requested scopes.
  3. Athena creates a private catalog for you with a warehouse picker and SQL editor. Queries run as your Databricks identity.

​
Ask Genie One or a Genie space from an agent

Genie One answers across the data you can use in Databricks. A Genie space answers from that space only. Both run as each member’s own Databricks identity, through their Databricks connection.
  1. Open the agent’s MCP Servers and add a server.
  2. Set Connection to Direct HTTP.
  3. Under Athena connection, set Credential source to your Databricks connection, or to Each user’s own Databricks connection for a server colleagues will use too.
  4. In Genie, pick Genie One or a Genie space. The server URL fills in.
  5. Click Test Setup. Leave Headers empty.
Databricks turns off the Genie One Beta endpoint (/api/2.0/mcp/genie) on October 31, 2026. When a server that still uses it has your Databricks connection as its Credential source, a warning appears under Genie. Click Switch to Genie One to move it.
If you changed the app’s scopes, each member reconnects Databricks so the new scopes are on their token.

​
Troubleshooting

Tokens are per-user, encrypted at rest, and refreshed automatically. Unity Catalog governs what each member can query; Athena adds no access of its own.