
Sbb Opendata Mcp
Pull Swiss Federal Railways (SBB) open datasets via OpenDataSoft through MCP while building mobility apps, dashboards, or travel features.
Overview
sbb-opendata-mcp is an MCP server for the Build phase that queries SBB Open Data via OpenDataSoft from your coding agent.
What is this MCP server?
- SBB Open Data exposed through OpenDataSoft for agent-queryable Swiss rail and mobility datasets.
- sbb-opendata-mcp v0.3.3, stdio MCP, PyPI with uvx launch pattern.
- Registry category Transport & Mobility—complements generic map APIs with operator-published Swiss rail open data.
- Repository github.com/malkreide/sbb-opendata-mcp for reproducible local MCP setup.
- Useful for indie travel planners, delay dashboards, and multimodal prototypes targeting Switzerland.
- Version 0.3.3 on PyPI identifier sbb-opendata-mcp
- Stdio transport, registryType pypi, runtimeHint uvx
- Publisher category Transport & Mobility
Community signal: 1 GitHub stars.
What problem does it solve?
Building Swiss rail or mobility features forces developers to hunt OpenDataSoft portals and hand-copy dataset fields into prompts instead of structured agent access.
Who is it for?
Indie developers building Switzerland-focused travel, commute, or logistics tools that need SBB-published open data in the agent loop.
Skip if: Real-time ticketing, payments, or non-SBB global transit APIs—open data integration only.
What do I get? / Deliverables
After registration, your agent can fetch SBB open datasets on demand while you implement integrations and mobility UX.
- Agent-accessible SBB Open Data via OpenDataSoft
- Integration-ready transport dataset queries during build
- Less manual portal browsing for Swiss mobility prototypes
Recommended MCP Servers
Journey fit
Canonical shelf is Build integrations because SBB open data is typically wired into product backends and agent tools during implementation, not only initial brainstorming. Integrations subphase matches OpenDataSoft-backed datasets consumed by APIs, maps, and agent assistants for transport and mobility features.
How it compares
SBB OpenDataSoft MCP bridge, not a browser automation skill for booking tickets.
Common Questions / FAQ
Who is sbb-opendata-mcp for?
Builders using MCP clients who implement Swiss mobility products and want SBB open datasets available as agent tools during integration work.
When should I use sbb-opendata-mcp?
Use it in Build integrations when prototyping or shipping features that consume SBB Open Data through OpenDataSoft rather than static CSV dumps.
How do I add sbb-opendata-mcp to my agent?
Configure stdio MCP with uvx running the sbb-opendata-mcp PyPI package v0.3.3 in Claude Code, Cursor, or Codex.