Set Up Cursor

Cursor connects to Citlyze over remote Streamable HTTP with an API key header. Create the key in workspace settings first.

Add the server

Edit ~/.cursor/mcp.json to make Citlyze available in every project, or .cursor/mcp.json in a project root to scope it to that project:

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

Remote servers need no type field in Cursor. Do not put the API key in the URL.

To keep the key out of the file, reference an environment variable instead:

"Authorization": "Bearer ${env:CITLYZE_API_KEY}"

Set CITLYZE_API_KEY in the environment Cursor is launched from. This matters especially for a project-level .cursor/mcp.json that might be committed to a repository.

Verify the connection

1. Open Cursor's settings and find the MCP section. The citlyze server should appear with a toggle; make sure it is enabled.
2. In a chat, ask a simple read-only question:

Show my Citlyze workspace overview.

If the key is valid and the plan includes API exports, the agent should call get_workspace_overview. If the server shows an error state, open the Output panel and select the MCP logs to see the response Cursor received.

Key handling

Create a dedicated API key for Cursor so it can be revoked without affecting dashboards or other integrations. Never commit a key inside .cursor/mcp.json; use the environment variable form above.

For other MCP clients, see Set Up MCP Clients.