Set Up MCP Clients

Connect Citlyze to Claude Desktop, Cursor, VS Code, Windsurf, Cline, Continue, and custom MCP clients.

Use this page for MCP clients that can connect to a remote Streamable HTTP server and send custom request headers.

Connection details

Setting	Value
Server name	`citlyze`
Transport	Streamable HTTP, usually named `http` or `streamable-http`
URL	`https://app.citlyze.com/api/mcp`
Header	`Authorization: Bearer aeo_live_...`

The public API index also reports:

{
  "mcp_endpoint": "/api/mcp"
}

Common clients

Client	Recommended setup
Claude Code	Use the CLI flow in Set Up Claude Code.
Claude Desktop	Use the generic JSON shape below if your installed version supports remote HTTP MCP servers.
Cursor	Use the generic JSON shape below for remote HTTP MCP, if enabled in your Cursor version.
VS Code / GitHub Copilot	Use the VS Code `servers` shape below in `.vscode/mcp.json` or user MCP config.
Windsurf / Cascade	Use the Windsurf `serverUrl` shape below.
Cline / Roo Code	Use the generic JSON shape below if the extension supports remote Streamable HTTP.
Continue	Use the generic JSON shape below if the installed version supports remote MCP.
OpenAI Agents SDK or custom agents	Configure a Streamable HTTP MCP client with the URL and authorization header above.

If a client only supports local stdio MCP servers, use the mcp-remote bridge section below.

If a client cannot send custom HTTP headers, it cannot connect directly to Citlyze yet because Citlyze requires the Authorization header.

Generic MCP JSON

Many clients use an mcpServers object. Try type: "http" first. If the client expects the protocol name instead, use type: "streamable-http".

{
  "mcpServers": {
    "citlyze": {
      "type": "http",
      "url": "https://app.citlyze.com/api/mcp",
      "headers": {
        "Authorization": "Bearer aeo_live_..."
      }
    }
  }
}

Do not put the API key in the URL.

Claude Desktop

For Claude Desktop versions that support remote HTTP MCP servers, add the generic JSON shape to the Claude Desktop MCP configuration file and restart the app.

If your Claude Desktop build only supports local stdio servers, use mcp-remote or another local bridge that can forward headers:

{
  "mcpServers": {
    "citlyze": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://app.citlyze.com/api/mcp",
        "--header",
        "Authorization: Bearer aeo_live_..."
      ]
    }
  }
}

VS Code / GitHub Copilot

VS Code uses a servers object in .vscode/mcp.json or the user MCP configuration.

{
  "servers": {
    "citlyze": {
      "type": "http",
      "url": "https://app.citlyze.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:citlyzeApiKey}"
      }
    }
  },
  "inputs": [
    {
      "id": "citlyzeApiKey",
      "type": "promptString",
      "description": "Citlyze API key",
      "password": true
    }
  ]
}

Prefer input variables or environment-backed secrets over committing API keys to a workspace file.

Windsurf / Cascade

Windsurf stores MCP configuration in ~/.codeium/windsurf/mcp_config.json. Remote HTTP servers use serverUrl or url.

{
  "mcpServers": {
    "citlyze": {
      "serverUrl": "https://app.citlyze.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:CITLYZE_API_KEY}"
      }
    }
  }
}

Custom HTTP clients

Custom agents should initialize MCP over Streamable HTTP at:

https://app.citlyze.com/api/mcp

Send the API key on every request:

Authorization: Bearer aeo_live_...

Clients must support HTTP MCP responses that return either JSON or text/event-stream.