
Connects Claude to datos.gob.es, Spain's official open data catalogue. Part of the Pipeworx gateway ecosystem, which routes requests to over 673 data sources. The server supports a streamable HTTP transport and includes an ask_pipeworx tool that handles plain English queries, automatically selecting the right API calls and parameters. Useful when you need Spanish government datasets, public sector information, or regional statistics without manually browsing the portal. You can add just this server or connect to the full Pipeworx gateway for access to their entire source collection. Runs remotely so no local setup required.
datos.gob.es MCP — Spanish open-data catalogue. Keyless.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
datasets(query?, page?, page_size?, theme?) — search datasetsdataset(id) — single datasetpublishers(limit?) — list publishersthemes(limit?) — list themes (DCAT classification)https://datos.gob.es/apidata/
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"datos-gob-es": {
"url": "https://gateway.pipeworx.io/datos-gob-es/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/datos-gob-es/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Datos Gob Es data" })
The gateway picks the right tool and fills the arguments automatically.
MIT