Custom connector (HTTP direct). If your Add custom connector dialog has a Request headers section (in beta, not available to every organization yet):

1. Go to Customize → Connectors → Add custom connector. On Team and Enterprise plans, an Owner adds it under Organization settings → Connectors instead, and every member then uses the key the Owner entered: everyone in the organization acts as that one Stape account, including its write and delete tools, so only do this when that's intended.
2. Set the URL to https://mcp.stape.io/mcp and Authentication to No sign-in.
3. Under Request headers, add authorization with your Stape API key as the value, mark it Required, and select Add.

The connector also works on claude.ai. EU accounts use https://mcp.stape.io/mcp?region=eu as the URL.

mcp-remote. Without Request headers, add this to your claude_desktop_config.json (Settings → Developer → Edit Config):

{
  "mcpServers": {
    "stape-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.stape.io/mcp",
        "--header",
        "Authorization: ${your_stape_api_key}"
      ]
    }
  }
}

EU accounts: add "--header", "X-Stape-Region: EU" to args.

claude mcp add --transport http stape-mcp-server https://mcp.stape.io/mcp \
  --header "Authorization: ${your_stape_api_key}"

This adds the server to the current project only. Add --scope user to use it in every project, or --scope project to write it to the project's .mcp.json (avoid that one if the file is committed, since it holds your key). Run claude mcp list or /mcp inside Claude Code to confirm it connected.

EU accounts: add --header "X-Stape-Region: EU".

VS Code's MCP client supports HTTP servers natively, no mcp-remote needed. Add this to .vscode/mcp.json (this workspace) or to the file MCP: Open User Configuration opens (every workspace). VS Code asks for the API key the first time the server starts and stores it, so the key never lands in the file:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "stape-api-key",
      "description": "Stape API key",
      "password": true
    }
  ],
  "servers": {
    "stape-mcp-server": {
      "type": "http",
      "url": "https://mcp.stape.io/mcp",
      "headers": {
        "Authorization": "${input:stape-api-key}"
      }
    }
  }
}

EU accounts: add "X-Stape-Region": "EU" to headers.

copilot mcp add --transport http stape-mcp-server https://mcp.stape.io/mcp \
  --header "Authorization: ${your_stape_api_key}"

This writes the server entry into ~/.copilot/mcp-config.json, and it's available right away. Run copilot mcp get stape-mcp-server to confirm it connected. Inside an interactive session, /mcp add does the same through a form. See GitHub's docs for more.

EU accounts: add --header "X-Stape-Region: EU".

GitHub Copilot Chat in VS Code uses VS Code's own MCP client, so it reads the same .vscode/mcp.json file — see VS Code above, including its EU change. No separate configuration is needed.

Cursor speaks HTTP directly too, no mcp-remote needed. Add this to .cursor/mcp.json (this project) or ~/.cursor/mcp.json (every project):

{
  "mcpServers": {
    "stape-mcp-server": {
      "url": "https://mcp.stape.io/mcp",
      "headers": {
        "Authorization": "${your_stape_api_key}"
      }
    }
  }
}

To keep the key out of the file, set "Authorization": "${env:STAPE_API_KEY}" and export STAPE_API_KEY in your shell profile. Manage the server from Customize in Cursor's sidebar.

EU accounts: add "X-Stape-Region": "EU" to headers.

Antigravity also speaks HTTP directly, using serverUrl instead of url. Add this to ~/.gemini/config/mcp_config.json, which the Antigravity editor and CLI share. In the editor, open it from the agent panel via … → MCP Servers → Manage MCP Servers → View raw config:

{
  "mcpServers": {
    "stape-mcp-server": {
      "serverUrl": "https://mcp.stape.io/mcp",
      "headers": {
        "Authorization": "${your_stape_api_key}"
      }
    }
  }
}

EU accounts: add "X-Stape-Region": "EU" to headers.

ChatGPT can't connect to the Stape MCP Server yet. Its custom MCP servers (Plugins → + → Add custom MCP server) accept only OAuth or no authentication (OpenAI's docs), and the Stape MCP Server authenticates with an API key. Use one of the other clients in the meantime.

1. In Lovable, go to Connectors, select + in the top right, then choose MCP server.
2. Set Server name to Stape and Server URL to https://mcp.stape.io/mcp.
3. Under authentication, choose Bearer token or API key (not the default OAuth) and paste your Stape API key.
4. Select Add server.

Lovable can't send custom headers, so EU accounts use https://mcp.stape.io/mcp?region=eu as the server URL instead of the X-Stape-Region header. The connection is personal (teammates add their own) and works in the project chat and Chats, not in your published app. See Lovable's docs for more.

If your client supports remote HTTP MCP servers with custom headers, point it at https://mcp.stape.io/mcp with an Authorization header holding your Stape API key, as in the Cursor config. Otherwise, use mcp-remote:

{
  "mcpServers": {
    "stape-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.stape.io/mcp",
        "--header",
        "Authorization: ${your_stape_api_key}"
      ]
    }
  }
}

EU accounts: send the X-Stape-Region: EU header (with mcp-remote, add "--header", "X-Stape-Region: EU" to args), or use https://mcp.stape.io/mcp?region=eu if the client takes only a URL and a key.