mcpField
D
Datagov Uk

Datagov Uk

Remote
pipeworx.ioLegal & Government0Updated 4d ago

About Datagov Uk

Datagov Uk is an MCP server for searching the UK’s data.gov.uk open-data catalogue. It retrieves dataset and publisher details, with downloadable file resources rather than queryable datastore tables.

Key features

  1. 01Search dataset catalogue
  2. 02Retrieve dataset details and file resources
  3. 03List publishing organizations
  4. 04Retrieve organization details

Use cases

  1. 01Find UK government datasets by topic
  2. 02Inspect downloadable dataset files and formats
  3. 03Review a publisher’s profile and datasets

MCP support

Exposes data.gov.uk dataset search, dataset details, organization listings, and organization details as MCP tools. It can run locally over stdio or connect through the Pipeworx gateway.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://gateway.pipeworx.io/datagov-uk/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

mcp-datagov-uk

data.gov.uk MCP — UK national open-data portal (CKAN API).

Part of Pipeworx — an MCP gateway connecting AI agents to 1878+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

ToolDescription
search_datasetsSearch the data.gov.uk catalogue (CKAN package_search) across 57k+ UK government open datasets. Returns matching datasets with titles, descriptions, publishing organization, and resources. Content is English. Pass an empty query to browse everything by relevance/sort.
dataset_detailsFull dataset record by id or slug (CKAN package_show), including its resources. Each resource exposes a downloadable file: read "url" (the download link), "format" (CSV/XLSX/ZIP/etc.), and "name". data.gov.uk resources are files, not queryable datastore tables.
list_organizationsList publishing organizations on data.gov.uk (CKAN organization_list) — UK government departments, agencies, councils, NHS bodies, ONS, etc. Use a returned org "name" as fq="organization:" in search_datasets to filter to that publisher.
organization_detailsFull details for one publishing organization (CKAN organization_show): display name, description, dataset count, and (optionally) a sample of its datasets. Use to learn what a given UK publisher releases.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "datagov-uk": {
      "url": "https://gateway.pipeworx.io/datagov-uk/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/datagov-uk/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 1878+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/datagov_uk_search_datasets \
  -H 'Content-Type: application/json' \
  -d '{"query":"air quality"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/datagov_uk_search_datasets. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "datagov-uk": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-datagov-uk"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-datagov-uk

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

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 Datagov Uk data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.