# Bart [Health: Active]

**Category:** 🚆 Travel & Transportation  
**Repository:** https://github.com/pipeworx-io/mcp-bart  
**GitHub Stars:** 0  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/bart

## Description
BART MCP — San Francisco Bay Area Rapid Transit real-time data (api.bart.gov)

## Tools
Capabilities this server exposes over MCP:

- **bart_departures** — Real-time BART San Francisco Bay Area train departures for a station — next train departure times in minutes, per destination, with platform, direction, train length (cars), line color, delay, and bikes allowed. Station accepts a 4-letter BART code ("EMBR", "SFIA") or a station name ("Embarcadero",…
- **bart_stations** — List all 50 BART San Francisco Bay Area train stations with 4-letter code, full name, city, street address, and coordinates. Optional filter matches station name or city (e.g. "Oakland", "Berkeley", "airport"). Use to find the station code for departures, trips, or fares. Example: bart_stations({ f…
- **bart_trip_planner** — Plan a BART trip between two Bay Area stations — the next trains from origin to destination with departure and arrival times, trip duration, legs (line, transfer stations, bikes), and the fare (Clipper and discount prices). Covers trips like SF to Oakland, Embarcadero to SFO airport, Berkeley to Mi…
- **bart_advisories** — Current BART service advisories and delays for the San Francisco Bay Area train system, plus elevator outage status at stations. Answers "is BART delayed right now", "are there BART service alerts", "which BART elevators are out". Example: bart_advisories({})

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "bart": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-bart"]
  }
}
```

## Documentation

## What the Bart MCP server does

The Bart MCP server connects MCP-compatible clients to San Francisco Bay Area Rapid Transit data from api.bart.gov. It is intended for questions that depend on current BART information, such as the next train from a station, the best available trip between two stations, current service disruptions, or elevator outages.

The integration is an independent, unofficial connection and is not affiliated with, endorsed by, or published by BART. It belongs in the Travel & Transportation category and focuses on BART rail data rather than general public-transit coverage.

## How it works

You can use the Bart MCP server in two ways. The hosted option connects an MCP client to `https://gateway.pipeworx.io/bart/mcp`. This scoped endpoint lists the BART tools along with shared Pipeworx meta-tools. The gateway also provides a full endpoint at `https://gateway.pipeworx.io/mcp`, where tools from the broader Pipeworx catalog are listed directly.

The local option runs `@pipeworx/mcp-bart` through standard input and output. It provides only the BART pack's tools and does not include the gateway's shared meta-tools. The same operations can also be called over HTTP through the gateway's tool endpoint without an MCP client.

## Setup and configuration

For a hosted connection, add the BART MCP URL to the client’s MCP server configuration. For a local connection, configure the server with the `npx -y @pipeworx/mcp-bart` command and no additional account or environment variable is specified in the provided setup instructions.

The gateway and standalone configurations expose different scopes. Choose the hosted endpoint if gateway routing or shared Pipeworx tools are useful; choose the local stdio package when the agent should access only the BART tools without a gateway round trip.

## Tools and capabilities

- `bart_departures` accepts a four-letter BART station code or a station name. It returns upcoming departures by destination, including departure time in minutes, platform, direction, train length, line color, delay, and whether bikes are allowed.
- `bart_stations` lists all 50 BART stations with their codes, names, cities, street addresses, and coordinates. An optional filter searches station names or cities, which helps identify codes for other requests.
- `bart_trip_planner` plans a trip between two station names or codes. Results include upcoming trains, departure and arrival times, duration, route legs, transfer stations, bike information, and Clipper and discount fares.
- `bart_advisories` returns current service advisories and delays, along with elevator outage status at stations.

Together, these tools support itinerary questions such as traveling between San Francisco and Oakland, reaching SFO, or checking whether a station elevator is unavailable.

## Limitations and notes

The data is limited to the operations exposed by the four BART tools. Station inputs can use names or four-letter codes, but ambiguous names may be easier to resolve with `bart_stations` first. The hosted endpoint may list roughly 30 shared tools in addition to the BART tools; its `initialize` response is the authoritative source for the exact scope at a given time. The integration is unofficial, and current results depend on the upstream BART data source.

_Full upstream README: https://allmcps.com/mcp/bart/readme_