meta-data-mcp — Claude Code MCP server: open data on demand
One MCP server that picks the right open-data source for a query. Useful when you need a dataset fast instead of wiring up dozens of APIs yourself.
claude mcp add meta-data-mcp -- uvx meta-data-mcpWhat meta-data-mcp does
Under the hood meta-data-mcp bundles dozens of plugins, each wrapping a separate open-data API. Your model sees a single server: it calls opendata_providers_find with something like "FX rates" or "earthquakes", the server scores the query against an internal registry and returns ranked matches. Then the model activates a provider with opendata_providers_activate and calls its tools directly.
Plugins are not installable, runnable or addressable on their own — they load when the server starts. The server level exposes 13 meta tools; the bundled plugins contribute roughly 330 tools. You can also add new ones: opendata_plugins_draft builds and validates a YAML spec, and opendata_plugins_create runs the generator.
You need uv installed. Registration across clients goes through uv run meta-data-mcp setup, which detects your MCP clients and writes a single meta-data-mcp entry under mcpServers, backing up each existing config to <file>.bak. Without uv on the machine the client has nothing to launch.
What it helps with
- find a matching open dataset from a free-text query
- pull data from a government or science API without hunting for it
- register one server instead of many separate ones
- draft a new plugin for a source that isn't covered yet
- check which providers are active in the current session
Example prompts for the agent
- Find a data source for earthquakes near Lisbon
- Activate the FX rates provider and list its tools
- Draft a plugin YAML spec for a new open API
How to install meta-data-mcp
Platform CLI
claude mcp add meta-data-mcp -- uvx meta-data-mcpuvx runs the command named after the package; if the README names another one, use uvx --from meta-data-mcp <command>
Platform CLI
codex mcp add meta-data-mcp -- uvx meta-data-mcpuvx runs the command named after the package; if the README names another one, use uvx --from meta-data-mcp <command>
Config file
{
"mcpServers": {
"meta-data-mcp": {
"command": "uvx",
"args": [
"meta-data-mcp"
]
}
}
}uvx runs the command named after the package; if the README names another one, use uvx --from meta-data-mcp <command>
Config file
{
"servers": {
"meta-data-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"meta-data-mcp"
]
}
}
}uvx runs the command named after the package; if the README names another one, use uvx --from meta-data-mcp <command>
Platform CLI
gemini mcp add meta-data-mcp uvx meta-data-mcpuvx runs the command named after the package; if the README names another one, use uvx --from meta-data-mcp <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about meta-data-mcp
How do I install meta-data-mcp in Claude Code?
Run claude mcp add meta-data-mcp -- uvx meta-data-mcp. You need uv installed first.
What does meta-data-mcp do?
It is a single MCP server that routes requests to dozens of open-data APIs. The model searches for a source through the meta tools and activates it for the session.
Can I install the plugins separately?
No. Plugins are an implementation detail — they are not separately installable or runnable, and they load automatically when the server starts.
