mcpField
C
Cso Ie

Cso Ie

Remote
pipeworx.ioLegal & Government0Updated 5d ago

About Cso Ie

Cso Ie is an MCP server for Ireland’s Central Statistics Office PxStat data, aimed at users exploring and retrieving statistics. It supports catalog search, table metadata, full JSON-stat data, and filtered slices, with gateway or local stdio setup.

Key features

  1. 01Search the CSO statistics catalog
  2. 02Inspect dimensions and category codes
  3. 03Read JSON-stat 2.0 datasets
  4. 04Filter data by dimension values

Use cases

  1. 01Find Irish statistics tables and update dates
  2. 02Inspect table dimensions and categories
  3. 03Retrieve filtered data from large tables

MCP support

It exposes tools for searching CSO PxStat datasets, inspecting metadata, and retrieving full or filtered data to MCP clients. It can connect through the Pipeworx gateway or run locally over stdio.

Configuration

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

Endpointhttps://gateway.pipeworx.io/cso-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-cso-ie

Ireland Central Statistics Office (CSO) PxStat MCP.

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

Tools

ToolDescription
list_datasetsSearch the CSO catalog of ~12,600 Irish statistics tables. Returns matching tables with their matrix code (e.g. "CPM01"), label, dimensions, and last-updated date. The full catalog is large, so always pass a keyword query to narrow it.
dataset_metadataGet the structure of one CSO table by matrix code: its dimensions, the category codes + human labels for each dimension, size, and last-updated date. Use this to discover valid dimension codes before calling get_dataset with filters.
get_datasetRead a full CSO table as JSON-stat 2.0 (dimensions + flat value array). Some tables are large (the CPI table is ~60k values); use dataset_metadata first to gauge size, or use query_dataset to fetch a filtered slice instead.
query_datasetRead a FILTERED slice of a CSO table via JSON-RPC. Pass a map of dimension code -> array of category index values to keep (get the dimension codes and category index values from dataset_metadata). Returns JSON-stat 2.0 covering only the selected cells — far smaller than get_dataset.

Quick Start

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

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

tools/list at https://gateway.pipeworx.io/cso-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 1875+ 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/cso_ie_list_datasets \
  -H 'Content-Type: application/json' \
  -d '{"query":"consumer price"}'

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

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-cso-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 Cso 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.