SF Muni Real-Time Transit

About SF Muni Real-Time Transit

Use SF Muni Real-Time Transit with your agent

claude mcp add --transport http sf-muni-real-time-transit https://muni-mcp.srivastsh.workers.dev/mcp --header "x-api-key-511: {$apiKey}"

{
  "mcpServers": {
    "sf-muni-real-time-transit": {
      "url": "https://muni-mcp.srivastsh.workers.dev/mcp",
      "headers": {
        "x-api-key-511": "{$apiKey}"
      }
    }
  }
}

Frequently asked questions

What is SF Muni Real-Time Transit?

SF Muni Real-Time Transit is an MCP (Model Context Protocol) server by srivastsh in the Monitoring category. Real-time SF Muni departures, routes, alerts, vehicle positions, and schedules.

How do I connect SF Muni Real-Time Transit to Claude, Cursor, or another MCP client?

SF Muni Real-Time Transit is a remote MCP server — add its endpoint (https://muni-mcp.srivastsh.workers.dev/mcp) to your client's MCP configuration (for example with "claude mcp add", or under "mcpServers" in Cursor's mcp.json) and restart the client.

Is SF Muni Real-Time Transit open source?

Yes — the source code is public at github.com/srivastsh/bay-area-transit-mcp.

Can AI agents pay to use SF Muni Real-Time Transit?

Not yet through Loomal — SF Muni Real-Time Transit is listed as a free directory entry. If its maintainer verifies ownership, they can set per-call USDC pricing that agents pay over x402, with settlement on Base.