prt-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host to bind to (default: 127.0.0.1) | 127.0.0.1 |
| PORT | No | Port to listen on (default: 3000) | 3000 |
| MCP_AUTH_TOKEN | No | Bearer token for /mcp endpoint | |
| PRT_USER_AGENT | No | Optional user agent string | |
| PRT_MAX_RETRIES | No | Optional maximum number of retries | |
| MCP_ALLOWED_HOSTS | No | Comma-separated Host allowlist | |
| MCP_RATE_LIMIT_MAX | No | Maximum requests per window | |
| MCP_ALLOWED_ORIGINS | No | Comma-separated browser Origin allowlist | |
| PRT_TRUETIME_API_KEY | Yes | Your PRT TrueTime API key (required) | |
| PRT_TRUETIME_BASE_URL | No | Optional base URL for TrueTime API | |
| PRT_REQUEST_TIMEOUT_MS | No | Optional request timeout in milliseconds | |
| MCP_RATE_LIMIT_WINDOW_MS | No | Rate limit window in milliseconds |
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": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| prt_get_routesC | Fetch route metadata from TrueTime getroutes. |
| prt_get_directionsC | Fetch available directions for a route using getdirections. |
| prt_get_stopsC | Fetch stops for a route with optional direction using getstops. |
| prt_get_vehiclesC | Fetch live vehicle data via getvehicles. |
| prt_get_predictionsC | Fetch arrival predictions for one or more stop IDs. |
| prt_get_patternsC | Fetch route geometry/pattern data via getpatterns. |
| prt_get_service_bulletinsC | Fetch service bulletins using getservicebulletins. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| transit-arrival-workflow | Step-by-step workflow for arrival predictions at a stop. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| prt-api-capabilities | High-level capability list for available tools. |
TDQS
Scored across 7 tools
Each tool targets a distinct TrueTime data endpoint: routes, directions, stops, vehicles, predictions, patterns, and service bulletins. The nouns alone make the intended data type unambiguous, so an agent can reliably select the correct tool.
Every tool follows the same prt_get_<plural_noun> snake_case pattern with a shared prt prefix. There are no deviations in verb style, casing, or structure, making the set highly predictable.
Seven read-only tools map cleanly to the seven TrueTime API endpoints. The count is well-scoped for a transit data wrapper, with no redundant or filler tools.
The surface covers the full TrueTime read-only endpoint set: routes, directions, stops, vehicles, predictions, patterns, and service bulletins. All standard transit-data queries are reachable with no obvious dead ends for the stated purpose.