Metro MCP Server

MCP server for US transit systems (DC Metro, NYC Subway) on Cloudflare Workers. The metro mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

A unified remote Model Context Protocol (MCP) server supporting multiple US transit systems. Currently supports Washington DC Metro (WMATA) and New York City Subway (MTA). Built for seamless integration with MCP-compatible clients like Claude Desktop, Cursor, Codex, and any client that supports Streamable HTTP MCP servers.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

• Incidents — ** Service disruptions and advisories
• Real — time feeds:** Protocol Buffers format with 30-second update intervals
• get_station_predictions — Get real-time train arrival predictions for a station
• search_stations — Search for stations by name or code
• get_stations_by_line — Get all stations on a specific line
• get_incidents — Check current service disruptions and advisories
• get_all_stations — Get a complete list of all stations with coordinates
• get_elevator_incidents — Find elevator and escalator outages
• get_bus_predictions — Get real-time bus arrival predictions (7-digit stop ID)
• get_bus_routes — Get list of all available bus routes
• get_bus_stops — Search bus stops by location or get all stops
• get_bus_positions — Get live positions of all buses (optionally filter by route)

Configuration

You will need 2 environment variables: WMATA_API_KEY, GITHUB_CLIENT_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• WMATA API Key (required) - Cloudflare Account (free tier works) - Bun or Node.js installed - GitHub OAuth App (for authentication)

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Metro MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the metro mcp mcp server does with a few real requests.

When to reach for it

Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Metro MCP's toolset — Incidents, Real, get_station_predictions and 11 more — is a fair guide to whether it matches your workflow. It is maintained by aarekaz; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Metro MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.