Prototyp · Vorschau: alle Server aus der offiziellen Registry, alle 30 Minuten synchronisiert. Bewertungen und Benutzerkonten folgen in einem späteren Schritt.
PopNx MCPMCP-Server für alle, die KI nutzen · in einfachen Worten erklärt
Einsteigermodus An
FarbenSystemHellDunkel
SpracheไทยEnglish中文日本語한국어EspañolDeutsch
☰ MenüEinstellungen
Einsteigermodus An
FarbenSystemHellDunkel
SpracheไทยEnglish中文日本語한국어EspañolDeutsch

DMV Transit

von Concorde1969Version 1.0.0i★ –iLäuft in der Cloud
Name in der Registrycom.dmvtransit/transit

Installieren

Überblick

Beschreibung vom Entwickler (englisches Original)

Unofficial DC, Maryland and Virginia transit: trips, Metro, buses, rail, fares and alerts.

Die drei Säulen von PopNx MCP

Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.

Was du damit machen kannst

Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.

  • Verbindung: Läuft in der Cloud
  • Transport: Streamable HTTP
  • Kategorie: Sonstiges

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Bevor du installierst

  • Basischecks: 3 von 3 bestanden
  • Läuft auf dem Server des Entwicklers: Was du fragst, läuft über dessen Server.
  • Kann 18 Dinge (Tools) search_transit_info, get_service_alerts, get_rider_reports, get_elevator_escalator_status …
  • Die Registry nennt keinen Schlüssel zum Eintragen.

Du brauchst

Welche App nutzt du?

Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.

Funktioniert in Claude im Web, auf dem Desktop und auf dem Handy:

  1. Öffne Settings → Connectors
  2. Tippe auf Add custom connector
  3. Füge die Adresse unten ein und tippe auf Add
  4. Wenn eine Anmeldung verlangt wird, melde dich beim Dienst des Entwicklers an
SettingsConnectors1+ Add2https://…3
https://dmvtransit.com/mcp

Führe das in deinem Terminal aus

claude mcp add --transport http transit https://dmvtransit.com/mcp

In Cursor öffnen

Oder kopier die Einstellungen selbst

In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen

{
  "mcpServers": {
    "transit": {
      "url": "https://dmvtransit.com/mcp"
    }
  }
}

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

In VS Code öffnen

Oder kopier die Einstellungen selbst

In .vscode/mcp.json in deinem Projekt einfügen

{
  "servers": {
    "transit": {
      "type": "http",
      "url": "https://dmvtransit.com/mcp"
    }
  }
}

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

ChatGPT verbindet sich nur mit Servern im Internet:

  1. Öffne ChatGPT im Web → Settings → Connectors (Apps)
  2. Tippe auf Create oder Add (bei manchen Tarifen musst du zuerst Developer mode unter Advanced einschalten)
  3. Füge die Adresse unten ein, gib ihr einen Namen und speichere
  4. Wenn eine Anmeldung verlangt wird, melde dich beim Dienst des Entwicklers an
SettingsConnectors1+ Create2https://…3
https://dmvtransit.com/mcp

Menünamen können sich je nach Tarif und mit der Zeit leicht unterscheiden.

Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Was er kann

