Set Up OpenCode

OpenCode connects to Citlyze as a remote MCP server with an API key header. Create the key in workspace settings first.

Add the server

Add the server to opencode.json in your project root, or to ~/.config/opencode/opencode.json to make it available everywhere:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "citlyze": {
      "type": "remote",
      "url": "https://app.citlyze.com/api/mcp",
      "enabled": true,
      "headers": {
        "Authorization": "Bearer aeo_live_..."
      }
    }
  }
}

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

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

Citlyze authenticates with the API key header, so no OAuth flow is involved; if OpenCode attempts one, set "oauth": false on the server entry.

Verify the connection

Run opencode mcp list and confirm citlyze appears as connected, then ask a simple read-only question in a session:

Show my Citlyze workspace overview.

If the key is valid and the plan includes API exports, the agent should call get_workspace_overview.

Key handling

Create a dedicated API key for OpenCode so it can be revoked without affecting dashboards or other integrations. Never commit a key inside a project-level opencode.json; use the environment variable form above.

For other MCP clients, see Set Up MCP Clients.