otp-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OTP_BASE_URL | No | URL of the OpenTripPlanner server. | http://otp:8080 |
| MCP_AUTH_TOKEN | No | Bearer token for authenticating HTTP requests to the MCP server. |
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 | {} |
| resources | {} |
| extensions | {
"io.modelcontextprotocol/ui": {
"mimeTypes": [
"text/html;profile=mcp-app"
]
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| plan_journeyA | Plan a public-transit (rail/subway) journey using a self-hosted OpenTripPlanner instance (self-hosted OTP (Kanto rail/subway)). 'from' and 'to' are each a station name (e.g. "新宿") or a "lat,lon" coordinate. Returns ranked itineraries with per-leg lines (line name, stations, minutes), departure/arrival times, and transfer count. Accurate within the covered area (Kanto); returns no route for places outside coverage. |
| plan_route_mapA | Plan a rail/subway journey and render it as a Yahoo!乗換案内-style vertical timeline (an inline interactive view on claude.ai). The view shows stations, departure/arrival times, line names in their official colors, and transfer points stacked vertically; the same itinerary is also returned as text. 'from' and 'to' are each a station name (e.g. "新宿") or a "lat,lon" coordinate. By default shows the best (fastest) itinerary; use 'routeIndex' to pick another. Prefer this over plan_journey when a visual route is helpful. |
| suggest_stationsA | Autocomplete station names against the self-hosted OpenTripPlanner instance (self-hosted OTP (Kanto rail/subway)). Returns matching stations with coordinates. Use to resolve or disambiguate a name before plan_journey. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| route_map | Route timeline view (MCP App). |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: plan_journey for text itineraries, plan_route_map for visual timelines, and suggest_stations for name resolution. There is no overlap in functionality.
All tools follow a verb_noun pattern with consistent prefixes (plan_, suggest_). The naming is predictable and clear.
Three tools is slightly minimal but covers the core workflow: suggest stations, plan text journey, plan visual journey. The scope is focused and each tool earns its place.
The core journey planning is covered, but there are notable gaps such as missing tools for station details, line information, or schedule data, which agents might need.