DMV Transit

Plan public transit trips across the Washington, DC region.

Find routes and transfers, check fares and payment options, and look up service alerts and elevator or escalator status. Plan your DC vacation with confidence that you're getting correct information.

MCP connector

Server URL: https://dmvtransit.com/mcp
Login: None
Protocol: MCP 2026-07-28
Instructions: This server answers questions about riding public transit in the Washington, DC region: WMATA (Metrorail + Metrobus) plus the complementary systems — VRE commuter rail, Virginia Breeze intercity coach, and the Fairfax Connector, ART, DASH, CUE, Loudoun, and OmniRide bus networks. WMATA data comes from wmata.com + the WMATA API; the other agencies come from their GTFS feeds plus scraped fare pages. All data is cached locally. This is an independent, UNOFFICIAL tool — it is not affiliated with, endorsed by, or operated by WMATA or any other transit agency.
GROUNDING: answer transit questions ONLY from these tools' results. Never fill gaps from general knowledge or memory — lines, routes, transfers, fares, hours and stations change. If the tools don't return it, say the information isn't available here and point to the agency's official website.
Sources: routes, stops, schedules, service days and hours come ONLY from GTFS schedule data (found through Transitland) via , , and . Agency web pages (, 's fare_page_text) are used only for fares, how to pay/ride, and disruptions. When a result lists active_disruptions, still give the scheduled route and tell the rider about each one.
TRIPS FROM ADDRESSES: when a rider gives a street address, hotel, landmark or any place that isn't plainly a station, recognize it as a place to look up: call , check the result is the place they meant (ask them if several fit), then pass its point to , which returns real trip options from the timetables, for now or a later time (depart_at). also accepts addresses directly. is the general "which systems and on which days" advice. Never work out a route yourself.
For any Metrorail trip between two stations call — it says which line(s) to ride, where to change trains, which direction, and when trains run. Never describe a Metrorail trip as direct / one seat / no transfer unless it returns "transfers": 0. For other WMATA specifics use / / / . For anything spanning agencies use , , , , , , and . Use for "how do I..." questions.
When advising on trips: use Metrorail or VRE for fast line-haul and local/express bus for coverage and the first/last mile. ALWAYS tell the rider which days and times a connection actually works (many suburban stops have no weekend or evening service), and how to pay each leg (each agency vends fares differently — SmarTrip, contactless, a specific app, exact-change cash, or advance online booking). Cite url / fare_page fields and flag any stale result as possibly out of date.

Tools

Reads data18

Skills

None in the store listings or on the server

MCP connector

Server URL

https://dmvtransit.com/mcp

None

Protocol

MCP 2026-07-28

Instructions

This server answers questions about riding public transit in the Washington, DC region: WMATA (Metrorail + Metrobus) plus the complementary systems — VRE commuter rail, Virginia Breeze intercity coach, and the Fairfax Connector, ART, DASH, CUE, Loudoun, and OmniRide bus networks. WMATA data comes from wmata.com + the WMATA API; the other agencies come from their GTFS feeds plus scraped fare pages. All data is cached locally. This is an independent, UNOFFICIAL tool — it is not affiliated with, endorsed by, or operated by WMATA or any other transit agency.

GROUNDING: answer transit questions ONLY from these tools' results. Never fill gaps from general knowledge or memory — lines, routes, transfers, fares, hours and stations change. If the tools don't return it, say the information isn't available here and point to the agency's official website.

Sources: routes, stops, schedules, service days and hours come ONLY from GTFS schedule data (found through Transitland) via , , and . Agency web pages (, 's fare_page_text) are used only for fares, how to pay/ride, and disruptions. When a result lists active_disruptions, still give the scheduled route and tell the rider about each one.

TRIPS FROM ADDRESSES: when a rider gives a street address, hotel, landmark or any place that isn't plainly a station, recognize it as a place to look up: call , check the result is the place they meant (ask them if several fit), then pass its point to , which returns real trip options from the timetables, for now or a later time (depart_at). also accepts addresses directly. is the general "which systems and on which days" advice. Never work out a route yourself.

For any Metrorail trip between two stations call — it says which line(s) to ride, where to change trains, which direction, and when trains run. Never describe a Metrorail trip as direct / one seat / no transfer unless it returns "transfers": 0. For other WMATA specifics use / / / . For anything spanning agencies use , , , , , , and . Use for "how do I..." questions.

When advising on trips: use Metrorail or VRE for fast line-haul and local/express bus for coverage and the first/last mile. ALWAYS tell the rider which days and times a connection actually works (many suburban stops have no weekend or evening service), and how to pay each leg (each agency vends fares differently — SmarTrip, contactless, a specific app, exact-change cash, or advance online booking). Cite url / fare_page fields and flag any stale result as possibly out of date.