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