mcp-belgium

One MCP server for Belgian public APIs.

mcp-belgium is the public entry point. It exposes a single aggregated MCP server that bundles Belgian transport, official statistics, open data, addresses, weather, air quality, and geospatial services behind one install and one client config entry.

The package is also prepared for publication to the official MCP Registry under io.github.lacausecrypto/mcp-belgium.

Why use it

• one npm package
• one MCP server entry in your client config
• namespaced tools like irail_*, statbel_*, best_*, kmi_*, urban_*, and urbis_*
• built-in catalog tools, resources, and a prompt so the LLM can discover the right Belgian domain before calling tools
• explicit limitation surfaces when an upstream requires a key or has changed contract

Install

Run directly:

npx -y mcp-belgium

With pnpm:

pnpm dlx mcp-belgium

Global install:

pnpm add -g mcp-belgium
mcp-belgium

Default transport is stdio, which is what desktop MCP clients expect.

Claude Desktop

{
  "mcpServers": {
    "belgium": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-belgium"
      ],
      "env": {
        "LOG_LEVEL": "silent"
      }
    }
  }
}

Optional env vars:

• STIB_API_KEY: enables live STIB/MIVB tools
• CBEAPI_KEY: enables live KBO/BCE company registry tools
• MCP_TRANSPORT=http: runs the server over Streamable HTTP
• PORT_BELGIUM=3017: sets the HTTP port for the aggregated server

What the LLM gets

Alongside the domain tools, mcp-belgium exposes a discovery layer:

• belgium_catalog_overview
• belgium_list_domains
• belgium_describe_domain
• belgium://catalog
• belgium://catalog.json
• belgium://domain/{domain}
• belgium_capability_guide

That means the LLM can:

• inspect the Belgian domains available from this single MCP
• see which domains are live, limited, or key-gated
• understand what kind of data each domain provides
• pick the right namespaced tool without guessing

Main domains

... View full README on GitHub