Download PDFMarkdown Version
ClaudeChatGPTPerplexityGeminiMicrosoft CopilotRaycastMeta AIGrokZ.aiQwenKimi
DeepSeekMistralCursorVS CodeWindsurfJetBrainsClineLovableVercel AI SDKLangChain

Use WMATA with your AI.

Connect your account once and let the AI you already use work with it, without building another integration. Access Washington DC Metro data via WMATA. track Metrorail and Metrobus in real-time, check incidents, and plan station visits from any AI agent.

Included with plan

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Complete set · 12 capabilities

The complete WMATA capability set.

These are the exact actions your AI can choose when you ask it to work with WMATA.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 12 available through WMATA.

  1. 01

    Get parking lots

    Can query all parking lots system-wide or filter by specific station code. Essential for park-and-ride trip planning, commuter parking availability, station selection for driving passengers, and transportation mode choice analysis. AI agents should use this when users ask "which stations have parking", "how many spaces are at Shady Grove", or need to plan park-and-ride journeys from suburban areas into DC. Get Metrorail station parking lot information

  2. 02

    Get rail stations

    Can filter by line code (RD=Red, OR=Orange, SV=Silver, BL=Blue, YL=Yellow, GR=Green) to show only stations on that line. Essential for station discovery, route planning, understanding line structure, and mapping the Metrorail network. AI agents should reference this when users ask "list all stations on the Red Line", "what is the station code for Foggy Bottom", or need to understand station sequences and line geography. Station codes are required for subsequent queries like next trains, predictions, entrances, and parking. List all Metrorail stations, optionally filtered by line

  3. 03

    Get bus incidents

    Returns incident descriptions, affected route IDs, detour information, bus stop closures, incident types (accident, road closure, construction, mechanical), start timestamps, and alternative service recommendations. Essential for bus service disruption awareness, alternative route planning, and passenger communication. AI agents should use this when users ask "are there any bus delays", "is route 30N running normally", or need to check Metrobus service reliability. Get current incidents affecting Metrobus service

  4. 04

    Get bus route details

    Returns all stops served by the route in order, trip headsigns, and route path information. Essential for route planning, understanding bus service coverage, stop discovery, and passenger journey preparation. AI agents should use this when users ask "what stops does the 30N bus serve", "show me the route details for X2", or need complete route structure including stop sequences for trip planning. Get detailed information about a specific Metrobus route

Capability set02 / 03

05-08

4 capabilities in this set.

Part of 12 available through WMATA.

  1. 05

    Get circuit predictions

    Returns bus route IDs, destination names, predicted arrival times in minutes, trip IDs, and vehicle IDs. Supports filtering by station code for station-specific predictions or system-wide queries. Essential for bus trip planning, real-time bus arrival awareness, and connection coordination between Metrorail and Metrobus. AI agents should use this when users ask "when is the next bus at Union Station", "show bus predictions for Foggy Bottom", or need real-time bus arrival predictions at a specific station or stop. Get next bus arrival predictions for Metrobus Circuit routes

  2. 06

    Get elevator incidents

    Returns affected station codes and names, elevator/escalator identifiers, outage descriptions, estimated repair times, outage start timestamps, and accessibility impact information. Essential for accessibility planning, wheelchair route verification, senior and disability passenger support, and station accessibility awareness. AI agents should use this when users ask "are there any elevator outages at Gallery Place", "is the elevator working at Union Station", or need to verify station accessibility before planning journeys for passengers with mobility needs. Get current elevator and escalator outages at Metrorail stations

  3. 07

    Get next rail

    Returns train destination names, lines (Red, Orange, Silver, Blue, Yellow, Green), predicted arrival times in minutes, car counts, group numbers, and train direction. Can query all trains system-wide or filter by specific station code. Essential for commuter trip planning, real-time arrival awareness, and station crowd management. AI agents should use this when users ask "when is the next train", "show upcoming trains at Gallery Place", or need real-time Metrorail arrival predictions. Station codes are 3-letter identifiers (e.g., "A01" for Metro Center, "B36" for Gallery Place). Use getRailStations first to find station codes if unknown. Get next train predictions across the entire Metrorail system or at a specific station

  4. 08

    Get rail incidents

    Returns incident descriptions, affected station codes, line impacts, incident types (delay, power problem, medical, police activity, track maintenance), severity indicators, start timestamps, and estimated resolution times. Essential for service disruption awareness, alternative route planning, passenger communication, and understanding system reliability. AI agents should reference this when users ask "are there any delays on the Red Line", "is Metro running normally", or need to check service reliability before planning Metrorail journeys. Get current incidents affecting Metrorail service