Tool-Namen und -Beschreibungen genau so, wie der Server sie am 6. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.

  • search_transit_info

    Full-text search of the agencies' web pages: fares, how to pay, accessibility, safety, rules, new-rider/visitor guides, and service-change notices. NOT a source for routes, stops, schedules, hours or service days — use get_metro_route, plan_connection, get_route or transfers_at (

  • get_service_alerts

    Live service disruptions: WMATA incidents (Metrorail, Metrobus, elevators) and agencies' GTFS-realtime alerts (detours, closed stops, missed trips). Args: line: Metrorail line code (RD, BL, YL, OR, GR, SV) or bus route number. station: Metrorail station name or code. mode: "rail"

  • get_rider_reports

    Recent reports from other RIDERS (crowdsourced on this site): delays, crowding, broken elevators, tips. Unverified and unofficial: always present them as "riders reported ...", with how long ago, never as agency information, and never let them replace the timetable or official al

  • get_elevator_escalator_status

    Elevators and escalators currently out of service, optionally for one station. Answer only from this tool's results: never add routes, hours, phone numbers, addresses or tips from memory. Unofficial tool, not affiliated with WMATA or any transit agency.

  • get_station_info

    Lines served, address, parking availability, transfers, and entrances for a station (accepts a name like "Gallery Place" or a code like "B01"). Answer only from this tool's results: never add routes, hours, phone numbers, addresses or tips from memory. Unofficial tool, not affili

  • get_fare

    Station-to-station Metrorail fare. Args: origin: Origin station name or code. destination: Destination station name or code. rider_type: "regular"/"peak", "offpeak", or "senior"/"disabled"/"reduced". Answer only from this tool's results: never add routes, hours, phone numbers, ad

  • geocode_address

    Find where a street address, hotel, attraction or other place is, in the DC, Maryland and Northern Virginia area. Call this whenever a rider names a place that isn't plainly a station, before planning a trip from or to it. Check that the result is the place they meant, and ask th

  • plan_trip

    Real trip options from the agencies' timetables, like the site's map: trips leaving in the 3 hours after the given time from each agency's closest stops (up to about a mile's walk; the walking time is part of each option), direct trips first, one transfer only when needed, two tr

  • get_metro_route

    How to ride Metrorail between two stations: which line(s), where to change trains, which direction ("toward ..."), number of stops, and the fare. Use this for EVERY Metrorail trip — never assume two stations share a line. Args: origin: Station name, code (e.g. "C10"), or airport

  • list_topics

    List content categories with document counts and data freshness. Answer only from this tool's results: never add routes, hours, phone numbers, addresses or tips from memory. Unofficial tool, not affiliated with WMATA or any transit agency.

  • get_guide

    Full text of the primary guide for a topic: new_rider, visitor, payment, fares, accessibility, safety, or maps. Answer only from this tool's results: never add routes, hours, phone numbers, addresses or tips from memory. Unofficial tool, not affiliated with WMATA or any transit a

  • list_agencies

    Every transit system in the region (WMATA + VRE, Virginia Breeze, Fairfax Connector, ART, DASH, CUE, Loudoun, OmniRide): mode, role, strengths, service area, a one-line fare/payment summary, and data freshness. Answer only from this tool's results: never add routes, hours, phone

  • find_stops_near

    Stops and stations within walking distance of a place, across all agencies. Args: place: A Metro station name, a stop name, or "lat,lon". radius_m: Search radius in meters (default 400). agency: Optional feed slug to restrict to (e.g. "dash", "vre", "wmata"). Answer only from thi

  • get_route

    One route from an agency's GTFS schedule: days and hours of service, typical frequency, endpoints, fare, and any live disruptions on it. Args: agency: Agency slug or name (e.g. "metrobus", "wmata" for Metrorail lines, "fairfax-connector", "OmniRide", "loudoun"). query: Route numb

  • transfers_at

    Routes from OTHER systems reachable on foot from a station or stop, grouped by agency, each with walk time and its service window from the GTFS schedules. Pass `day` (e.g. "saturday") and/or `time` ("HH:MM") to get a per-connection feasibility check. Answer only from this tool's

  • how_to_pay

    How to pay to ride one agency. `fare_page_text` is the agency's own fare page (the source for prices, discounts and transfer rules); the other fields are a shorter hand-maintained summary that the fare page overrides. Args: agency: Agency slug or name (e.g. "vre", "dash", "omniri

  • plan_connection

    Advise on getting between two places across systems: which system for each leg, the transfer hub, WHICH DAYS/TIMES the connection works, and the fare + how to pay per leg. Guidance, not a booked itinerary. Args: origin: Address, place name, station, or "lat,lon". destination: Add

  • estimate_trip_cost

    Estimate the total fare for a cross-system trip: per-leg fares, how to pay each, and a total — noting each leg is usually a separate payment. Origin and destination can be addresses, places, stations or "lat,lon". Answer only from this tool's results: never add routes, hours, pho

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026

  • ✓ Bestanden

    Entwickler passt zum Repo

    Der Registry-Name wurde über die Domain dmvtransit.com bestätigt (die Registry prüft, wem die Domain gehört)

  • … Noch nicht geprüft

    Wird noch gepflegt

    Dieses Repo haben wir noch nicht von GitHub gelesen

  • … Noch nicht geprüft

    Hat eine Lizenz

    Dieses Repo haben wir noch nicht von GitHub gelesen

  • ✓ Bestanden

    Endpunkt antwortet

    Antwort in 256 ms (HTTP 200)

  • – Nicht zutreffend

    Anmeldung mit OAuth

    Keine Anmeldung nötig

  • ✓ Bestanden

    Keine versteckten Anweisungen in Tool-Beschreibungen

    Wir haben 18 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden

