Skip to content
Developers
Esc
↑↓navigate↵open⌘Jpreview
On this page

Connect an AI app

Add the Qaf MCP server to Claude, ChatGPT, Claude Code, Codex, Cursor, VS Code or another MCP app, then sign in with your Qaf account.

Every app connects to the same server URL. After you add it, the app opens a Qaf sign-in page in your browser: sign in with your Qaf account and allow access.

https://api.qaf.ai/mcp

App menus change often. If a step doesn’t match what you see, follow the app’s own guide, linked in each tab.

  1. In Claude, open Customize › Connectors and select Add › Add custom connector.
  2. Name it Qaf, paste the server URL and select Continue. Review the detected settings and select Continue again.
  3. Under Authentication, keep Sign in now. Under OAuth client, choose Register automatically: Qaf doesn’t support Claude’s published identity.
  4. Select Add, then sign in with your Qaf account and allow access.

On Team and Enterprise plans, an owner adds the connector first, under Organization settings › Connectors. Each member then selects Connect next to it in Customize › Connectors.

To use Qaf in a chat, select + in the message box, open Connectors and turn on Qaf. Claude’s guide: Get started with custom connectors using remote MCP.

  1. In ChatGPT on the web, open Plugins, select + and choose Add custom MCP server.
  2. Name it Qaf and paste the server URL under Connection. For authentication, choose OAuth.
  3. Read the warning, select I understand and want to continue, then Create as a plugin.
  4. Install the plugin, then sign in with your Qaf account and allow access.

To use Qaf in a conversation, type @ in the message box and select Qaf. In a workspace, admin settings can restrict custom MCP servers. OpenAI’s guide: Add custom MCP server.

  1. Add the server for all your projects:

    claude mcp add --transport http --scope user qaf https://api.qaf.ai/mcp
  2. In Claude Code, run /mcp, select qaf and sign in with your Qaf account in the browser that opens.

To sign in from a terminal without a session, run claude mcp login qaf. Anthropic’s guide: Connect Claude Code to tools via MCP.

  1. Add the server:

    codex mcp add qaf --url https://api.qaf.ai/mcp
  2. Sign in with your Qaf account in the browser that opens:

    codex mcp login qaf

The Codex CLI, the IDE extension and the ChatGPT desktop app share this setting. It lives in ~/.codex/config.toml:

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

OpenAI’s guide: MCP in Codex.

  1. Add Qaf to Cursor, or add it to ~/.cursor/mcp.json yourself. If the file exists, add the qaf entry to its mcpServers.

    {
      "mcpServers": {
        "qaf": {
          "url": "https://api.qaf.ai/mcp"
        }
      }
    }
  2. Open Customize in Cursor, turn on qaf, and sign in with your Qaf account when the browser opens.

Cursor’s guide: Model Context Protocol.

  1. In VS Code, run MCP: Add Server from the Command Palette.
  2. Choose HTTP (HTTP or Server-Sent Events), paste the server URL and enter qaf as the server ID.
  3. Select Global, then Copilot Global, to use it in every workspace.
  4. When VS Code starts the server, sign in with your Qaf account in the browser that opens.

To share it with everyone who works on a project, add it to .mcp.json at the workspace root:

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

MCP: Add Server offers this file only when the experimental chat.mcp.workspaceRootConfig.enabled setting is on. An existing .mcp.json works with the setting off.

VS Code’s guide: Add and use MCP servers in VS Code.

Any app that supports remote MCP servers with OAuth sign-in can connect. It needs:

  • Server URL: https://api.qaf.ai/mcp
  • Transport: Streamable HTTP
  • Sign-in: OAuth 2.1 with dynamic client registration and PKCE. The app registers itself; there’s no client ID to enter.

An app that only runs local (stdio) servers can reach Qaf through the mcp-remote bridge:

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

Building a client? Sign-in and connected apps lists the endpoints and protocol details.

Troubleshooting

The app can't connect

Check that the URL is exactly https://api.qaf.ai/mcp. The app must support remote MCP servers over Streamable HTTP; an app that only runs local servers needs the bridge in Other apps.

Your account can't connect

The sign-in page says so when an account can’t use the server. A guest session can’t connect: sign in to qaf.ai with an account first. An account that is waiting to be deleted, or is suspended, can’t connect either. If you think your account should have access, email us at contact@qaf.ai.

The sign-in page doesn't open

Allow pop-ups for the app’s site, then try again. On a machine without a browser, run claude mcp login qaf --no-browser or codex mcp login qaf --no-browser and follow the prompt.

Qaf's tools don't appear

Most apps need the server turned on for each chat or workspace: in Claude, turn on Qaf under + › Connectors; in ChatGPT, type @ and select Qaf; in Cursor, turn on qaf in Customize. If the tools still don’t appear, remove the server and add it again.

The app asks you to sign in again

An app stays signed in while you use it. It has to sign in again after 30 days without use, or after you disconnect it. In Claude Code, run /mcp, select qaf and choose Re-authenticate. In Codex, run codex mcp login qaf. In other apps, remove the server and add it again.