InfraNode MCP Server

Most developer tooling work still happens through a UI a human drives. InfraNode MCP server moves it into the conversation instead. Keyless open data for 84 German cities: weather, air, transit, traffic. 38 read-only MCP tools.

The short version

German cities publish a lot of open data, but every source has its own format, fields and quirks, and several need portal registration. InfraNode normalizes ~20 categories, weather (DWD), air quality (UBA), public transit (incl. realtime departures), traffic, electricity price (SMARD), land values (BORIS), parking, charging, water levels, demographics, energy and more, for 84+ German cities behind one interface. No API key, no account. Every response uses one canonical { data, meta } envelope with per-record license and attribution. The same data is also exposed as an MCP server (12 lean read-only

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

The tools it exposes

The server publishes 7 tools. What each one is for:

• ChatGPT — ** add a connector with the URL https://mcp.infranode.dev/mcp
• Single — city servers** (e.g. Munich, Berlin) cover one city each
• Code — ** Apache-2.0 (see LICENSE)
• Data — ** the open data served through InfraNode keeps the licenses of its
• Group — Data types (endpoint keys)
• Discovery — list_cities, sources, compare (one resource across many cities), overview (one-call catalog + live snapshot)
• Mobility — transit, live stop departures (transit_departures tool), stations (catalog), station boards by EVA (station_board_departures/station_board_arrivals

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. InfraNode's toolset — ChatGPT, Single, Code and 4 more — is a fair guide to whether it matches your workflow. It is maintained by dev.infranode; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against InfraNode's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.