In-depth architectural comparison of the Databricks Genie MCP and Metabase MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Databricks Genie MCP
Data Platforms · Local stdio
Quality: 36/100 (Fair) | Auth: API Key required
Metabase MCP
Data Platforms · Local stdio
Quality: 55/100 (Good) | Auth: API Key required
Verdict Summary: Choose Databricks Genie MCP if you need specialized Data Platforms tools running via a local process. Choose Metabase MCP if your workspace requires Data Platforms integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Databricks Genie MCP when:
You need dedicated capabilities in the Data Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: DATABRICKS_HOST, DATABRICKS_TOKEN.
Primary tools included: List Genie spaces (manual configuration required), Fetch Genie space metadata (title, description), Start new Genie conversations with natural language input.
A server that connects to the Databricks Genie API, allowing LLMs to ask natural language questions, run SQL queries, and interact with Databricks conversational agents.
MCP server connecting Claude to Metabase with 28 tools for natural language data analysis, dashboard management, SQL queries, and automated insights. Features SQL guardrails, rate limiting, and audit logging.
Category & Scope
Tools & Capabilities Breakdown
Databricks Genie MCP Tools (5)
List Genie spaces (manual configuration required)
Fetch Genie space metadata (title, description)
Start new Genie conversations with natural language input
Follow up on existing Genie conversations
Retrieve SQL queries and structured result tables
Metabase MCP Tools (6)
Metabase API-key authentication
Read, write, and full server modes
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Databricks Genie MCP is categorized under Data Platforms and uses a local stdio subprocess. In contrast, Metabase MCP belongs to Data Platforms using local stdio subprocess. Select Databricks Genie MCP when you need capabilities focused on data platforms and Metabase MCP when you require tools for data platforms.