transcapi-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRANSCAPI_API_KEY | Yes | Required. Your TransCAPI API key. | |
| TRANSCAPI_BASE_URL | No | Optional. Defaults to https://api.transcapi.com. | https://api.transcapi.com |
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_placesA | Find towns, villages, postcodes (full or partial, e.g. "S1") and stops by name. Places sharing a name are ranked by size. Give lat/lon to sort by distance from there. |
| nearby_stopsB | Bus, tram and rail stops within |
| nearby_stationsA | Rail stations within |
| bus_departuresB | What is leaving (or, with board="arrivals" or "both", arriving at) a bus
stop. Tracked buses have an expected time and |
| rail_departuresA | Live trains leaving (or arriving at, with board="arrivals" or "both") a
station: expected times, platforms, cancellations and delay reasons from
National Rail, plus station messages. |
| train_serviceA | Every station one train calls at. For a train running today, each call has
live status, expected and actual times, and the platform at its next
station. Take |
| bus_serviceA | Every stop one bus journey calls at, the days it runs, and where the bus is
now if it is running. Take |
| live_busesA | Buses on the road within |
| disruptionsA | Planned works, incidents and line status: bus and tram across Great Britain,
plus Tube, DLR, Overground, Elizabeth line and London Trams. Filter by area
(lat/lon/radius), mode, operator or line. To ask what affects a particular
journey, pass its route as |
| plan_journeyA | Public transport journeys between two points, with walking, fares and live
positions of buses already running. |
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 10 tools
Each tool targets a clearly distinct query type: place search, nearby stops/stations, mode-specific departures, live buses, disruptions, journey/service details, and journey planning. The only potential overlaps (nearby_stops vs nearby_stations, bus_departures vs live_buses) are resolved by explicit output identifiers and descriptions.
All names use snake_case and are readable, with mostly noun-based resource names. Two tools use verb-led names (search_places, plan_journey), which is a minor deviation from the dominant noun-phrase pattern.
Ten tools is well-scoped for a public transport API, covering distinct query categories without redundancy. Each tool has a clear purpose and earns its place.
The surface covers search, nearby stops/stations, departures, live vehicles, disruptions, service details, and journey planning. Minor gaps exist, such as direct lookup by stop/station identifier and dedicated tram live departures, but most workflows are supported.