Metabase MCP vs CorpusIQ — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Metabase MCP vs CorpusIQ
In-depth architectural comparison of the Metabase MCP and CorpusIQ 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
Metabase MCP
Data Platforms · Local stdio
Quality: 53/100 (Good) | Auth: API Key required
CorpusIQ
Data Platforms · Remote HTTP/SSE
Quality: 75/100 (Great) | Auth: OAuth 2.0
Verdict Summary: Choose Metabase MCP if you need specialized Data Platforms tools running via a local process. Choose CorpusIQ if your workspace requires Data Platforms integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Metabase 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 (Free / Open Source).
You have access to required keys: METABASE_URL, METABASE_API_KEY.
Primary tools included: Metabase API-key authentication, Read, write, and full server modes, SELECT-only SQL guardrails.
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.
65+ MCP tools for business operations: ecommerce, finance, marketing, and analytics data through one streamable-HTTP endpoint. Built for operators.
Category & Scope
Tools & Capabilities Breakdown
Metabase MCP Tools (6)
Metabase API-key authentication
Read, write, and full server modes
SELECT-only SQL guardrails
Batch and chained workflow execution
Tiered rate limiting and audit logging
Optional Anthropic-powered analysis
CorpusIQ Tools (6)
65+ listed MCP tools
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).
Metabase MCP is categorized under Data Platforms and uses a local stdio subprocess. In contrast, CorpusIQ belongs to Data Platforms using remote streaming HTTP/SSE transport. Select Metabase MCP when you need capabilities focused on data platforms and CorpusIQ when you require tools for data platforms.