Databricks
Register Ternary MCP as a Databricks MCP service with OAuth credentials that Ternary issues for your workspace.
Connect Databricks to Ternary as an MCP service, so agents in your Databricks workspace can use Ternary tools.
Databricks is supported, but it needs an OAuth client that Ternary creates for your workspace. Contact Ternary before you start.
Before you start
You need:
- An existing Ternary account
- Access to at least one Ternary tenant
- Permission to create Unity Catalog connections in your Databricks workspace
Step 1: Request credentials from Ternary
Contact Ternary Support or your Ternary account team and include:
- Your Databricks workspace URL, for example
https://adb-1234567890123456.7.azuredatabricks.net - The region where your Ternary tenant is hosted: US (
my.ternary.app) or EU (my.eu.ternary.app)
Ternary sends you a client ID for that workspace. If your Databricks form requires a client secret, Ternary sends that too. Each workspace needs its own client.
Step 2: Create the connection
In Databricks, open Unity Gateway, select MCPs, click + MCP, and choose Connect an existing MCP server. Choose a catalog and schema, click Create new connection, and choose OAuth User to Machine Per User with Manual Configuration.
Use the values for your region. If the form asks for a single MCP server URL instead of a host and base path, enter the host followed by /mcp.
| Setting | Value |
|---|---|
| Host | https://core-api.ternary.app |
| Port | 443 |
| Base path | /mcp |
| Client ID | The client ID from Ternary |
| Client secret | The client secret from Ternary, if required |
| Authorization endpoint | https://core-api.ternary.app/oauth/authorize |
| Token endpoint | https://auth.ternary.app/oauth/token |
| OAuth scope | openid profile email offline_access |
| Setting | Value |
|---|---|
| Host | https://core-api.eu.ternary.app |
| Port | 443 |
| Base path | /mcp |
| Client ID | The client ID from Ternary |
| Client secret | The client secret from Ternary, if required |
| Authorization endpoint | https://core-api.eu.ternary.app/oauth/authorize |
| Token endpoint | https://auth.ternary.app/oauth/token |
| OAuth scope | openid profile email offline_access |
The authorization endpoint is on the Ternary server, not on auth.ternary.app. Databricks cannot send the setting Ternary needs to issue an MCP token, so the Ternary server adds it before it sends you to sign in.
Step 3: Sign in
Click Create & load tools. Then, under Tools, click Login.
Your browser opens the Ternary sign-in page.
- Sign in with your existing Ternary credentials.
- Approve the access request.
- Return to Databricks and click Create MCP Service.
Each Databricks user signs in with their own Ternary account and sees only the tenants they can access in Ternary.
Step 4: Verify the connection
Add the Ternary MCP service to an agent and try:
Using Ternary, show last month's spend by provider.
Troubleshooting
The userinfo audience is not allowed
The authorization endpoint points at auth.ternary.app. Change it to the /oauth/authorize URL on the Ternary server for your region.
Callback URL mismatch
Ternary registered a different workspace URL. Contact Ternary with the exact workspace URL you use.
Sign-in fails
Make sure your Ternary user exists in the region you selected. The MCP connection does not create accounts.
See Troubleshooting Ternary MCP for shared issues.
Updated 4 days ago