Quickstart

1. Open Account settings → Connectors, click + Custom connector, then Remote.
2. Name it Apogee, paste https://app.apogee.ad/mcp, choose OAuth as the authentication and Streamable HTTP as the transport.
3. Tick the acknowledgement and click Add.
4. Click the Apogee card, log in to Apogee and click Authorize.

Plans: Pro, Max and Enterprise. On Enterprise, an admin first allows members to add custom connectors (off by default).

Perplexity also offers an API Key option but does not document how it sends the key: use OAuth.

Checked on 10 October 2026 against Perplexity Help Center: custom remote connectors.

1. Open Connectors from the sidebar, click + Add Connector, then the Custom MCP Connector tab.
2. Name it apogee (no spaces) and paste https://app.apogee.ad/mcp as the server URL.
3. Click Connect. Vibe detects Apogee's sign-in: log in to Apogee and click Authorize.

Plans: Adding a connector is for administrators: on Free, Pro and Student, the account owner is one. Organization admins can turn connectors off.

Checked on 10 October 2026 against Mistral docs: MCP connectors and Mistral Help Center: Le Chat is now Vibe.

1. Add the server from your terminal:
   Terminal Copy

   claude mcp add --transport http apogee https://app.apogee.ad/mcp

2. In Claude Code, type /mcp, pick apogee and sign in to Apogee in your browser.

Add --scope user to have Apogee in all your projects (default: this project, for you only).

claude mcp add --transport http apogee https://app.apogee.ad/mcp \
  --header "Authorization: Bearer apk_…"

Checked on 10 October 2026 against Claude Code docs: MCP.

1. Create an API key in Settings → API with the scopes Cursor needs.
2. Open ~/.cursor/mcp.json (create it if needed) and add Apogee with your key:
   ~/.cursor/mcp.json Copy

   {
     "mcpServers": {
       "apogee": {
         "url": "https://app.apogee.ad/mcp",
         "headers": {
           "Authorization": "Bearer apk_…"
         }
       }
     }
   }

3. Turn Apogee on from Customize in the sidebar, then ask in the agent chat.

Keep the key in ~/.cursor/mcp.json (yours only), never in a project's .cursor/mcp.json that you share. Or write "Bearer ${env:APOGEE_API_KEY}" and set that variable.

Cursor also signs in with OAuth. Apogee accepts it from the desktop app (its sign-in returns to your computer), not from Cursor's web agents.

Checked on 10 October 2026 against Cursor docs: MCP.

1. Run MCP: Add Server from the Command Palette, choose HTTP, paste https://app.apogee.ad/mcp and name it apogee.
2. Trust the server when VS Code asks. On the first connection a browser window opens: log in to Apogee and click Authorize.
3. Open Copilot Chat in Agent mode and ask.

Plans: Copilot Free, Pro, Pro+ and Max: nothing to turn on. Copilot Business and Enterprise: an admin turns on the **MCP servers in Copilot** policy (off by default).

{
  "servers": {
    "apogee": {
      "type": "http",
      "url": "https://app.apogee.ad/mcp"
    }
  }
}

{
  "inputs": [
    {
      "type": "promptString",
      "id": "apogee-key",
      "description": "Apogee API key",
      "password": true
    }
  ],
  "servers": {
    "apogee": {
      "type": "http",
      "url": "https://app.apogee.ad/mcp",
      "headers": {
        "Authorization": "Bearer ${input:apogee-key}"
      }
    }
  }
}

Checked on 10 October 2026 against VS Code docs: MCP servers, VS Code docs: MCP configuration and GitHub docs: MCP in Copilot.

1. Add the server from your terminal:
   Terminal Copy

   gemini mcp add --transport http apogee https://app.apogee.ad/mcp

2. In Gemini CLI, run /mcp auth apogee and sign in to Apogee in your browser (it needs a browser on this computer). Run it again when the sign-in expires.

Plans: Gemini Code Assist Standard and Enterprise, and paid Gemini API keys. Google moved Google AI Pro, Ultra and free users to Antigravity CLI in June 2026: check its MCP settings.

Add --scope user to have Apogee in all your projects (default: this project).

gemini mcp add --transport http \
  --header "Authorization: Bearer apk_…" apogee https://app.apogee.ad/mcp

Checked on 10 October 2026 against Gemini CLI docs: MCP servers and Google: Gemini CLI to Antigravity CLI.

1. Create an API key in Settings → API with the scopes it needs.
2. Open the MCP config file: in the Cascade panel, the … menu at the top right, MCPs section (the file is ~/.config/devin/mcp_config.json).
3. Add Apogee with your key, save, and turn it on with its toggle:
   mcp_config.json Copy

   {
     "mcpServers": {
       "apogee": {
         "url": "https://app.apogee.ad/mcp",
         "headers": {
           "Authorization": "Bearer apk_…"
         }
       }
     }
   }

Plans: Teams and Enterprise: an admin allows MCP servers (and may limit them to an allowlist) in the team settings.

Devin Desktop signs in with OAuth too, but does not document where its sign-in returns: use an API key.

Checked on 10 October 2026 against Devin docs: Cascade MCP and Devin docs: MCP configuration.

1. Server URL https://app.apogee.ad/mcp, transport Streamable HTTP.
2. Sign-in: OAuth 2.1 with PKCE, discovered from the server, with Dynamic Client Registration. Apogee accepts it from the assistants of this guide and from your own computer (http://localhost); any other client uses an API key.
3. API key: create one in Settings → API with only the scopes the client needs, and send Authorization: Bearer apk_….

{
  "mcpServers": {
    "apogee": {
      "type": "http",
      "url": "https://app.apogee.ad/mcp",
      "headers": {
        "Authorization": "Bearer apk_…"
      }
    }
  }
}

The key names differ by client (url, serverUrl, httpUrl…): check your client's MCP settings.