swiss-public-transport-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.
This server publishes no instructions, or was last inspected before Glama recorded them.
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 |
|---|---|
| search_locationsA | Find Swiss train stations, bus stops, and other transport locations. Use this to:
Returns station IDs, coordinates, and relevance scores. |
| plan_journeyA | Plan a journey through Switzerland by train, bus, tram, boat, or cableway. Use this whenever someone wants to:
Returns real-time schedules with platform numbers, delays, transfers, and occupancy levels. Call multiple times with different legs to plan a full day itinerary visiting several places. |
| get_stationboardA | Check what's departing or arriving at a Swiss station right now. Use this to:
Returns a live board with times, platforms, destinations, and delay status. |
| get_booking_linkA | Get a direct link to buy tickets on sbb.ch for a specific journey. Use this when someone wants to:
Returns a ready-to-click URL that opens SBB's timetable with the search pre-filled. |
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 4 tools
All four tools serve clearly distinct purposes: searching locations, planning journeys, checking station boards, and generating booking links. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (get_booking_link, get_stationboard, plan_journey, search_locations) with underscores and no mixing of conventions.
Four tools is exactly right for a public transport MCP server—core functionalities (search, plan, live board, booking) are each covered by a single tool without unnecessary fragmentation or overlap.
The server covers the essential user journeys: finding stations, planning trips, checking real-time departures, and purchasing tickets. Minor gaps like disruptions alerts or fare details are absent but do not severely hinder common use cases.