io.github.mohammad-abbasi-sh/autobahn-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Unofficial read-only MCP server for the German Autobahn via the official verkehr.autobahn.de API (no key, no login): roadworks, closures, warnings, truck/car parking areas and EV charging stations for one motorway at a time (e.g. "A1", "A100"). NOTE: the API's reststop, traffic and webcam services return empty arrays on every probed motorway right now (verified 2026-11-10), so they are not exposed as tools. Built by Mohammad Abbasi (mohammad-abbasi-sh) — https://almanibama.ir · https://mabbasi.ir — Germany MCP factory.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| autobahn_roadworksB | Roadworks on one German motorway. road: e.g. "A1" or "A100". limit: 1..50 (default 10). |
| autobahn_closuresB | Closures on one German motorway. road: e.g. "A1" or "A100". limit: 1..50 (default 10). |
| autobahn_warningsC | Warnings on one German motorway. road: e.g. "A100" or "A1". limit: 1..50 (default 10). |
| autobahn_parkingB | Truck/car parking areas on one German motorway, with capacities. road: e.g. "A1" or "A7". limit: 1..50 (default 10). |
| autobahn_ev_chargingB | EV charging stations on one German motorway. road: e.g. "A1" or "A7". limit: 1..50 (default 10). |
| autobahn_healthA | Check whether verkehr.autobahn.de is reachable right now. Returns status ok (HTTP 200), blocked (HTTP 403/429 — bot wall or rate limit) or error, plus the HTTP status and the probed URL. One polite request; it does not fetch any listings. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool maps to a single distinct data category on the Autobahn API: roadworks, closures, warnings, parking, EV charging, and a standalone health probe. There is no plausible way to confuse one with another, and the health tool is clearly separated as a non-listing diagnostic.
All six tools follow an identical pattern: the `autobahn_` prefix plus a snake_case domain noun (roadworks, closures, warnings, parking, ev_charging, health). The convention is uniform and predictable, and the shared parameter signature (road, limit) reinforces it.
Six tools is a tight, well-scoped set for a single-source road data server, with each tool earning its place as a separate endpoint. No redundant or speculative tools inflate the surface.
The surface covers the main Autobahn dataset categories (roadworks, closures, warnings, parking, EV charging) plus a connectivity check, which is solid lifecycle-free read coverage. Minor gaps remain: no tool to list valid road identifiers/reference data, and no webcam or general traffic-flow/charging-detail endpoint.