Ignav Flights

Ignav runs a hosted Model Context Protocol (MCP) server that connects AI agents and assistants to live flight search with real booking links. Point any MCP client at the endpoint and it can search fares and hand users URLs that open airline and OTA checkout pages with the flight pre-selected.

The endpoint ishttps://ignav.com/mcp, using the Streamable HTTP transport. There is nothing to install or host.

- search_airports— resolve cities, airport names, and metro areas into IATA airport codes.
- search_flights— search one-way and round-trip fares. Every returned itinerary includes abooking_urlthat links directly to an airline or OTA booking page.

MCP tool calls require an Ignav account. Cloud MCP clients use OAuth, so usage belongs to the signed-in Ignav user instead of a shared cloud connector IP. Local clients can send an API key as eitherAuthorization: Bearer YOUR_API_KEYorX-Api-Key: YOUR_API_KEY. Clients that only accept a URL can send the same key with HTTP Basic auth.

Authorization: Bearer YOUR_API_KEY X-Api-Key: YOUR_API_KEY Authorization: Basic base64("ignav:YOUR_API_KEY")

MCP server URL https://ignav.com/mcp Authentication OAuth

Add a custom connector with the same MCP server URL. Claude follows the OAuth flow, asks you to connect your Ignav account, and then calls the hosted MCP server on your account's request credits.

MCP server URL https://ignav.com/mcp Authentication OAuth

Grok web custom connectors currently take a server URL. Use an Ignav API key in the URL below; Grok sends it as HTTP Basic auth, so calls stay tied to your account instead of a shared connector IP.

MCP server URL https://ignav:YOUR_API_KEY@ignav.com/mcp Authentication API key via HTTP Basic URL

SetIGNAV_API_KEYin your shell, then add the remote server with an auth header:

claude mcp add --transport http ignav https://ignav.com/mcp \ --header "Authorization: Bearer $IGNAV_API_KEY"

Codex can use Streamable HTTP MCP servers from the CLI and IDE extension. SetIGNAV_API_KEYin your environment, then add Ignav with the CLI:

codex mcp add ignav --url https://ignav.com/mcp \ --bearer-token-env-var IGNAV_API_KEY

You can also configure the same bearer token in~/.codex/config.toml:

[mcp_servers.ignav] url = "https://ignav.com/mcp" bearer_token_env_var = "IGNAV_API_KEY"

In the Codex terminal UI, run/mcpto confirm the server is active.

Add the server and bearer header to yourmcp.json:

{ "mcpServers": { "ignav": { "url": "https://ignav.com/mcp", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } }

Any other MCP client that supports remote HTTP servers works the same way — point it athttps://ignav.com/mcpand use OAuth if the client supports MCP OAuth, or send a bearer token /X-Api-Keyheader. If the client only accepts a URL, usehttps://ignav:YOUR_API_KEY@ignav.com/mcp.

To use MCP,create a free accountand connect with OAuth or send an API key. MCP calls are billed as normal API usage: 1,000 free successful requests included, then$2.00 per 1,000 successful requestswith no minimums. Only successful requests are billed.

Integrate with the Amazon Product Advertising API to search for products and access product information.