How to connect Bart to OpenClaw
Connect Bart to OpenClaw with ClawLink: paste your Bart key once and 18 tools work from chat. No MCP server to run, nothing stored on your machine.
BartAPI KEYMCPBART (Bay Area Rapid Transit) provides public transportation services in the San Francisco Bay Area.. Once connected, OpenClaw can read and act on Bart from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Bart access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Bart setup: install one ClawHub skill, connect Bart in the browser, and OpenClaw can call real Bart actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Bart.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Bart
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Bart?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Bart in the ClawLink dashboard — paste your Bart API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Bart, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Bart is connected in the dashboard, that agent calls the same 18 Bart tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Bart MCP for OpenClaw
Looking for a Bart MCP server for OpenClaw? ClawLink connects Bart to OpenClaw and exposes 18 Bart tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Bart integration works the same way.
What the OpenClaw Bart integration can do
18 Bart tools are ready for OpenClaw once the account is connected.
All 18 Bart tools for OpenClaw
| Tool | What it does |
|---|---|
Get API version bart_get_api_version | Get the current version of the BART API |
Get elevator status bart_get_elevator_status | Fetch current elevator status across all BART stations |
Get estimated departures bart_get_estimated_departures | Get real-time estimated departure times for a specified BART station |
Get fare bart_get_fare | Get fare information between two BART stations including Clipper and cash prices |
Get gtfs alerts bart_get_gtfs_alerts | Fetch GTFS-RT service alerts in protobuf format for integration with GTFS static feed |
Get gtfs rt trip updates bart_get_gtfs_rt_trip_updates | Fetch real-time trip updates in GTFS-Realtime format |
Get gtfs static schedule feed bart_get_gtfs_static_schedule_feed | Downloads the BART static GTFS (General Transit Feed Specification) schedule feed as a ZIP |
Get route info bart_get_route_info | Fetch detailed information about a specific BART route |
Get route schedule bart_get_route_schedule | Get detailed schedule information for a specific BART route showing all trains and their stops |
Get schedule arrive bart_get_schedule_arrive | Retrieve schedule information based on a specified arrival time |
Get schedule depart bart_get_schedule_depart | Get BART train schedules departing from an origin station to a destination station at a |
Get service advisories bart_get_service_advisories | Fetch current BART service advisories |
Get station access bart_get_station_access | Get comprehensive station access information including parking, transit, bike facilities, and |
Get station info bart_get_station_info | Get detailed information for a specific BART station by its abbreviation code |
Get station schedule bart_get_station_schedule | Get detailed scheduled departure information for a specific BART station |
Get stations bart_get_stations | Get a list of all BART stations with their complete information |
Get train count bart_get_train_count | Fetch current count of trains active in the BART system |
List routes bart_list_routes | Get a list of all current BART routes/lines with basic information |
Try it: find the Bart tool you need
Browse the 18 Bart tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Bart, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Bart, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Bart, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Bart, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Bart working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Bart API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Bart account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Bart. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Bart actions to the runtime in a format your agent can reliably use. | 18 tools for Bart are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Bart to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Bart in the browser, and the 18 tools above work from chat. There is no SDK and no config file, and the Bart key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Bart skill but can't call the tools
The ClawHub skill teaches OpenClaw about Bart, but the calls run through the ClawLink plugin and your connected account. Make sure Bart is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Bart from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Bart tools
Bart tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Bart call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Bart returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Bart has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Bart integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Bart: link your Bart account once in the browser and OpenClaw can call the Bart API through 18 ready-made tools — no custom code or token handling.
How do I add Bart to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Bart skill from ClawHub, then you click Connect in the dashboard to authorize Bart. OpenClaw calls the tools from the next message — no config files, and the Bart key you paste is stored server-side instead of in your environment.
How long does it take to connect Bart to OpenClaw?
About two minutes. Sign in, click Connect next to Bart in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Bart up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Bart working from chat.
OpenClaw installed the Bart skill but can't call the tools
The ClawHub skill teaches OpenClaw about Bart, but the calls run through the ClawLink plugin and your connected account. Make sure Bart is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
GitHub tools
Manage repositories, issues, pull requests, and workflows
PagerDuty tools
Manage incidents, on-call schedules, and services
SafetyCulture
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.