Explore the BusMaps Transit API with an AI Assistant

The BusMaps Transit MCP Server is live. The Model Context Protocol is an open standard that connects AI assistants to external tools and data. Our public explorer lets an agent read the BusMaps API documentation, inspect schemas, and make limited live requests against validated public transit data for 90+ countries. Nobody needs to paste documentation into a chat.

What your agent can do

Read-only tools cover trip planning, live data, geography, geocoding, and all seven Voice Model-Ready methods.

On connect the agent also reads 49 self-describing resources - an overview guide, screen recipes, and a response schema plus a trimmed real example for every tool - so it knows the response shape before it makes the first call. Three prompts help build an integration plan, explain the complete API, or walk through the Voice Model-Ready methods.

Connect in one line

Claude Code:

claude mcp add --transport http busmaps-transit https://mcp.busmaps.com/mcp

Config file (Claude Desktop, Cursor, Windsurf, Cline):

{
  "mcpServers": {
    "busmaps-transit": {
      "type": "http",
      "url": "https://mcp.busmaps.com/mcp"
    }
  }
}

Full connect instructions for Gemini CLI, Codex CLI, and VS Code Copilot are on the MCP server page.

Try these prompts

• "Plan a route from central London to central Paris" - the agent calls plan_transit_route and returns a Eurostar itinerary with legs, times across two time zones, and an encoded polyline.
• "When is the next departure near Manchester Piccadilly, and is it delayed?" - get_departures returns scheduled and live predicted times.
• "Show current vehicles in central Berlin" - get_vehicle_positions_in_area returns a current position snapshot with route, direction, and timestamp.

Interactive documentation, application REST access

The hosted MCP server is a public no-key explorer with shared rate limits. It is intended for reading the documentation and testing the methods. Applications call the standard REST API or Voice Model-Ready endpoints directly with their own BusMaps API key and plan. The tools are generated from the same API contract that drives the documentation, so schemas stay aligned with the live API.

Point your agent at https://mcp.busmaps.com/mcp to explore the API. When the flow is understood and verified, get an API key for direct REST requests.