SBB Open Data via OpenDataSoft
Most cloud and infrastructure work still happens through a UI a human drives. Sbb MCP server moves it into the conversation instead. SBB Open Data via OpenDataSoft.
🇨🇭 Part of the Swiss Public Data MCP Portfolio
The SBB Open Data portal speaks the OpenDataSoft REST API (v2.1). This server translates it into clean Markdown and JSON for the AI model, and adds MCP structuredContent alongside the human-readable text so programmatic clients can consume the underlying records without re-parsing. The server is model-agnostic and works with any MCP-compatible client.
The server publishes 11 tools. What each one is for:
sbb_get_passenger_frequency — Boardings/alightings by station and year (daily avg.)sbb_get_rail_disruptions — Live rail traffic messagessbb_get_infrastructure_construction_projects — Infrastructure construction (stations, lines)sbb_get_real_estate_projects — SBB real estate development projectssbb_get_trains_per_segment — Train counts per route segment (SBB, BLS, SOB …)sbb_get_platform_data — Platform data (length, type, area)sbb_get_rolling_stock — Rolling stock (capacity, year built)sbb_compare_stations — Compare up to 10 stations (multi-dataset)sbb_search_stations — Search stops (Swiss DiDok register, all CH)sbb_list_datasets — List all ~89 SBB open datasetsDemo — The Demo tool exposed by this serverBecause 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.
Configuration is passed through the environment: MCP_HOST, MCP_ALLOWED_HOSTS, MCP_ALLOWED_ORIGINS. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the cloud and infrastructure 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. Sbb's toolset — sbb_get_passenger_frequency, sbb_get_rail_disruptions, sbb_get_infrastructure_construction_projects and 8 more — is a fair guide to whether it matches your workflow. It is maintained by malkreide; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Sbb's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| sbb_get_passenger_frequency | Boardings/alightings by station and year (daily avg.) |
| sbb_get_rail_disruptions | Live rail traffic messages |
| sbb_get_infrastructure_construction_projects | Infrastructure construction (stations, lines) |
| sbb_get_real_estate_projects | SBB real estate development projects |
| sbb_get_trains_per_segment | Train counts per route segment (SBB, BLS, SOB …) |
| sbb_get_platform_data | Platform data (length, type, area) |
| sbb_get_rolling_stock | Rolling stock (capacity, year built) |
| sbb_compare_stations | Compare up to 10 stations (multi-dataset) |
| sbb_search_stations | Search stops (Swiss DiDok register, all CH) |
| sbb_list_datasets | List all ~89 SBB open datasets |
| Demo | The Demo tool exposed by this server. |
{
"mcpServers": {
"sbb-opendata": {
"command": "uvx",
"args": ["sbb-opendata-mcp"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MCP_HOST | Endpoint or connection string the server talks to. | Optional |
| MCP_ALLOWED_HOSTS | Endpoint or connection string the server talks to. | Optional |
| MCP_ALLOWED_ORIGINS | Configuration value read at startup. | Optional |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.