Statfin Fi

What the Statfin Fi MCP server does

Statfin Fi MCP server exposes Statistics Finland’s official StatFin catalogue through the Model Context Protocol. The underlying source is the StatFin PxWeb API, which contains Finnish statistics on subjects including population, education, employment, consumer prices, housing, health, and national accounts.

The server supports three data-facing tools:

• subjects navigates the catalogue. An empty path returns the top-level subject folders, while a folder path returns its tables. Results distinguish folders from tables.
• table_meta describes one table’s dimensions and all valid values. Use it before constructing a detailed PxWeb request.
• query_table returns figures. It accepts a plain-English select mapping or a body containing a PxWeb query that is passed through.

Tables use paths such as vkour/15ig.px, with a folder and a four-character table identifier. Older, longer table paths are rewritten to the current format when encountered.

How it works

A typical workflow starts with subjects to locate a relevant table, followed by table_meta to learn how that table is organized. The agent can then call query_table with labels such as a measure or category instead of first discovering every Finnish dimension code. The server resolves the requested values against that table’s metadata.

Unspecified dimensions receive defaults where the table provides a defensible choice. The year uses the latest published value, eliminable dimensions can be aggregated, and explicit total values such as SSS, Total, or a table-specific open-ended range may be selected. The response includes selection_resolved, making those choices visible. If no safe total exists, the dimension is returned in full rather than being silently reduced.

A label matching multiple values returns all matching rows. Matches that are too broad—more than 20—are reported as such. For results of up to 60 cells, the response also provides figures, pairing values with dimension labels instead of leaving the caller to decode a flat json-stat2 array.

Setup and configuration

The gateway endpoint can be added to an MCP client with the URL https://gateway.pipeworx.io/statfin-fi/mcp. The gateway requires no account for the initial calls and adds shared Pipeworx tools alongside the pack’s three tools. A full Pipeworx gateway connection is also available at https://gateway.pipeworx.io/mcp.

Statfin Fi MCP server can instead run locally over stdio with the npm package @pipeworx/mcp-statfin-fi:

{
  "mcpServers": {
    "statfin-fi": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-statfin-fi"]
    }
  }
}

The local process handles MCP initialization, tool listing, and tool calls for this pack only. No environment variables, registration, or authentication key are specified. HTTP tool calls are also available through the gateway’s tool API.

Tools and capabilities

subjects is useful for discovering the approximately 135 top-level subject folders and the tables inside them. table_meta is required when a caller needs native dimension codes or wants to construct a direct body query. query_table supports both natural-language value selection and explicit PxWeb JSON, returning figures in json-stat2-compatible form.

Dimension codes remain native Finnish even when the English StatFin endpoint is used, and some labels may not be translated. Plain-English selection avoids needing to infer those codes. Direct-body callers should inspect metadata first.

Limitations and notes

The data source is Statistics Finland, also known as Tilastokeskus, and its published data is licensed under CC BY 4.0. The server itself is licensed under MIT. The gateway connection includes shared Pipeworx meta-tools, so its tool list is larger than the three Statfin-specific tools. The local stdio package does not include those shared routing tools.

The gateway and local package use the same StatFin source and tools, but only the gateway provides ask_pipeworx routing across other Pipeworx data packs. For exact values, review selection_resolved, especially when dimensions were omitted from a request. A direct body request also requires the correct Finnish dimension codes and valid table values.