Log inSubmit server
Bart logo

Bart

Access real-time BART departures, station data, trip plans, fares, advisories, delays, and elevator outages through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Bart

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "bart": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-bart"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The Bart MCP server exposes San Francisco Bay Area Rapid Transit data through MCP tools for departures, stations, trip planning, fares, advisories, and elevator outages. It can connect through the Pipeworx gateway over a remote MCP URL or run locally as a stdio server with npx. Use it when an agent needs current BART information for a station, route, or service-status question.

Use cases

  • Check the next BART departures from a station
  • Find station codes by city or station name
  • Plan a BART trip with transfers and fares
  • Check current BART delays and service advisories
  • Identify station elevator outages

Key features

  • Real-time station departures
  • BART station directory with coordinates
  • Trip planning with fares and transfers
  • Service advisories and delay status
  • Elevator outage information
  • Hosted or local stdio deployment

Tools4

What Bart lets your agent do. Expand a tool for its parameters.

Self-reported~305 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 46d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · @pipeworx/mcp-bart (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit3d agoMost recent push to the default branch.
Tools exposed4Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Bart works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Bart

Bart is an MCP server that connects AI clients to San Francisco Bay Area Rapid Transit data through the BART API. It provides bart_departures, bart_stations, bart_trip_planner, and bart_advisories for real-time departures, station lookup, trip planning, fares, service status, delays, and elevator outages.

Run it locally with `npx -y @pipeworx/mcp-bart` and configure that command as an MCP server.

Yes, Cursor is named as a supported MCP client in the setup instructions. Add `https://gateway.pipeworx.io/bart/mcp` to Cursor for the hosted connection, or configure the local `npx` command for a standalone stdio connection.

Call `bart_departures` with a station name or four-letter station code, such as `Embarcadero` or `EMBR`. The result includes upcoming trains by destination with timing, platform, direction, train length, line color, delay, and bike information.

Yes, `bart_trip_planner` plans travel between two BART stations and returns upcoming trains, departure and arrival times, duration, route legs, transfers, bike information, and Clipper and discount fares.

Related MCP servers

All in Travel & Transportation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewBart AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/bart?style=directory)](https://allmcps.com/mcp/bart)
HTML Embed
<a href="https://allmcps.com/mcp/bart"><img src="https://allmcps.com/api/badge/bart?style=directory" alt="Bart on AllMCPs" /></a>