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