Statbel Be
Statbel — Statistics Belgium (be.STAT / bestat) open data MCP.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
claude mcp add --transport http statbel-be 'https://gateway.pipeworx.io/statbel-be/mcp'
{
"mcpServers": {
"statbel-be": {
"type": "http",
"url": "https://gateway.pipeworx.io/statbel-be/mcp"
}
}
}
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
mcp-statbel-be
Statbel — Statistics Belgium (be.STAT / bestat) open data MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
Tools
| Tool | Description |
|---|---|
list_views | Browse/search Statbel (Statistics Belgium, be.STAT) saved statistical views. Each view is a pre-built table over a dataset and carries a single locale (nl/fr/de/en). Returns id, name, locale, dataSourceId and publish dates. Filter by case-insensitive substring of the view name (matches in any language). |
get_view | Metadata for one Statbel view by its id (a UUID, e.g. from list_views). Returns the view object: name, locale, dataSourceId (the underlying dataset), and publish/change dates. To get the dataset description in all available languages, pass the returned dataSourceId to get_dataset. |
list_datasets | Browse/search Statbel datasets (be.STAT "datasources"). Each dataset has a name code (e.g. "IM_EAF_HOUSE_SALES_IDX"), a descriptions map with one entry per supported language (nl/fr/de/en), a category id, supportedLocales, and last-update timestamps. Filter by case-insensitive substring matched against the dataset code and all-language descriptions. |
get_dataset | Multilingual metadata for one Statbel dataset by its id (a UUID, e.g. the dataSourceId from a view). Returns the dataset code name, the descriptions map (nl/fr/de/en text), supportedLocales, defaultLocale, category id and update dates. |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"statbel-be": {
"url": "https://gateway.pipeworx.io/statbel-be/mcp"
}
}
}
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/statbel-be/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 1683+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/list_views \
-H 'Content-Type: application/json' \
-d '{"query":"house prices"}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/list_views. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"statbel-be": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-statbel-be"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-statbel-be
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
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 Statbel Be data" })
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Questions fréquentes
Qu'est-ce que Statbel Be ?
Statbel — Statistics Belgium (be.STAT / bestat) open data MCP.
Comment installer Statbel Be ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http statbel-be 'https://gateway.pipeworx.io/statbel-be/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour Statbel Be ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
Statbel Be est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient Statbel Be ?
Il est publié par pipeworx-io. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.