get_bus_stops — Transit MCP MCP Tool Read-only
get_bus_stops
(get bus stops) is one of 18 tools on the
Transit MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_bus_stops from your client
- Claude Code Transit MCP get_bus_stops run in your project directory
- Claude Desktop Transit MCP get_bus_stops ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Transit MCP get_bus_stops ~/.cursor/mcp.json
- VS Code Transit MCP get_bus_stops .vscode/mcp.json
- Zed Transit MCP get_bus_stops ~/.config/zed/settings.json
- Windsurf Transit MCP get_bus_stops ~/.codeium/windsurf/mcp_config.json
- Cline Transit MCP get_bus_stops ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Transit MCP get_bus_stops ~/.gemini/settings.json
- Grok Transit MCP get_bus_stops .mcp.json (in your project root)
- ChatGPT Transit MCP get_bus_stops Settings → Connectors → Advanced → Developer mode
- Claude.ai Transit MCP get_bus_stops Settings → Connectors → Add custom connector
- LangChain Transit MCP get_bus_stops pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http transit-mcp https://transitmcp.com/mcpOther tools on this server
- get_station_predictions
- search_stations
- get_stations_by_line
- get_all_stations
- get_station_transfers
- get_incidents
- get_elevator_incidents
- get_bus_predictions
- get_bus_routes
- get_bus_positions
- get_train_positions
- get_route_info
- find_transit
- plan_trip
- get_departures
- get_service_status
- get_vehicle_status
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.