Flight Recovery Mcp

v1.0.0

A powerful MCP server built with NitroStack

Connection Setup

Add via Cursor Settings UI (Settings > Features > MCP > Add New MCP Server): 

{
  "mcpServers": {
    // your other mcp servers
    "flight-recovery-mcp": {
      "url": "http://flight-recovery-6ad4c09d-dhoni-heapify-global-community.app.nitrocloud.ai/mcp"
    }
  }
}

Connect remote tools directly via Claude's Web UI:

Add custom connector BETA
Connect Claude to your data and tools. Learn more about connectors or get started with pre-built ones.
Advanced settings
Only use connectors from developers you trust. Anthropic does not control which tools developers make available and cannot verify that they will work as intended or that they won't change.
Building an MCP server? Report issues and subscribe to updates here

Configure custom tools directly via ChatGPT's Web UI:

New App
Icon (optional)
PNG only. Best results at 256 x 256 px or larger. Max file size: 10 KB
Name
Description (optional)
Connection
Authentication
Custom MCP servers introduce risk. Learn more
OpenAI hasn't reviewed this MCP server. Attackers may attempt to steal your data or trick the model into taking unintended actions, including destroying data.
Read the guide

Add the following configuration block under mcpServers in your Antigravity configuration file (~/.gemini/config/mcp_config.json): 

{
  "mcpServers": {
    // your other mcp servers
    "flight-recovery-mcp": {
      "serverUrl": "http://flight-recovery-6ad4c09d-dhoni-heapify-global-community.app.nitrocloud.ai/mcp"
    }
  }
}

Add the following configuration block to your Codex configuration file (~/.codex/config.toml): 

[mcp_servers.flight-recovery-mcp]
url = "http://flight-recovery-6ad4c09d-dhoni-heapify-global-community.app.nitrocloud.ai/mcp"

Connect directly using the Server-Sent Events endpoint: 

http://flight-recovery-6ad4c09d-dhoni-heapify-global-community.app.nitrocloud.ai/mcp
Available Tools
assess_disruption

STEP 1. Returns the status of a flight (cancelled or delayed), cause, and times. Call first when the user reports a disrupted flight.

map_blast_radius

STEP 2. Checks the traveller's commitments (client dinner, hotel late check-in, meeting) against the flight's status. If another tool (e.g. a calendar) provides the real meeting/dinner time, pass it in these optional fields. Call after assess_disruption.

rank_alternates

STEP 3. Ranks three replacement flights, shows what each keeps or loses, and returns one recommended option. Default: protect_meeting. Use earliest_arrival or lowest_cost ONLY if the user explicitly asks for the fastest or cheapest option. If another tool (e.g. a calendar) provides the real meeting/dinner time, pass it in these optional fields. Call after map_blast_radius.

plan_recovery

STEP 4. Returns specific ordered proposed actions for the recommended or chosen replacement flight. Default: protect_meeting. Use earliest_arrival or lowest_cost ONLY if the user explicitly asks for the fastest or cheapest option. If another tool (e.g. a calendar) provides the real meeting/dinner time, pass it in these optional fields. Proposals only; nothing is executed. Call last.