Airffic Architect

Accounts and assistants

One engine, three clients.

Claude, Grok, and ChatGPT call the same operations as the workspace. Remote MCP uses OAuth. OpenAPI actions use a bearer key.

Account

Checking this browser…

Claude

Add a custom connector with the remote MCP URL. Claude registers itself and sends you to the consent page on this site. Local Claude Desktop can still use stdio.

MCP URL ends in /mcp

Grok

Point a remote MCP client at the same URL, or call the OpenAPI operations as tools. A personal afa_ key works as Authorization: Bearer when the client asks for a header instead of OAuth.

ChatGPT

Import /openapi.json as a GPT action. Choose API key header X-API-Key or bearer auth. The action calls the same routes as the workspace.

When this server is connected to the shared Airffic project, sign-in is that account. Otherwise this page keeps a development directory on the server.

Commands for each client are in the repository file docs/connecting-ai-clients.md. Set AIRFFIC_MCP_AUTH=required before the MCP port is reachable from the internet. How this service attaches to the shared platform is in docs/platform-integration.md.