BlueConic's Model Context Protocol (MCP) server is available on the Databricks Marketplace as a Connect Provider listing. This lets AI agents and workflows running in Databricks connect directly to a BlueConic tenant to query and act on customer data.
Why
AI agents are only as useful as the context they can reach, and for most brands that context — real-time customer profiles, segments, behavioral signals — lives in BlueConic’s CDP, not in the data warehouse. Databricks is where more of those same brands run their data and AI workloads. Connecting the two today means custom pipelines and stale exports. The BlueConic MCP server removes that gap, letting AI agents and workflows in Databricks query and act on BlueConic customer data directly, and bringing that data into Databricks AI workflows without a separate integration to build and maintain.
Example Use cases
Data enrichment: enrich Databricks Delta tables directly with BlueConic profile data and vice versa — segments, preferences, engagement history — without standing up a custom ETL pipeline to keep it fresh.
Model training: with BlueConic profile data extending what’s already in Databricks, teams can train more effective models — propensity, churn, lifetime value, personalization — on a richer, unified feature set.
Actionable insights: analyze BlueConic domain objects — segments, churn risk, likelihood to buy — alongside Databricks data to validate and refine those metrics against deeper, cross-platform signal.
Finding the listing
Search the Databricks Marketplace for "BlueConic" and install the BlueConic MCP listing into your workspace: https://dbc-9550db14-bba0.cloud.databricks.com/marketplace/consumer/listings/5911dad1-5295-417f-9f6c-e72b8666c833?o=1180462777935703
Connect Databricks with BlueConic
Authorize the Databricks MCP connection as a BlueConic application, using an OAuth2 client credentials setup scoped to specific read and write permissions and a configured "run as user."
For all details on how to set this up in BlueConic, see BlueConic Model Context Protocol (MCP).
To set this up, you'll need:
Your BlueConic tenant's MCP endpoint: https://{your-tenant}.blueconic.net/mcp
OAuth2 client credentials (Client ID and Client Secret) for an application scoped to the read and write permissions you want to expose