# Ssb No [Health: Active]

**Category:** 🧮 Data Science Tools  
**Repository:** https://github.com/pipeworx-io/mcp-ssb-no  
**GitHub Stars:** 0  
**npm Downloads (last month):** 469  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/ssb-no

## Description
Statistics Norway (SSB) PxWebApi MCP.

## Tools
Capabilities this server exposes over MCP:

- **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" -> Popul…
- **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.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "ssb-no": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-ssb-no"]
  }
}
```

## Documentation

## What the Ssb No MCP server does

The Ssb No MCP server exposes Statistics Norway’s PxWebApi through MCP. It focuses on finding and querying SSB statistical tables rather than providing a general-purpose database interface. Agents can browse the subject hierarchy, inspect a table’s structure, and retrieve values from a selected table.

The pack has three primary tools:

- `subjects` lists the children of a node under `/table/`. An empty path starts at the root. Returned nodes include an ID, a type, and display text. Folder nodes use type `l`; table leaves use type `t`.
- `table_meta` returns the variables, dimensions, and valid values for a numeric SSB table ID.
- `query_table` sends a PxWeb query object to a numeric SSB table ID and returns the selected data.

## How it works

A typical workflow starts with `subjects`. Follow IDs such as `be` or `be05` to move through the subject tree until you find a table. The ID on a table leaf is the numeric identifier needed by the other tools; an example in the documentation is `07459`.

Next, call `table_meta` to learn which dimensions the table exposes and which values are accepted. Use that information to construct the body for `query_table`. Dimensions can be selected explicitly. If dimensions are omitted, PxWeb elimination rules may collapse them instead of returning every possible combination.

The hosted endpoint is available at `https://gateway.pipeworx.io/ssb-no/mcp`. Through that connection, the pack’s tools appear alongside shared Pipeworx meta-tools. `ask_pipeworx` can route a natural-language question across the wider Pipeworx catalog, while the standalone package exposes only the Ssb No tools.

## Setup and configuration

For a hosted connection, add the MCP URL to a compatible client’s server configuration. No environment variables are documented for either deployment method.

The local package runs through npm with `npx -y @pipeworx/mcp-ssb-no`. Configure it as a stdio MCP server by setting the command to `npx` and passing `-y` and `@pipeworx/mcp-ssb-no` as arguments. This local mode does not require a Pipeworx account or a gateway round trip.

Without an MCP client, hosted tools can also be called over HTTP. For example, `POST https://gateway.pipeworx.io/v1/tools/ssb_no_subjects` with a JSON body containing `{"path":""}` starts a subject-tree lookup.

## Tools and capabilities

The Ssb No MCP server supports subject discovery, table-schema inspection, and data retrieval from SSB PxWebApi tables. The gateway endpoint also includes Pipeworx-wide discovery and routing tools, but those are not part of the standalone package.

## Limitations and notes

The pack-specific tools require a numeric SSB table ID for metadata and data queries. A caller must use the table structure and valid values returned by `table_meta` to build a suitable PxWeb request. The Ssb No MCP server does not document write operations or tools outside the three SSB functions.

The hosted pack endpoint and the full Pipeworx gateway reach the same broader source catalog, but they differ in which tools are listed directly. The hosted pack endpoint includes shared meta-tools; the local package does not. The gateway’s exact tool scope can change, so its `initialize` response is authoritative.

_Full upstream README: https://allmcps.com/mcp/ssb-no/readme_