
Connects Claude to Statistics Norway's PxWebApi for querying official Norwegian statistics and demographic data. Exposes a single tool for fetching table metadata, which gives you variable definitions, dimensions, and valid values for any SSB table using its numeric ID. The gateway handles natural language queries through ask_pipeworx, so you can request Norwegian economic indicators, population stats, or labor market data without manually constructing API calls. Part of the larger Pipeworx ecosystem that bundles 673+ data sources behind one MCP gateway. Useful when you need authoritative Norwegian government data for analysis, reporting, or research without leaving your AI workflow.
Statistics Norway (SSB) PxWebApi MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
subjects | Navigate the subject tree. Pass a node id path under /table/ (default empty = root list of subjects). Each level returns child nodes ({id, type, text}); type "l" is a folder, "t" is a leaf table whose id is the numeric table id used by table_meta/query_table. e.g. path "" -> subjects, "be" -> Population, "be05" -> Population count tables. |
table_meta | Table definition (variables/dimensions and valid values). id is the numeric SSB table id, e.g. "07459". |
query_table | Pull data from a table. id is the numeric SSB table id; body is a PxWeb query object. Omitted dimensions with elimination collapse; otherwise select values per dimension. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"ssb-no": {
"url": "https://gateway.pipeworx.io/ssb-no/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/ssb-no/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 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
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 Ssb No data" })
The gateway picks the right tool and fills the arguments automatically.
MIT