Metro MCP

Service information

Support

Start with the public docs and service summary. If something still looks wrong, report it with enough context to reproduce without sharing secrets.

Last updated

Documentation and status

  • Documentation covers client setup, endpoints, tools, data sources, cache windows, and rate limits.
  • /info server information returns the current public MCP endpoint, supported cities, station counts, and capabilities as JSON.
  • Official WMATA or MTA channels are the right place to confirm urgent service conditions.

Bugs and feature requests

Use GitHub issues for reproducible non-sensitive bugs, documentation corrections, and feature requests.

Include the Metro MCP version, client name and version, request ID, timestamp with time zone, city and tool or page, and a minimal reproduction with the expected and actual result. Remove credentials, authorization data, personal information, and private conversation content before posting.

Never post API keys, bearer tokens, or secrets.

Security reports

Start at the repository’s GitHub Security page for the current reporting route. Private vulnerability reporting is not currently enabled for this repository, so do not publish exploitable details, secrets, or personal data in a public issue. The Security page is the source of truth if reporting options change.

Response expectations

This is a maintained open-source service, not a staffed transit help desk. Reports are reviewed as maintainer availability allows, with no guaranteed response time. Clear reproduction details help, but submitting a report does not guarantee a fix or feature.

Privacy and use

Read the Privacy page for request data and logs, or the Terms of Use for upstream-data limits and acceptable use.