Transitland MCP Server

Purpose: Accessing and querying global public transit data through an MCP-compatible server.

Inferred · not functionally tested

Audience: developers building transit and mobility applications

Inferred · not functionally tested

Functions: data_extraction

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: Open Source · platforms: API, WEB · deployment: browser, self_hosted, cli, api_only

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: github.com. These links do not verify the individual claims.

In the Frameworks & SDKs space, Transitland MCP Server takes a focused approach. Inferred · not functionally tested: It focuses on accessing and querying global public transit data through an MCP-compatible server. Inferred · not functionally tested: It is built as an open-source project for developers building transit and mobility applications. Basis unknown · not verified: Transitland MCP Server is open source under the Open Source license. Basis unknown · not verified: It ships for the web, the command line, and API, and it can be self-hosted.

cyanheads builds and maintains Transitland MCP Server. Inferred · not functionally tested: Among its 6 catalogued features are operator lookup, GTFS feeds, and GTFS-RT feeds. Inferred · not functionally tested: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.