Im Vergleich mit anderen in Sonstigesi

  • Mehr Sterne als 0 % der anderen 32433 Server in dieser Kategorie
  • Neuer in der Registry veröffentlicht als 91 % der anderen 32433 Server in dieser Kategorie
  • Basischecks gleich gut wie oder besser als bei 100 % der anderen 32433 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Häufige Fragen

Ist DMV Transit sicher?

Er hat 3 von 3 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.

Welche Schlüssel oder Codes braucht er?

Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.

Läuft er auf meinem Computer oder in der Cloud?

Er läuft in der Cloud des Entwicklers. Du verbindest dich übers Internet, ohne etwas zu installieren, aber was du sendest, läuft über die Server des Entwicklers.

Wird er noch gepflegt?

Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (1.0.0) kam vor 3 Tagen in die Registry.

Welche Apps können ihn nutzen?

Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.

Was kann ich stattdessen nutzen?

In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, Symantec Cloud DLP AIops

Alternativen

Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.

So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

Spec Driven Development

von formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Läuft auf deinem Computer★ 440MITAktualisiert vor 14 Monaten
Installieren

Remote Desktop Commander

von desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Läuft in der Cloud★ 211Aktualisiert gestern
Installieren

README vom Entwickler

README öffnen

Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.

DMV Regional Transportation Assistant (transit-mcp)

A plain-language assistant that helps people — especially first-time riders — get around the Washington DC / Maryland / Virginia region by public transit. It answers from current, cited data pulled from WMATA (Metrorail + Metrobus), the Virginia systems (VRE, Fairfax Connector, ART, DASH, CUE, Loudoun, OmniRide, Virginia Breeze), Maryland (MTA bus, commuter bus, Metro SubwayLink, Light RailLink, MARC, Annapolis Transit, Harbor Connector, Potomac Valley), the Dulles Airport shuttles, and intercity services (Amtrak, FlixBus and other intercity buses), and focuses on what trips actually hinge on: which systems connect where, on which days and at what times a connection works, and how to pay each leg.

The home page is a leave-now trip planner on a map: type where you're going (or use your location), and it shows every good way to get there in the next 3 hours — direct trips first, one change only when it saves time, and changes with a wait of 10 minutes or less preferred (a longer wait is offered only when nothing better works) — with live departure times where the agency publishes them. It uses each agency's closest stops (up to about a mile away) and shows how much walking each trip involves. The assistant chat sits in a drawer beside the map.

Unofficial. This is an independent project. It is **not affiliated with,

endorsed by, sponsored by, or operated by** WMATA or any other transit agency.

Agency names identify their services only. For official information, contact the

agency directly.

Answers are grounded in the stored data: the assistant must call its tools before it answers, is instructed never to fill gaps from the model's general knowledge, and says "I don't have that information" rather than guess. (The Claude API no longer accepts a temperature setting, so accuracy is enforced through the data, the tools and the prompt instead — see chat/agent.py.)

