mcpField
D
Datagov Ie

Datagov Ie

Remote
pipeworx.ioLegal & Government0Updated 4d ago

About Datagov Ie

Datagov Ie is an MCP server for exploring Ireland’s data.gov.ie open-data catalogue. It supports dataset discovery and retrieval of tabular records, alongside publisher and topic listings.

Key features

  1. 01Search dataset catalogue
  2. 02Retrieve dataset details and resources
  3. 03Query active datastore tables
  4. 04List publishing organizations
  5. 05List thematic groups

Use cases

  1. 01Find Irish government datasets by topic
  2. 02Read rows from queryable resources
  3. 03Identify publishers and data categories

MCP support

Exposes data.gov.ie catalogue search, dataset details, datastore queries, organization listings, and group listings 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-ie/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-ie

data.gov.ie MCP — Ireland's 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 Ireland's national open-data catalogue (data.gov.ie, CKAN package_search). Returns matching datasets from government departments, state agencies, and local councils, with titles/descriptions and their resources (English).
dataset_detailsFull dataset record by id or slug (CKAN package_show), including its resources. Each resource has a download "url" (often PDF/CSV/XLSX) and a "datastore_active" flag; resources with datastore_active=true can be read row-by-row via datastore_query using the resource "id".
datastore_queryRead actual table rows from a resource via CKAN datastore_search. Works only for resources with datastore_active=true (get the resource_id from dataset_details).
list_organizationsList publishing organizations (government departments, state agencies, county/city councils) on data.gov.ie (CKAN organization_list).
list_groupsList thematic groups/categories on data.gov.ie (CKAN group_list).

Quick Start

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

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

tools/list at https://gateway.pipeworx.io/datagov-ie/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_ie_search_datasets \
  -H 'Content-Type: application/json' \
  -d '{"query":"housing"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/datagov_ie_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-ie": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-datagov-ie"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-datagov-ie

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 Ie 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.