@pipeworx/mobility-database

Connect: https://gateway.pipeworx.io/mobility-database/mcp · Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 3

The open catalogue of public-transport data feeds maintained by MobilityData — ~4,500 GTFS Schedule feeds and ~1,900 GTFS-Realtime feeds across ~70 countries, each with the operator’s own download URL, licence and bounding box. The successor to TransitFeeds.

Tools

• mobilitydb_search_feeds(query?, country?, municipality?, provider?, data_type?, include_inactive?, limit?) — find the transit feed for an agency, city or country.
• mobilitydb_gtfs_rt_feeds(country?, query?, entity_type?, group_by_agency?, limit?) — realtime feeds (vehicle positions / trip updates / service alerts) with the schedule feed each is keyed against.
• mobilitydb_feed(feed_id) — everything the catalogue records about one feed, plus its sibling realtime streams and any superseding entry.

Auth

Keyless.

MobilityData also runs an authenticated REST API at api.mobilitydatabase.org, which takes a bearer token minted from a refresh token issued on free signup at https://mobilitydatabase.org/sign-up. This pack deliberately does not use it and declares no platform key: the catalogue export carries the same feed inventory with no credential, and declaring a key env var the gateway does not hold un-sinks routing toward a tool that could only refuse. What the authenticated API would add is per-version dataset history and MobilityData’s own validation reports; if that is wanted, PLATFORM_MOBILITYDB_TOKEN and the code that uses it land together in one change.

Data sources

• https://files.mobilitydatabase.org/feeds_v2.csv — the catalogue export (~6,475 rows including superseded entries).

Traps, verified live 2026-09-17

• It is real CSV, not line-splittable. Feed names and notes contain commas, quotes, CJK text and nested parentheses — "TC_大有巴士(公總) (Dayou bus (public bus))". Splitting on , puts an operator’s contact email in the data_type column. There is an RFC 4180 parser in src/index.ts for exactly this.
• One agency publishes three realtime rows, one per entity_type: vp vehicle positions, tu trip updates, sa service alerts, each with a different URL. Counting “realtime feeds” without collapsing on static_reference triples the agency count.
• A realtime feed is unusable without its schedule feed. static_reference names it; realtime trip ids only resolve against that specific GTFS feed.
• Some feeds need the CONSUMER’s own credential at the transit agency (urls.authentication_type 1 or 2, parameter named in urls.api_key_parameter_name). That credential is between the caller and the agency; it is reported so a caller knows before fetching.
• redirect.id marks a superseded entry that is still present in the export and would otherwise look like a live feed.

Tools

• mobilitydb_search_feeds — Find the public-transport schedule feed (GTFS) for an agency, city or country from the Mobility Database, MobilityData’s open catalogue of ~4,500 transit feeds worldwide. Returns the operator’s own do
• mobilitydb_gtfs_rt_feeds — List the GTFS-Realtime feeds — live vehicle positions, trip updates and service alerts — registered in the Mobility Database for a country, city or operator, with the realtime endpoint URL and the GTF
• mobilitydb_feed — Everything the Mobility Database records about one transit feed, by its catalogue id (e.g. mdb-1210, or a jbda-* id). Returns the operator’s download URL and the catalogue’s stable latest-version URL,