Skip to main content
Databricks plays the same role as Snowflake: it supplies the business data that conversation analysis needs to be joined against.

​
What the agent gets

SQL execution against Unity Catalog, through Databricks SQL. Unity Catalog uses a three-level namespace, catalog.schema.table, so queries should be fully qualified.

​
Setup

The MCP server lives in your own workspace, so there is no shared endpoint.
1

Note your workspace MCP URL

It follows this shape:
Rippit accepts .databricks.com and .azuredatabricks.net hosts.
2

Create an OAuth application

Databricks does not let Rippit register itself. Create the OAuth application once at the account level, and add the redirect URI Rippit shows in the connect dialog, copied exactly.
3

Connect in Rippit

Paste the workspace MCP URL and the application’s client ID and secret.

​
Identity and scope

The connection uses the Databricks identity of the person who authorized it, so Unity Catalog grants apply as usual. An organization-wide connection shares that identity with everyone in your Rippit organization. As with Snowflake, a purpose-built service principal or user whose grants match what the agent should read is a better choice than an individual’s account.

​
Tools

Only execute_sql_read_only is enabled by default.
execute_sql runs any SQL, not just reads. Enabling it lets the agent modify and drop data in any catalog the connected identity can write to. If you only need analysis, leave it off.