Cursor onebusaway mcp server onebusaway_get_schedule_for_stop
How to: Cursor onebusaway mcp server onebusaway_get_schedule_for_stop
Add onebusaway mcp server to Cursor
-
01
Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"onebusaway-mcp-server": {
"url": "https://onebusaway.caseyjhand.com/mcp"
}
}
}-
02
Save the file and restart Cursor.
-
03
Ask for something onebusaway_get_schedule_for_stop does. Cursor lists the server's tools on connect and calls onebusaway_get_schedule_for_stop itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that onebusaway mcp server's identifier in your config matches the one above exactly.
Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs
Set these first
onebusaway mcp server will not start until these are set, so onebusaway_get_schedule_for_stop never becomes available.
-
ONEBUSAWAY_API_KEY -
ONEBUSAWAY_BASE_URL -
ONEBUSAWAY_RATE_LIMIT_REQUESTS -
ONEBUSAWAY_RATE_LIMIT_WINDOW_MS -
ONEBUSAWAY_RATE_LIMIT_MAX_WAIT_MS -
MCP_LOG_LEVEL
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.