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,

... View full README on GitHub