marta-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MARTA_API_KEY | Yes | Your MARTA API key for rail data. Register at https://www.itsmarta.com/developer-reg-rtt.aspx |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_rail_arrivalsB | Get real-time MARTA train arrival predictions. |
| list_rail_stationsA | List all MARTA rail station names accepted by get_rail_arrivals. |
| get_bus_positionsA | Get live MARTA bus vehicle positions from the GTFS-realtime feed. |
| get_bus_trip_updatesA | Get live MARTA bus arrival/departure predictions (GTFS-realtime trip updates). |
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
Each tool targets a distinct aspect of MARTA transit data: bus positions, bus trip updates, rail arrivals, and rail stations. No overlap in functionality.
All tools use a consistent verb_noun pattern in snake_case (e.g., get_bus_positions, list_rail_stations). The minor variation of 'list_' for stations is standard for listing endpoints.
4 tools is an appropriate scope for a real-time transit data server, covering bus and rail essentials without being too sparse or overwhelming.
The tool set covers core real-time functionality for both bus and rail. However, it lacks a bus route or station list analogous to list_rail_stations, which could be a minor gap for agents needing bus station identifiers.