Scheduling & Booking · Bart + Claude
Bart MCP with Claude: Live Transit Schedules and Route Planning for Operations Teams
The short answer
Claude works with Bart through the Model Context Protocol, an open standard that lets Claude securely use other software. Once connected with an API key, Claude can fetch train schedules, read live service alerts, plan multi-leg routes and check station information, all through natural language requests from your team.
What is Bart?
Bart is the Bay Area Rapid Transit system, a public rail network serving the San Francisco Bay Area. It provides fast public transportation for commuters and travellers. Its published data covers train schedules, station information and service updates, which helps riders plan journeys and stay informed about changes to service.
How Claude connects to Bart through MCP
The Model Context Protocol is an open standard that acts like a universal adapter between Claude and other software. It lets Claude use a tool securely, reading information and taking actions with permissions your organisation controls. For Bart, the connection uses an API key, so access is granted deliberately rather than shared broadly.
Once connected, Claude can read train schedules, check live service alerts, plan routes across several legs and look up station details. Your team can ask questions in everyday language, such as which route gets a visitor from the airport to a downtown office fastest, and receive a clear answer drawn from current data.
Permissions and approvals keep people in charge. We grant least-privilege access, limiting Claude to the read functions your workflow needs. Where a result will drive a decision, such as notifying customers of a disruption, a person reviews and approves the action before it goes out.
What you can automate
Live Disruption Alerts for Staff
Operations teams often need to know quickly when a line is affected. Claude can check Bart's live service alerts on a set schedule and summarise anything relevant to your sites. Staff receive a short, plain-English briefing, so they can adjust shift start times or warn colleagues before the morning rush.
Travel Desk Route Planning
Travel coordinators regularly arrange journeys for visiting clients and staff. Claude can plan multi-leg routes between stations and airports, compare options and present the quickest combination with approximate timings. The coordinator reviews the suggestion and then adds it to the itinerary, saving time on manual lookups.
Facilities and Office Information
Facilities teams field frequent questions from employees about getting to the office by public transport. Claude can look up nearby station details and typical schedules, then draft a clear travel guide for new starters. The guide is updated when station information changes, keeping onboarding material accurate.
Customer Service Responses
Hospitality and event businesses often receive questions about transit access. Claude can answer common enquiries about schedules and station locations in natural language, drawing on current data. Responses are drafted for a team member to check before sending, so guests receive accurate, timely guidance.
Commuter Support for Field Teams
Field service and sales teams travel between sites across the Bay Area. Claude can plan routes that link several stations and suggest alternatives when service is disrupted. Dispatchers receive a short summary they can share with engineers, reducing late arrivals at client sites.
An end-to-end workflow: Morning Disruption Briefing for a Field Services Team
TriggerEvery weekday at 6:30 a.m., before the first dispatch of the day.
Claude checks Bart's live service alerts for lines serving the team's job sites.
Claude reads the scheduled jobs for the day from the team's scheduling system.
Claude identifies which engineers travel by affected routes and plans alternative multi-leg journeys.
Claude drafts a short briefing listing disruptions, affected jobs and suggested routes.
A dispatcher reviews the briefing and approves it before it is sent to the team by e-mail.
OutcomeEngineers start the day with a clear, approved plan, so fewer appointments are missed. Typical results include shorter dispatcher preparation time and fewer late arrivals, though outcomes vary by organisation.
How we set it up
Free Automation Audit
We review how your team currently checks transit information and plans journeys, and identify the workflows worth automating. You receive a clear recommendation at no cost.
Secure Connection
We connect Claude to Bart using an API key, stored securely and granted only the read permissions your workflow requires.
Workflow Design
We design the end-to-end workflow across Bart and your other systems, such as Microsoft 365, your CRM or ticketing tool, with people approving any consequential actions.
Testing Against Real Cases
We test the workflow against real past journeys and disruptions to confirm the outputs are accurate and useful before anything goes live.
Launch, Monitoring and Training
We launch with monitoring and audit logs, then train your team to use and review the workflow confidently.
Who benefits
- Operations Managers
- Receive timely, plain-English briefings on disruptions that could affect staff and deliveries.
- Travel and Office Coordinators
- Plan multi-leg journeys faster and present clear options to colleagues and visitors.
- Dispatch and Field Service Leads
- Protect appointment schedules with daily route checks and early warnings.
- IT and Department Heads
- Gain a controlled, auditable connection to transit data with clear permissions.
Security and control
- Access is limited to read functions required by the workflow, following least-privilege principles.
- The API key is stored securely and can be rotated or revoked at any time.
- People approve any action that affects customers, staff or payments before it happens.
- Audit logs record what Claude accessed and when, supporting internal review.
- Route suggestions are indicative and should be checked against official Bart information before critical decisions.
For teams in the US, UK, India and the Middle East
Organisations in the United States, the United Kingdom, India and the Middle East each have different data protection requirements. In the United States, state privacy laws apply, while the United Kingdom follows UK GDPR. India's Digital Personal Data Protection Act, 2023 governs personal data, and the UAE and Saudi Arabia each have their own data protection laws. We choose the hosting region for your deployment to help meet these requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Bart MCP server do?
The Bart MCP server acts as a secure bridge between Claude and Bart's transit information. It lets Claude fetch train schedules, read live service alerts, plan multi-leg routes and check station details. Your team can then request this information in plain language, and Claude returns answers based on current data.
Is connecting Bart to Claude secure?
Yes, when set up correctly. The connection uses an API key, which we store securely and restrict to the read permissions your workflow needs. Audit logs record activity, and people approve any consequential action. We never guarantee compliance outcomes, but we design each connection around least-privilege access.
What can Claude actually do with Bart?
Claude can read train schedules, check live service alerts, plan routes that combine several legs, and look up station information. It can summarise these results, answer questions in everyday language and draft messages for your team. Claude does not change Bart's systems or services.
How long does setup take?
Timelines depend on how many workflows you want and how they connect to your other systems. A focused single workflow often takes a few weeks from the free automation audit to launch, including testing and team training. We confirm a realistic schedule during the audit.
Which plan or permissions do I need?
Generally, you need an API key from Bart with access suited to your use case, along with the Claude access your organisation already uses. We confirm the exact requirements during the free audit, so you know what to prepare before the build begins.