Connect your client

Every client connects to the same server:

https://mcp.airframe.ai/mcp

• Transport: Streamable HTTP
• Authentication: OAuth 2.1 with dynamic client registration. Your client discovers the sign-in page on its own; you don't need a client ID or secret.
• Server name: use airframe wherever a client asks for one.

Adding the server to a client doesn't sign you in. Each section below ends with how to start sign-in. You need an Airframe account; if you've never signed in at airframe.ai, do that once first.

Chat apps: Claude · ChatGPT · Microsoft Copilot Studio · Mistral Le Chat · Perplexity

Coding agents: Claude Code · Codex · Gemini CLI · Antigravity CLI · opencode · Goose · JetBrains Junie

Editors: Cursor · VS Code and GitHub Copilot · Devin Desktop (Windsurf) · Zed · Cline · JetBrains AI Assistant

Everything else: Other clients

Chat appsCopy Anchor Link

ClaudeCopy Anchor Link

Works in claude.ai, Claude Desktop, Cowork, and the Claude mobile apps. Once connected, the connector is available everywhere you use Claude.

Pro and Max

1. Open Customize → Connectors and search the directory for Airframe, then select Connect.
2. If Airframe isn't listed for you, select Add → Add custom connector, enter the name airframe and the server URL, then select Add.
3. Sign in with your Airframe account and approve access.

Team and Enterprise

An organization Owner adds the connector once in Organization settings → Connectors. Each member then opens Customize → Connectors, finds Airframe, and selects Connect to sign in with their own Airframe account.

To use it in a chat, select + → Connectors and make sure Airframe is on. For a consistent brief and battlecard format, also install the Claude plugin.

ChatGPTCopy Anchor Link

1. Go to chatgpt.com/plugins and select + → Add custom MCP server.
2. Name it Airframe, add a short description, and enter the server URL under Connection.
3. Choose OAuth for authentication, confirm the prompt, and select Create as a plugin.
4. Install the plugin, then in a new chat type @ and choose Airframe. ChatGPT opens Airframe's sign-in page the first time.

Availability depends on your ChatGPT plan and workspace settings. In Enterprise workspaces, an admin controls custom MCP servers under Workspace settings → Permissions & roles.

Microsoft Copilot StudioCopy Anchor Link

1. Open your agent and go to Tools → Add a tool → New tool → Model Context Protocol.
2. Enter the server name airframe, a description, and the server URL.
3. Choose OAuth 2.0, then Dynamic discovery, and select Create.
4. Select Next → Create a new connection, sign in with your Airframe account, and select Add to agent.

Your Power Platform data policies apply.

Mistral Le ChatCopy Anchor Link

An admin adds custom connectors. On Free, Pro, and Student plans, the account owner is the admin.

1. Open Connectors → + Add Connector and choose the Custom MCP Connector tab.
2. Enter the name airframe (no spaces) and the server URL, then select Connect.
3. Le Chat detects OAuth and walks you through Airframe's sign-in.

PerplexityCopy Anchor Link

1. Open Customize → Connectors (or Plugins in the sidebar) and choose Add custom → Connector → Add MCP connector → Remote.
2. Enter the name airframe and the server URL, set Auth to OAuth and Transport to Streamable HTTP, and accept the acknowledgement.
3. Select the Airframe connector card to sign in.

In Enterprise organizations, an admin adds custom connectors under Enterprise settings → Permissions → Connectors, and may need to turn on Allow members to add custom connectors.

Coding agentsCopy Anchor Link

Claude CodeCopy Anchor Link

The Claude plugin installs the connector and the company-research skill together:

/plugin install airframe --marketplace airframeai/claude-plugin

To add only the connector:

claude mcp add --transport http airframe https://mcp.airframe.ai/mcp

Add --scope user to make it available in every project, or --scope project to write it to the repository's .mcp.json:

{
  "mcpServers": {
    "airframe": { "type": "http", "url": "https://mcp.airframe.ai/mcp" }
  }
}

Sign in: run /mcp in Claude Code, choose airframe, and finish in the browser. From a shell, claude mcp login airframe does the same.

CodexCopy Anchor Link

Works in the Codex CLI, the Codex IDE extension, and the ChatGPT desktop app, which share one configuration.

codex mcp add airframe --url https://mcp.airframe.ai/mcp
codex mcp login airframe

Or add it to ~/.codex/config.toml:

[mcp_servers.airframe]
url = "https://mcp.airframe.ai/mcp"

Sign in: codex mcp login airframe opens the browser. In the desktop app or IDE extension, go to Settings → MCP servers → Add server, choose Streamable HTTP, enter the URL, restart, and select Authenticate.

Gemini CLICopy Anchor Link

gemini mcp add --transport http airframe https://mcp.airframe.ai/mcp

