seats.aero

The seats.aero MCP server is a TypeScript-based tool that connects to the seats.aero API so you can query flights, availability, and routes from any MCP client (such as Claude Desktop) using natural language or scripted commands. It exposes a small set of capabilities that mirror the seats.aero API endpoints, making it possible to fetch flight lists, bulk availability data, and route information through familiar MCP commands. You will need a seats.aero Pro API key to use the feature set effectively. The server is designed to be run locally and integrated with your MCP client configuration, so you can issue queries in natural language and receive structured results.

To use the server, configure your MCP client to point to the local Node.js process (as shown in the example config) and provide your seats.aero API key via the SEATS_API_KEY environment variable. Once running, you can invoke commands like get_flights, get_bulk_avail, and get_routes through your client, which will relay requests to the seats.aero API and return results in a consumable format.

Prerequisites:

• Node.js installed on your system
• pnpm installed (optional but used by the project)
• seats.aero Pro API key for actual usage

Installation steps:

1. Install dependencies
   • pnpm i
2. Build the TypeScript project
   • pnpm build
3. Start the MCP server
   • pnpm start

Configuration:

• Create or modify your claude_desktop_config.json (or equivalent MCP client config) to point to the server, for example: { "seats": { "command": "node", "args": ["/Users/USER/Sites/seats-mcp/build/index.js"], "env": { "SEATS_API_KEY": "SEATS_API_KEY" } } }

Notes:

• Replace "/Users/USER/Sites/seats-mcp/build/index.js" with the actual path to your built server if different.
• Ensure SEATS_API_KEY is set in your environment or via your MCP client configuration for authentication.

Tips and common issues:

• You must have a valid seats.aero Pro API key to use the commands effectively.
• The MCP server relies on the built index.js; ensure you run a fresh build after code changes.
• If the server fails to start, check that the Node.js version is compatible with the built output and that the path to index.js is correct.
• Your MCP client config should include the SEATS_API_KEY in the env section to pass authentication.
• The tools mirror seats.aero endpoints (for example, the cached search, bulk availability, and routes endpoints), so behavior and parameters align with the seats.aero API documentation.