{
  "markdown": "# mcp-asub-ax\n\nStatistics and Research Åland (ÅSUB) PxWeb MCP.\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| `subjects` | Browse the ÅSUB (Statistics Åland) PxWeb subject tree. Pass a sub-path like \"Statistik\" or \"Statistik/BE\" to list folders (type \"l\") and tables (type \"t\", id ends in \".px\"); omit path to list the top-level databases (Statistik, Utredning). |\n| `table_meta` | Fetch dimension definitions and valid values for an ÅSUB PxWeb table (.px file). Path must be the full table path ending in \".px\" (e.g. \"Statistik/BE/Befolkningsrörelsen/BE006.px\"). Returns dimension codes, labels, and the value lists needed to build a query_table body. |\n| `query_table` | POST a PxWeb selection query to an ÅSUB table and return the data as json-stat2. Path must end in \".px\"; body is a PxWeb query object with a \"query\" array of {code, selection: {filter, values}} entries plus {response: {format: \"json-stat2\"}}. Narrow each dimension's values to stay under PxWeb's per-response cell limit. |\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"asub-ax\": {\n      \"url\": \"https://gateway.pipeworx.io/asub-ax/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/asub-ax/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 Asub Ax 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": 3144,
  "sha": "6d00c7ee19fd561091e42d4c692048ac008b0beca3afd1cac435d5c5a28be2df",
  "repo_slug": "pipeworx-io/mcp-asub-ax",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_asub_ax_a1a2b5b5/readme"
}