metrotransit-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_routesA | Get all Metro Transit routes in the Minneapolis-St. Paul metro area (METRO Blue/Green/Gold/Orange/Red/A/B/C/D/E lines and bus routes). Supports optional filtering by search query. |
| get_route_directionsA | Get valid travel directions for a specific route (e.g., Eastbound/Westbound, Northbound/Southbound) and their direction IDs. |
| get_route_stopsA | Get all scheduled stops for a route in a specific direction, including their place codes and station descriptions. |
| get_departuresA | Get real-time departure predictions, vehicle countdowns, and stop alerts for a Metro Transit stop or station. You can query either by a 4-5 digit Stop ID, or by Route ID + Direction ID + Place Code. |
| get_service_alertsA | Get active service alerts, detours, stop closures, and disruptions across the Metro Transit network, optionally filtered by route ID or keyword. |
| search_stopsA | Search for stops/stations along a specific route by keyword or station name (e.g., search 'Stadium' or 'Nicollet' on the Green Line). |
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 6 tools
Each tool targets a distinct transit resource (routes, directions, stops, departures, alerts), but get_route_stops and search_stops overlap in purpose—one returns all stops while the other filters them by keyword. Descriptions are clear enough to differentiate, though minor boundary ambiguity exists.
All tool names follow a consistent snake_case verb_noun pattern (list_routes, get_route_directions, get_departures, search_stops). No mixed conventions or vague verbs, making the set highly predictable.
Six tools is well-scoped for a transit information server, covering route discovery, stop lookup, departures, and alerts without unnecessary bloat. Each tool earns its place in the workflow.
The core transit query surface is covered: routes, directions, stops, departures, and alerts. Minor gaps exist such as no route-by-ID lookup or stop details endpoint, but agents can achieve common tasks with the provided operations.