Transit

Transit — connector documentation

• MCP endpoint: https://transit.connectorbay.com/mcp
• REST API: POST https://transit.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://transit.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: none required. An optional Authorization: Bearer <key> raises rate limits.
• Health: https://transit.connectorbay.com/health · Tool schemas: https://transit.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/transit · agent@connectorbay.com

What Transit is for

Live public-transport answers for the cities whose agencies publish keyless real-time data: is my line running, when is the next train at this station, how do I get from here to there, are there bikes at that dock, what are today's service alerts — plus a way to read any other agency's GTFS-Realtime feed.

What it does

London (Transport for London Unified API): status of every Tube, Elizabeth line, Overground, DLR and tram line with the reason for delays or closures; live arrivals at any station or stop (hubs such as King's Cross are resolved to their rail platforms), filterable by line; door-to-door journey planning with legs, times, changes and pay-as-you-go fare; Santander Cycles dock availability by name or nearest to a station. New York City (MTA): next subway trains at a station from the GTFS-Realtime trip feeds, with direction, destination and minutes; active service alerts by line. San Francisco Bay Area (BART): real-time departures with platform, direction, train length, colour line and delay; system advisories. Any agency: a GTFS-Realtime feed URL summarised — entity counts, upcoming stop times for a stop id, vehicle positions and alerts, optionally by route.

What it is not

Coverage is limited to agencies with open, keyless real-time APIs; WMATA, CTA, RATP, Delhi Metro and Mumbai local need registered keys or have no feed. Real-time predictions are the agencies' own and change by the minute; fares are TfL's adult pay-as-you-go estimate where provided. Transit does not sell tickets or hold accounts.

Tools

London

london_status — Live status of London's Tube, Elizabeth line, Overground, DLR and tram lines with the reason for any delay, closure or suspension. Use for "is the Central line running", "any tube problems right now", "Northern line status". Args: line, problems_only.

london_arrivals — Next arrivals at a London station: line, destination, platform, direction and minutes away (Tube, Elizabeth line, Overground, DLR, tram, buses). Use for "next trains from Oxford Circus", "when's the next Victoria line at King's Cross". Args: station, line, max_results.

london_journey — Plan a journey across London with TfL's journey planner: up to four options with legs (mode, line, from/to, times), total minutes, changes and the adult pay-as-you-go fare where TfL provides it. Use for "how do I get from Paddington to Canary Wharf", "fastest way to Heathrow from King's Cross at 7am tomorrow". Args: from_place, to_place, depart_at, mode.

london_bikes — Santander Cycles docking stations near a place: bikes, e-bikes and empty docks right now. Use for "any bikes near Waterloo", "where can I dock a bike at Hyde Park Corner". Args: near, max_results.

New York

nyc_subway_arrivals — Next New York City subway trains at a station from MTA's real-time feeds: line, direction (uptown/downtown), destination and minutes away. Use for "next 6 train at Union Square", "when is the next L at Bedford Av", "trains at Grand Central". Args: station, line, max_results.

nyc_subway_alerts — Current NYC subway service alerts — delays, service changes, suspensions, planned work — by line. Use for "L train alerts", "any subway delays right now", "weekend service changes on the A". Args: line, max_results.

Bay Area

bart_departures — Real-time BART departures at a station: destination, minutes, platform, direction, train length, colour line and delay. Use for "next BART from Embarcadero", "trains to SFO from Downtown Berkeley". Args: station, max_results.

bart_advisories — BART system-wide service advisories (delays, elevator outages, disruptions). Use for "any BART delays", "is BART running normally".

Anywhere

gtfs_realtime — Summarise any public GTFS-Realtime feed: entity counts, upcoming stop times (with a stop id), vehicle positions and alerts, optionally filtered by route. Use for agencies not covered natively when you know their feed URL (many publish keyless feeds). Args: url, stop_id, route_id, max_results.

coverage — Which cities and agencies Transit covers natively, what each supports, and how to use other agencies via a GTFS-Realtime feed URL.

Conventions

• Read-only. Every tool reads public data or computes; nothing is written anywhere and nothing about the user is stored.
• Result envelope. ok: true with data, or ok: false with a structured error (bad_input, not_found, upstream_error). degraded lists optional sources that were unreachable.
• Rate limits. Free tier 60 tool calls/minute and 300/day per user (keyed on the user identifier supplied by the host agent, else client IP); Pro keys raise this. Over-limit calls return HTTP 429 with Retry-After. initialize and tools/list are never counted.

Support

agent@connectorbay.com · connectorbay.com/transit/support

Transit — Privacy Policy

Effective 23 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Transit is. Transit is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for public-transport information: line status, live arrivals, journey plans, cycle-hire availability, service alerts and departures for London, New York City and the Bay Area, and summaries of GTFS-Realtime feeds. You interact with your assistant; the assistant sends us only the station, line, place names, postcode or coordinates, time and feed URL needed for the lookup.

What we receive. The arguments of each tool call (station or place names, a postcode or coordinates for journey planning, a line, a time, a feed URL), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.

Lookups are forwarded, not stored. Place names, postcodes and coordinates given for a journey are sent to Transport for London's journey planner for that request only and are not stored by us. We do not record where you travel, build a profile or retain journeys. Successful upstream answers are cached in memory for 20 seconds to 2 minutes (real-time data) or up to a day (station lists), keyed by the query.

What we do not receive or store. We do not receive your conversation with the assistant, your name, contacts, travel-card or account details. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.

Sub-processors. Transport for London (api.tfl.gov.uk), Metropolitan Transportation Authority (api-endpoint.mta.info), BART (api.bart.gov), and any agency whose GTFS-Realtime feed URL you supply. Each receives the query and our server's IP address, never yours. Hosting: Vercel (United States regions).

Legal bases and your rights. For users in California, the EU/UK and elsewhere, our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs and caches, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.

Children. Transit is a general-audience service operated by the adult using the assistant.

Changes. We will post changes here with a new effective date.

Transit — Terms of Service

Effective 23 September 2026. These terms govern use of the Transit connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Transit returns public-transport information — line status, live arrivals and departures, journey plans, cycle-hire availability, service alerts and GTFS-Realtime feed summaries — from transit agencies' open data. It is accessed through an AI assistant or directly over MCP or HTTP.
2. Sources and licences. Powered by TfL Open Data (contains OS data © Crown copyright and database rights, and Geomni UK Map data © and database rights); MTA data under the MTA developer data terms; BART data under BART's API licence; other feeds under the terms of the agency that publishes them. Agency names and marks belong to their owners; the Service is not affiliated with or endorsed by any agency.
3. Accuracy. Real-time predictions, statuses and fares are the agencies' own, change constantly and may be wrong or delayed; check departure boards before travelling and allow extra time for connections.
4. Acceptable use. Do not use the Service to poll feeds at high frequency, to bulk-scrape the sources, or to circumvent rate limits. Automated use within the published limits is welcome.
5. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
6. Data. Our Privacy Policy describes what we process. In short: your query is forwarded and nothing is stored.
7. Attribution. Transport for London; MTA; BART; the publishing agency for any other feed.
8. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
9. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including missed connections. Our total liability is limited to US $100.
10. Governing law. California law; venue in San Mateo County, California.
11. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/transit

Transit support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://transit.connectorbay.com/mcp
• REST API: https://transit.connectorbay.com/openapi.json
• Live status: https://transit.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Transit never asks for them.