Skip to main content

​
Overview

CodeAlive works with any MCP-compatible AI agent. This page covers setup for agents that use standard JSON configuration. For agents with unique setup requirements, see their dedicated pages.

​
General Setup

All agents below follow the same pattern:
  1. Get your API key from app.codealive.ai
  2. Find the agent’s MCP config file
  3. Add the CodeAlive server configuration
  4. Restart the agent
Quick install: Run npx @codealive/installer to automatically detect and configure CodeAlive for supported agents. See the Installation Guide for details.

​
Agent Configurations

Roo Code reads a JSON settings file similar to Cline.Config file: mcp_settings.json (Roo) or cline_mcp_settings.jsonRemote HTTP:
{
  "mcpServers": {
    "codealive": {
      "type": "streamable-http",
      "url": "https://mcp.codealive.ai/api",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY_HERE"
      }
    }
  }
}
Docker (STDIO):
{
  "mcpServers": {
    "codealive": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run", "--rm", "-i",
        "-e", "CODEALIVE_API_KEY=YOUR_API_KEY_HERE",
        "ghcr.io/codealive-ai/codealive-mcp:v0.3.0"
      ]
    }
  }
}
If your Roo build doesn’t honor HTTP headers, use the Docker STDIO option.
Zed uses context_servers in its settings with STDIO transport only.Config: Zed Settings (settings.json)
{
  "context_servers": {
    "codealive": {
      "command": {
        "path": "docker",
        "args": [
          "run", "--rm", "-i",
          "-e", "CODEALIVE_API_KEY=YOUR_API_KEY_HERE",
          "ghcr.io/codealive-ai/codealive-mcp:v0.3.0"
        ]
      }
    }
  }
}
Zed currently supports STDIO transport only — HTTP/SSE is not yet available.
Antigravity uses a Gemini-style config format.Config file: ~/.gemini/antigravity/mcp_config.json
{
  "mcpServers": {
    "codealive": {
      "type": "streamable-http",
      "url": "https://mcp.codealive.ai/api",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY_HERE"
      }
    }
  }
}
Goose uses a UI-based setup flow.Setup path: Settings → MCP Servers → Add → choose Streamable HTTPStreamable HTTP configuration:
  • Name: codealive
  • Endpoint URL: https://mcp.codealive.ai/api
  • Headers: Authorization: Bearer YOUR_API_KEY_HERE
Docker (STDIO) alternative: Add a STDIO extension with:
  • Command: docker
  • Args: run --rm -i -e CODEALIVE_API_KEY=YOUR_API_KEY_HERE ghcr.io/codealive-ai/codealive-mcp:v0.3.0
Kilo Code uses a UI-based setup.Setup path: Manage → Integrations → Model Context Protocol (MCP) → Add ServerHTTP:
{
  "mcpServers": {
    "codealive": {
      "type": "streamable-http",
      "url": "https://mcp.codealive.ai/api",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY_HERE"
      }
    }
  }
}
STDIO (Docker):
{
  "mcpServers": {
    "codealive": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run", "--rm", "-i",
        "-e", "CODEALIVE_API_KEY=YOUR_API_KEY_HERE",
        "ghcr.io/codealive-ai/codealive-mcp:v0.3.0"
      ]
    }
  }
}
Qwen Code supports multiple transports (stdio/SSE/streamable-http).Config file: ~/.qwen/settings.jsonStreamable HTTP:
{
  "mcpServers": {
    "codealive": {
      "type": "streamable-http",
      "url": "https://mcp.codealive.ai/api",
      "requestOptions": {
        "headers": {
          "Authorization": "Bearer YOUR_API_KEY_HERE"
        }
      }
    }
  }
}
Docker (STDIO):
{
  "mcpServers": {
    "codealive": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run", "--rm", "-i",
        "-e", "CODEALIVE_API_KEY=YOUR_API_KEY_HERE",
        "ghcr.io/codealive-ai/codealive-mcp:v0.3.0"
      ]
    }
  }
}
Qwen Code wraps headers in requestOptions — different from most other clients.
Kiro does not yet support remote MCP servers natively. Use the mcp-remote workaround.Prerequisites:
npm install -g mcp-remote
Config file: ~/.kiro/settings/mcp.json or .kiro/settings/mcp.json (workspace)Remote HTTP (via mcp-remote):
{
  "mcpServers": {
    "codealive": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.codealive.ai/api",
        "--header",
        "Authorization: Bearer ${CODEALIVE_API_KEY}"
      ],
      "env": {
        "CODEALIVE_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}
Docker (STDIO):
{
  "mcpServers": {
    "codealive": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run", "--rm", "-i",
        "-e", "CODEALIVE_API_KEY=YOUR_API_KEY_HERE",
        "ghcr.io/codealive-ai/codealive-mcp:v0.3.0"
      ]
    }
  }
}
Qoder uses a UI-based setup with SSE transport.Setup path: User icon → Qoder Settings → MCP → My Servers → + Add (Agent mode)SSE (remote HTTP):
{
  "mcpServers": {
    "codealive": {
      "type": "sse",
      "url": "https://mcp.codealive.ai/api",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY_HERE"
      }
    }
  }
}
STDIO (Docker):
{
  "mcpServers": {
    "codealive": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run", "--rm", "-i",
        "-e", "CODEALIVE_API_KEY=YOUR_API_KEY_HERE",
        "ghcr.io/codealive-ai/codealive-mcp:v0.3.0"
      ]
    }
  }
}
JetBrains AI Assistant requires the mcp-remote workaround for remote HTTP MCP servers.Prerequisites:
npm install -g mcp-remote
Setup path: Settings/Preferences → AI Assistant → Model Context Protocol → Configure
{
  "mcpServers": {
    "codealive": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.codealive.ai/api",
        "--header",
        "Authorization: Bearer ${CODEALIVE_API_KEY}"
      ],
      "env": {
        "CODEALIVE_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}
See JetBrains MCP Documentation for more details.
n8n connects via the AI Agent node with MCP tools.Setup:
  1. Add an AI Agent node to your workflow
  2. Configure the agent with MCP tools:
    • Server URL: https://mcp.codealive.ai/api
    • Authorization Header: Bearer YOUR_API_KEY_HERE
  3. The server automatically handles n8n’s extra parameters (sessionId, action, chatInput, toolCallId)
Example Workflow:
Trigger → AI Agent (with CodeAlive MCP tools) → Process Response
n8n middleware is built-in — the server automatically strips n8n’s extra parameters before processing tool calls.

​
Troubleshooting

  1. Verify your API key is correct
  2. Check the config file location and JSON syntax
  3. Ensure the Authorization header includes Bearer prefix
  4. Restart the agent completely
Use Docker STDIO instead — it works with every agent that supports MCP:
{
  "command": "docker",
  "args": [
    "run", "--rm", "-i",
    "-e", "CODEALIVE_API_KEY=YOUR_API_KEY_HERE",
    "ghcr.io/codealive-ai/codealive-mcp:v0.3.0"
  ]
}
Some agents (Kiro, JetBrains AI) don’t support remote HTTP natively. Install mcp-remote:
npm install -g mcp-remote
Then use the STDIO config with npx mcp-remote as the command.
For more solutions, see the Troubleshooting Guide.