mobilitydb_feed

Pack: mobility-database · Endpoint: https://gateway.pipeworx.io/mobility-database/mcp

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/mobilitydb_feed for the schema, then POST the same URL with its arguments for the data.

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, licence, contact, bounding box, declared GTFS features, publication status, and — for a realtime feed — the GTFS Schedule feed it is keyed against, plus every sibling realtime stream the same agency publishes.

Parameters

NameTypeRequiredDescription
feed_idstringyesMobility Database feed id, e.g. mdb-1210. Shown as id by mobilitydb_search_feeds.

Example call

Arguments

{
  "feed_id": "mdb-53"
}

curl

curl -X POST https://gateway.pipeworx.io/mobility-database/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"mobilitydb_feed","arguments":{"feed_id":"mdb-53"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('mobilitydb_feed', {
  "feed_id": "mdb-53"
});

More examples

{
  "feed_id": "mdb-1602"
}

Connect

Add this to your MCP client config, or use one-click install buttons:

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

See Getting Started for client-specific install steps.

Regenerated from source · build September 18, 2026