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