{
  "markdown": "# mcp-datacube-sk\n\nDATAcube — Statistical Office of the Slovak Republic (data.statistics.sk).\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Tools\n\n| Tool | Description |\n|------|-------------|\n| `list_datasets` | Browse / search the DATAcube collection of Slovak statistical cubes. Filter by case-insensitive substring of the English label. Returns each matching cube's code (use it as `cube` in the other tools), label, last update date, and its ordered list of dimension codes. |\n| `dataset_dimensions` | List the dimensions of one cube, in path order, with each dimension's valid value codes and labels. Selections in get_data are positional and must follow this dimension order. Get the cube code from list_datasets. |\n| `get_data` | Pull data for a cube as JSON-stat. Provide one selection per dimension, in the dimension order returned by dataset_dimensions. Each selection is either a single value code, a comma-separated list of codes (e.g. \"SEX_M,SEX_F\"), or the literal \"all\" for every value of that dimension. The number of selections must equal the cube's dimension count. Output is JSON-stat: `value` is the flat data array, `dimension`/`size`/`id` describe its shape. |\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"datacube-sk\": {\n      \"url\": \"https://gateway.pipeworx.io/datacube-sk/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/datacube-sk/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Datacube Sk data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 3294,
  "sha": "0464968e20bcbacb74960ee06627cff5aa0a17299efb3167df27c727ee71b750",
  "repo_slug": "pipeworx-io/mcp-datacube-sk",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_datacube_sk_76243114/readme"
}