find_warm_destinations — decidewhere.to MCP Tool Read-only
find_warm_destinations
(find warm destinations) is one of 6 tools on the
decidewhere.to
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call find_warm_destinations from your client
- Claude Code decidewhere.to find_warm_destinations run in your project directory
- Claude Desktop decidewhere.to find_warm_destinations ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor decidewhere.to find_warm_destinations ~/.cursor/mcp.json
- VS Code decidewhere.to find_warm_destinations .vscode/mcp.json
- Zed decidewhere.to find_warm_destinations ~/.config/zed/settings.json
- Windsurf decidewhere.to find_warm_destinations ~/.codeium/windsurf/mcp_config.json
- Cline decidewhere.to find_warm_destinations ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI decidewhere.to find_warm_destinations ~/.gemini/settings.json
- Grok decidewhere.to find_warm_destinations .mcp.json (in your project root)
- ChatGPT decidewhere.to find_warm_destinations Settings → Connectors → Advanced → Developer mode
- Claude.ai decidewhere.to find_warm_destinations Settings → Connectors → Add custom connector
- LangChain decidewhere.to find_warm_destinations pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http group-decisions https://decidewhere.to/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 27 October 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.