Stadiq MCP server

Five read-only tools over the Stadiq API, so an assistant can answer what is happening around an address without you writing the fetch call.

Last updated 19 August 2026.

Contents

Set it up

  1. Get a key

    Create a key on the Get started page. The free developer tier works.

  2. Check the key

    Run one request with it before you wire it into a client. Then an auth error later points at the wiring.

    Terminal
    curl -s -H "Authorization: Bearer sq_live_…" \
      "https://stadiq.app/api/v1/briefing?lat=51.2194&lng=4.4025"
  3. Add the server to your client

    In claude_desktop_config.json for Claude Desktop, or the MCP settings of Cursor or any other client. Nothing to install first: npx -y fetches the package on first run. Treat the key like a password: keep it in an environment variable or a local config file, never in a shared repository or a screenshot. If it leaks, revoke it in the dashboard (account menu, API en sleutels) and create a new one; the old key stops working at once.

    MCP configuration
    {
      "mcpServers": {
        "stadiq": {
          "command": "npx",
          "args": ["-y", "stadiq-mcp"],
          "env": { "STADIQ_API_KEY": "sq_live_…" }
        }
      }
    }
  4. Ask a question

    For example: “What road works are running near Groenplaats in Antwerp?” The assistant calls a tool and reads the JSON.

    Tool call and part of the result, illustrative values
    stadiq_disruptions { "lat": 51.2194, "lng": 4.4025 }
    
    "summary": {
      "activeWorks": 3,
      "plannedWorks": 5,
      "upcomingWorks14d": 1,
      "transitDisruptions": 2
    }

The five tools

stadiq_locations
The locations on the account behind the key, with ids and coordinates. No arguments. Call it first if you want to use locationId.
stadiq_disruptions
Road works within 2 km of a point and transit disruptions affecting it, with how many works are active, planned or imminent.
stadiq_air_quality
Latest NO₂ and PM reading from the nearest station, compared with WHO and EU limits, and whether the point is inside the Antwerp low-emission zone. Measured values only.
stadiq_briefing
The risk level and key facts, including the best and worst windows in the next 24 hours.
stadiq_history
GIPOD works and occupations our daily archive captured around a point or address in and around Antwerp, with every change to their start, end or status, and the days the archive missed.

The others take either locationId or both lat and lng; stadiq_history also accepts an address. The coordinates are bounded in the tool schema to the service area (latitude 50.6 to 51.55, longitude 2.5 to 5.95), so a model that invents a Paris coordinate is stopped by the schema, not by a round trip.

All five are annotated read-only, non-destructive and idempotent. The server holds no state and every tool is a GET underneath. It can spend your API quota and nothing else.

Environment variables

STADIQ_API_KEY
Required. Without it the server refuses to call anything and says so, rather than returning an empty result.
STADIQ_BASE_URL
Optional, defaults to https://stadiq.app.

What the tools return

The API's JSON, passed through as text and as structured content. It is deterministic: the same coordinates return the same computed numbers. No language model sits between the sources and the tool output.

Errors are passed through. A bad key, an exhausted quota or a coordinate outside Flanders surfaces the API's own message. Response shapes and error codes are in the API reference.

Alternatives

When mcp-belgium is the better choice

mcp-belgium is free, MIT-licensed and wraps many Belgian public APIs: iRail, STIB/MIVB, Infrabel, Statbel, KMI, IRCELINE, the KBO register and more. Use it for national breadth and raw access without a key.

Use Stadiq when you want the sources joined: works, transit and air quality resolved to one address, with results that cannot reach that address filtered out. The De Lijn and IRCELINE guides show why that is more work than it looks. The two can run side by side.