Or add it to ~/.gemini/settings.json. Use httpUrl; url means the older SSE transport:

{
  "mcpServers": {
    "airframe": { "httpUrl": "https://mcp.airframe.ai/mcp" }
  }
}

Sign in: run /mcp auth airframe. Gemini CLI needs a local browser for the OAuth callback.

Antigravity CLICopy Anchor Link

Add it to ~/.gemini/config/mcp_config.json, or .agents/mcp_config.json in a project. Antigravity uses serverUrl and rejects url and httpUrl:

{
  "mcpServers": {
    "airframe": { "serverUrl": "https://mcp.airframe.ai/mcp" }
  }
}

Sign in: open Agent settings → Customizations, select Authenticate next to airframe, sign in in the browser, and paste the code back.

opencodeCopy Anchor Link

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "airframe": {
      "type": "remote",
      "url": "https://mcp.airframe.ai/mcp",
      "enabled": true
    }
  }
}

Sign in: run opencode mcp auth airframe. opencode mcp list shows the connection status.

GooseCopy Anchor Link

Or run goose configure → Add Extension → Remote Extension (Streamable HTTP), or add it to ~/.config/goose/config.yaml:

extensions:
  airframe:
    name: Airframe
    type: streamable_http
    uri: https://mcp.airframe.ai/mcp
    enabled: true
    timeout: 300

Sign in: Goose opens the browser for OAuth when it first connects.

JetBrains JunieCopy Anchor Link

Add it to .junie/mcp/mcp.json in a project, or ~/.junie/mcp/mcp.json:

{
  "mcpServers": {
    "airframe": { "url": "https://mcp.airframe.ai/mcp" }
  }
}

Sign in: the server shows Authorization required. Open /mcp, select airframe, choose Authorize, and sign in in the browser.

EditorsCopy Anchor Link

CursorCopy Anchor Link

Or add it to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "airframe": { "url": "https://mcp.airframe.ai/mcp" }
  }
}

Sign in: Cursor shows the server as needing login. Select it to open Airframe's sign-in page. In the Cursor CLI, run agent mcp login airframe.

VS Code and GitHub CopilotCopy Anchor Link

Requires VS Code 1.99 or later with Copilot agent mode. Or add it to .vscode/mcp.json, or your user configuration with MCP: Open User Configuration:

{
  "servers": {
    "airframe": { "type": "http", "url": "https://mcp.airframe.ai/mcp" }
  }
}

Sign in: VS Code opens the browser the first time it starts the server. Manage the sign-in from the Accounts menu.

On Copilot Business and Enterprise, an organization admin must turn on the MCP servers in Copilot policy first. It's off by default.

Devin Desktop (Windsurf)Copy Anchor Link

Windsurf is now Devin Desktop. Open the Cascade panel's … menu, choose Open MCP config file, and add:

{
  "mcpServers": {
    "airframe": { "serverUrl": "https://mcp.airframe.ai/mcp" }
  }
}

On Windows the file is %APPDATA%\devin\mcp_config.json. Enterprise users may need to turn MCP on, and team admins can restrict servers to an allowlist.

ZedCopy Anchor Link

Open Settings → AI → MCP Servers → Add Server → Add Remote Server, or add it to settings.json:

{
  "context_servers": {
    "airframe": { "url": "https://mcp.airframe.ai/mcp" }
  }
}

Sign in: Zed prompts you to authenticate when it connects.

ClineCopy Anchor Link

Open MCP Servers → Remote Servers, choose Streamable HTTP, enter the server URL, and select Add Server. Or add it to cline_mcp_settings.json:

{
  "mcpServers": {
    "airframe": { "type": "streamableHttp", "url": "https://mcp.airframe.ai/mcp" }
  }
}

Keep "type": "streamableHttp"; without it, Cline falls back to the older SSE transport. If sign-in doesn't start, use the mcp-remote bridge.

JetBrains AI AssistantCopy Anchor Link

Open Settings → Tools → AI Assistant → Model Context Protocol (MCP) and add a server with this configuration:

{
  "mcpServers": {
    "airframe": { "url": "https://mcp.airframe.ai/mcp" }
  }
}

If sign-in doesn't start, use the mcp-remote bridge.

Other clientsCopy Anchor Link

Any client that supports remote MCP servers with OAuth can use the server URL directly.

For clients that only run local (stdio) servers, including the Claude Desktop config file, bridge with mcp-remote. It needs Node.js 18 or later and opens the browser to sign in on first connect:

{
  "mcpServers": {
    "airframe": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.airframe.ai/mcp"]
    }
  }
}

mcp-remote stores tokens in ~/.mcp-auth. Delete that folder to sign in again.

For headless agents and CI, where a browser sign-in isn't possible, see API keys.

Steps can differ slightly between client versions. If something here doesn't match what you see, let us know.