Official MCP setup · no JavaScript required
The Fly MCP: connect your client
Full MCP endpoint: https://mcp.thefly.com/mcp. Transport: Streamable HTTP. Preferred API-key header: X-API-Key: <MCP API key>. The full endpoint also accepts Authorization: Bearer <MCP API key>; send only one credential header. Never put credentials in the URL.
Read the complete agent setup guide, plain-text discovery index, or machine-readable manifest. These public guides do not require a key or sign-in.
Choose the correct setup
Claude web / native Desktop connector: use https://mcp.thefly.com/mcp with OAuth. Leave Advanced OAuth Client ID and Client Secret blank. Complete human sign-in and consent; do not paste an MCP key into those fields.
Claude Code and header-capable clients: use X-API-Key. Existing The Fly users should sign in and use their developer keys. New standalone agent accounts require explicit approval and do not inherit a human subscription.
ChatGPT app: https://mcp.thefly.com/chatgpt/mcp, OAuth only, compact read-only profile. Do not use an API key.
Claude Code example
Merge into .mcp.json only after approval. Keep the placeholder literal and supply THEFLY_MCP_API_KEY through the approved local environment or secret store, not chat or source control.
{
"mcpServers": {
"thefly": {
"type": "http",
"url": "https://mcp.thefly.com/mcp",
"headers": {
"X-API-Key": "${THEFLY_MCP_API_KEY}"
}
}
}
}
Verify and recover
Complete the normal MCP initialize handshake and tools/list. With approval, run a read-only symbol lookup. Do not modify watchlists or personal settings during setup.
Consent/CSRF error? Start a fresh authorization from the client in the same browser; do not refresh or resubmit the failed page. Never disable CSRF protection. If it persists, collect only client/browser, time/time zone and the error—not login URLs, cookies, keys or browser-log exports.