Add FlightQueue (remote MCP server)

[jackculpan]

Adds servers/flightqueue/ — a remote hosted server, so no Dockerfile or image build is needed.

Endpoint	https://mcp.flightqueue.com/mcp
Transport	streamable-http
Category	travel
Docs	https://flightqueue.com
Source	https://github.com/Flight-Queue/mcp (MIT)
Maintainer	FlightQueue (Merchant Software Solutions Limited, UK company no. 14098922)

Airport security wait times and forecasts, FAA delays, EES border queues and airline baggage stats for 8,000+ airports. 22 tools; 19 work on a free account.

On the omitted oauth block

Deliberate, and it matches servers/ais-fleet and our other PRs for servers/award-travel-finder (#4834) and servers/flightseatmap. The oauth block in this repo provisions a pre-issued secret (a personal access token in an env var). We have no API key and no PAT — auth is OAuth 2.1 exactly as the MCP spec describes:

• Unauthenticated calls return an RFC 9728 WWW-Authenticate challenge pointing at /.well-known/oauth-protected-resource
• RFC 7591 dynamic client registration is supported, so there is no client ID to provision either
• Sign-in is required for this server (unlike our other two remote servers, FlightQueue does not answer any calls anonymously) — the user signs in through their browser on the first tool call

So there is nothing for the toolkit to store as a secret.

tools.json is []

Per CONTRIBUTING, remote servers use dynamic tool discovery, and dynamic.tools: true is set:

curl -s -X POST https://mcp.flightqueue.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}}'

That currently returns a spec-correct invalid_token error, confirming the endpoint is live and requires sign-in before tools/list.

🤖 Generated with Claude Code