Quick start (Windows)

  1. Install Python 3.11+ (tick *Add python.exe to PATH*).
  2. Double-click `start.bat`.
  • First time: it sets everything up, creates a settings file and opens it in Notepad. Paste in your ANTHROPIC_API_KEY (console.anthropic.com) and WMATA_API_KEY (free at developer.wmata.com), save, and double-click start.bat again. It then downloads transit data (15–20 minutes for all 23 feeds).
  • For the map planner, also add TRANSITLAND_API_KEY (transit.land, Explorer plan) and GOOGLE_GEOCODING_API_KEY (Google Geocoding API; GEOCODE_API_KEY from geocode.maps.co also works), and download the regional map once (about 600 MB; without it the map shows a plain background): powershell -ExecutionPolicy Bypass -File deploy\map\fetch-basemap.ps1
  • After that: the assistant opens in your web browser within seconds.
  1. Keep the black window open while you use it; close it to stop.
FileWhat it does
start.batSet up if needed, then start the assistant and open the browser
refresh-data.batDownload the latest alerts, schedules, fares and rider info (run weekly)
check-setup.batPlain-English check of keys, data, agencies and the trip planner

If a feed can't be downloaded, you can add it by hand — see feeds/README.md.

Deploying (public website)

The same app runs as a public site — https://dmvtransit.com — on one small AWS Lightsail server in Ohio (us-east-2) with Docker, created and managed by the scripts in deploy/lightsail/: docker compose up -d --build starts the website, automatic HTTPS (Caddy) and a scheduler that keeps data fresh. Public mode adds per-visitor rate limits, a site-wide daily cap and friendly error messages. Step-by-step guide: [deploy/README.md](deploy/README.md).

Architecture