Capability set03 / 03

09-12

4 capabilities in this set.

Part of 12 available through WMATA.

  1. 09

    Get station entrances

    Returns entrance names, street addresses, latitude/longitude coordinates, entrance descriptions, and whether the entrance has escalator or elevator access. Essential for station navigation, first-time visitor guidance, street-level wayfinding, accessible entrance identification, and trip end planning. AI agents should reference this when users ask "where are the entrances to Metro Center", "find the closest entrance to Gallery Place", or need street-level navigation guidance for reaching a Metrorail station. Get entrance information for a specific Metrorail station

  2. 10

    Get station prediction

    Returns trains with destination names, line colors, predicted arrival times, car counts, and train direction. More targeted than system-wide next rail queries. Essential for passenger waiting at a specific station, connection planning, and real-time arrival boards. AI agents should use this when users ask "when is the next train at Silver Spring", "show trains coming to Shady Grove", or need station-specific arrival predictions. Requires station code from getRailStations results. Get next train predictions at a specific Metrorail station

  3. 11

    Get bus positions

    Returns bus vehicle IDs, route IDs, latitude/longitude coordinates, trip IDs, destination names, deviation from schedule in seconds, and direction. Can query all buses system-wide or filter by specific route ID. Essential for real-time bus tracking, passenger wait time estimation, and bus arrival prediction. AI agents should reference this when users ask "where is the X2 bus", "show all buses on route 30N", or need to track Metrobus vehicles in real-time. Route IDs are typically 2-5 character identifiers (e.g., "30N", "X2", "L2"). Use getBusRoutes first to find route IDs if unknown. Get real-time positions of Metrobus vehicles, optionally filtered by route

  4. 12

    Get bus routes

    Returns route IDs, route names, descriptions, and route types. Covers all WMATA-operated bus routes including limited-stop, local, and express services across DC, Maryland, and Virginia. Essential for route discovery, service area analysis, transit network understanding, and identifying route IDs for use in bus position and route detail queries. AI agents should reference this when users ask "list all bus routes", "what bus routes serve DC", or need to identify route IDs for subsequent Metrobus queries. List all Metrobus routes in the WMATA system

Observed, not estimated

878ms average. Fast in production.

WMATA is checked daily against the live service.

Daily averagePeak 1053ms
Aug 20Today
Fastest day
727ms
Slowest day
1053ms
14-day trend
Slowing+23%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 12 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of WMATA, so you can see the experience inside your AI.

It does not authenticate your account with WMATA. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

WMATA Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_EYQRq26ybnEjlKYIt4RwxqPojXK1XYFGw8q2movb/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — WMATA capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "wmata-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_EYQRq26ybnEjlKYIt4RwxqPojXK1XYFGw8q2movb/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

FAQ

Questions WMATA owners ask.

  • 01

    Can my AI check when the next Metrorail train is arriving at my station?

    Yes! Use the get_station_prediction capability with the station code (e.g., "A01" for Metro Center, "B36" for Gallery Place). Your AI will return all upcoming trains with destination names, line colors (Red, Orange, Silver, Blue, Yellow, Green), predicted arrival times in minutes, and car counts. If you do not know the station code, first use get_rail_stations to find it by name. For a system-wide view of all upcoming trains, use get_next_rail without a station code.

  • 02

    How do I check if there are any delays or incidents affecting my Metrorail line?

    Use the get_rail_incidents capability to check all active service disruptions across the Metrorail system. This returns incident descriptions, affected stations and lines, incident types (delays, power problems, medical emergencies, track maintenance), and start times. You can also check get_elevator_incidents for elevator and escalator outages that may affect accessibility at your station. For Metrobus service issues, use get_bus_incidents.

  • 03

    Can I track Metrobus vehicles in real-time to see when my bus will arrive?

    Yes! Use get_bus_positions to see real-time GPS locations of all Metrobus vehicles, or filter by route ID (e.g., "30N", "X2") to track buses on a specific route. Returns vehicle IDs, route IDs, latitude/longitude, destinations, and schedule deviation in seconds. For detailed route information including stop sequences, use get_bus_route_details with the route ID. Use get_bus_routes first to find route IDs if unknown.

Explore

More in Iot Hardware

Suggestions