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