get_nearby_events — commutescout MCP Tool Read-only
get_nearby_events
(get nearby events) is one of 10 tools on the
commutescout
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_nearby_events from your client
- Claude Code commutescout get_nearby_events run in your project directory
- Claude Desktop commutescout get_nearby_events ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor commutescout get_nearby_events ~/.cursor/mcp.json
- VS Code commutescout get_nearby_events .vscode/mcp.json
- Zed commutescout get_nearby_events ~/.config/zed/settings.json
- Windsurf commutescout get_nearby_events ~/.codeium/windsurf/mcp_config.json
- Cline commutescout get_nearby_events ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI commutescout get_nearby_events ~/.gemini/settings.json
- Grok commutescout get_nearby_events .mcp.json (in your project root)
- ChatGPT commutescout get_nearby_events Settings → Connectors → Advanced → Developer mode
- Claude.ai commutescout get_nearby_events Settings → Connectors → Add custom connector
- LangChain commutescout get_nearby_events pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http commutescout https://mcp.commutescout.com/mcpOther tools on this server
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.