Three layers, each swappable on its own (details in docs/EXTENDING.md):

 agencies/*.toml ──► ingest source plugins ──► SQLite (FTS5) + data/gtfs/*.zip

one file per gtfs · web_pages · │ agency wmata_api · (yours) ▼ retrieval + scheduling engine heuristic | python | process | http │ TripRequest / TripPlan ▼ MCP server (17 tools) ──► web chat (Claude) └─► any MCP client

LayerExtension pointWhere
AgenciesDrop a TOML file — no codeagencies/, built-ins in src/transit_mcp/agencies/definitions/
Data sources@register_source plugin or entry pointsrc/transit_mcp/ingest/sources/
Trip planningYour engine in Python, Node (stdio) or HTTP behind a versioned JSON contractsrc/transit_mcp/planning/, templates in engines/

Every stored record keeps its source URL, fetch time and content hash, so answers are cited and stale data is flagged.

Where each kind of answer comes from
AnswerSource
Routes, stops, schedules, service days and hours (Metrorail and Metrobus included)Each agency's GTFS feed, found through [Transitland](https://www.transit.land/)
Fares, how to pay, how to rideThe agency's own fare / rider web pages, plus WMATA's station-to-station fare data (checked against wmata.com/pay.html)
DisruptionsWMATA real-time incidents, agencies' GTFS-realtime alerts, and their service-alert / service-change web pages — always shown *alongside* the GTFS schedule, never instead of it
Live departure times (map planner)The agency's own GTFS-realtime TripUpdates feed at the URL Transitland lists (WMATA rail and bus, VRE, Fairfax Connector, MARC, ART); Transitland's departures API for the rest. Otherwise scheduled times, labelled "Scheduled"
Addresses → map pointsSuggestions while typing from Google Places Autocomplete (place picked → Place Details for its location), else the Google Geocoding API (or geocode.maps.co without a Google key); all called from the server (the key never reaches browsers)
The mapOpenStreetMap data in a self-hosted Protomaps extract, drawn with MapLibre GL

Web pages are never used for routes or schedules. Each feed is downloaded from the official URL listed in Transitland's public registry (no API quota used); Transitland's own hosted copy is the fallback, at one metered API call each (transit-mcp doctor shows which source each feed used). Every Transitland API call is counted against TRANSITLAND_MONTHLY_BUDGET (4,500 of the Explorer plan's 5,000), after which the planner shows scheduled times.

The planner only suggests a change between two stops less than 0.3 km apart (of any agency), so every transfer is a short walk. Trips with two changes are searched only when nothing with fewer changes works (TRIP_MAX_TRANSFERS). At BWI, DCA and IAD the step between the terminal and the rail station comes from planning/airports.toml: BWI's free shuttle to the MARC/Amtrak station (timing from the airport's website, since the shuttle has no current GTFS feed) and DCA's and IAD's walkways, each with the airport's own directions. Feeds that give trips as headways (frequencies.txt: the Dulles shuttles, CUE, Annapolis Transit) are expanded into one trip per run when loaded. Nearby stops are also grouped into clusters (every pair in a cluster is less than 0.3 km apart) for the assistant's "what connects here" answers.

Fares

Each agency's fare summary is in its definition file, with the agency's fare page scraped nightly where the site allows it. VRE and MARC price trips by station, which GTFS doesn't carry, so their published charts are in planning/rail_fares.toml and trips show the exact one-way fare. Fares that vary by trip (Amtrak, FlixBus, Greyhound, Virginia Breeze, intercity buses) send riders to the operator's site.

Rider reports (crowdsourced)

Riders can warn each other from the map page (Report an issue): the station and line (if any), where the trip started and ended, the date, and what happened in their own words. Each report is saved in the transit database (rider_reports) and checked by a small Claude model (REPORTS_MODEL, default claude-haiku-5-5), which holds back off-topic or abusive posts, sorts it (delay, crowding, elevator...), writes a short neutral summary and notes the agencies, lines and stations. Published reports show on matching trip options for REPORTS_SHOW_HOURS (3) and the assistant can look them up; both always label them as unverified rider reports. Review them with transit-mcp reports list|hide|publish|delete.

Accounts: My places

Visitors (tourists especially) sign in with their email address and a 6-digit code we email them (no password), and save their hotel with check-in and check-out dates, a home, and the attractions they plan to visit, each with an optional day. Current places appear as one-tap quick picks under "Where to?", in the From and To suggestions, and as pins on the map (Go here / Start here); a hotel counts only during the stay, and past visits drop out. Accounts live in their own SQLite file (ACCOUNTS_DB), never linked to the chat log; saved places are logged as "saved" without names and are kept out of links. Codes go out by SMTP (Amazon SES on the public site; see deploy/README.md); a local server without SMTP prints the code in its log. A code works for 10 minutes and 5 tries.

Plan my trip (assistant)

The site is one panel beside the map: "Where to?" at the top, then a single conversation where trip searches appear as live cards alongside the assistant's answers. The assistant can put a trip on the map itself (show_trip, for "take me to the Zoo"), and each question carries the trip on screen, so "how do I pay for this trip?" means the option the rider picked. On phones the panel is a sheet over the map.

Signed-in visitors can plan a trip by chatting: "Plan my visit" starts planning mode. It saves their hotel and places, puts stops on days with "be there by" or "leave at" times, and works out the buses and trains between them for each day (timetable trips that arrive with time to spare, or a walk when it's close). Questions about places to eat or visit are answered with Google Places Text Search (rating, price, opening hours), never from the model's memory, capped by GOOGLE_PLACES_SEARCH_MONTHLY_BUDGET. Anyone can ask questions; saving and planning need an account. The plan is stored in the account, shown under My places, and the planning tools run only in the web app, not on the MCP server, so /mcp holds no personal data. Tool inputs are left out of the chat log.

Command line

All commands run from the project folder (.venv\Scripts\transit-mcp.exe …, or just transit-mcp … with the virtual environment activated).

transit-mcp launch                         # what start.bat runs

transit-mcp doctor # what check-setup.bat runs transit-mcp ingest all # what refresh-data.bat runs transit-mcp ingest gtfs --only dash,vre # one scope (api|gtfs|web), some agencies transit-mcp agencies # every system with role + fare headline transit-mcp agencies --config

Nur der Anfang wird gezeigt; den Rest findest du im Repo

PopNx fragen