Alkemi MCP vs Opendatasoft — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Alkemi MCP vs Opendatasoft
In-depth architectural comparison of the Alkemi MCP and Opendatasoft 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
Alkemi MCP
Data Platforms · Local stdio
Quality: 40/100 (Fair) | Auth: API Key required
Opendatasoft
Data Platforms · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Verdict Summary: Choose Alkemi MCP if you need specialized Data Platforms tools running via a local process. Choose Opendatasoft 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 Alkemi 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 (Freemium).
You have access to required keys: BEARER_TOKEN.
Primary tools included: Natural-language querying, Snowflake connectivity through Alkemi, Google BigQuery connectivity through Alkemi.
Search datasets on any Opendatasoft portal (default public.opendatasoft.com) by keyword, with optional sort and facet filters; returns dataset IDs, titles, and field summaries.
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).
Alkemi MCP is categorized under Data Platforms and uses a local stdio subprocess. In contrast, Opendatasoft belongs to Data Platforms using local stdio subprocess. Select Alkemi MCP when you need capabilities focused on data platforms and Opendatasoft when you require tools for data platforms.
Fetch schema and metadata for a single Opendatasoft dataset by dataset_id; returns field definitions, record count, and dataset description from the specified portal instance.
records
Query records from an Opendatasoft dataset with optional keyword search, ODSQL WHERE/SELECT/GROUP BY/ORDER BY clauses, pagination, and projection; returns matching rows as JSON.
facets
Retrieve distinct values and counts for a named facet field within an Opendatasoft dataset; useful for enumerating categories or filtering options before querying records.
instance_info
Fetch catalog-level metadata for an Opendatasoft portal instance (total dataset count, themes, languages); defaults to public.opendatasoft.com.