Mobility Database MCP server

@pipeworx/mobility-database

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.

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Tools

— find the transit feed for an agency, city or country.

• mobilitydbsearchfeeds(query?, country?, municipality?, provider?, datatype?, includeinactive?, limit?)

— realtime feeds (vehicle positions / trip updates / service alerts) with the schedule feed each is keyed against.

• mobilitydbgtfsrtfeeds(country?, query?, entitytype?, groupbyagency?, limit?)

plus its sibling realtime streams and any superseding entry.

• mobilitydbfeed(feedid) — everything the catalogue records about one feed,

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 . 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, PLATFORMMOBILITYDBTOKEN and the code that uses it land together in one change.

Data sources

(~6,475 rows including superseded entries).

• — the catalogue export

Traps, verified live 2026-09-17

quotes, CJK text and nested parentheses — "TC大有巴士(公總) (Dayou bus (public bus))". Splitting on , puts an operator's contact email in the datatype column. There is an RFC 4180 parser in src/index.ts for exactly this.

• It is real CSV, not line-splittable. Feed names and notes contain commas,

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.

• One agency publishes three realtime rows, one per entity_type: vp

names it; realtime trip ids only resolve against that specific GTFS feed.

• A realtime feed is unusable without its schedule feed. static_reference

(urls.authenticationtype 1 or 2, parameter named in urls.apikeyparametername). That credential is between the caller and the agency; it is reported so a caller knows before fetching.

• Some feeds need the CONSUMER's own credential at the transit agency

and would otherwise look like a live feed.

• redirect.id marks a superseded entry that is still present in the export

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "mobility-database": {
      "url": "https://gateway.pipeworx.io/mobility-database/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/mobility-database/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

Shortened. The full README is on GitHub.