Other MCP clients

Connect Gemini CLI, OpenCode, Copilot CLI, Cline, Zed or any MCP client to CodePanel's remote MCP server, or run the server locally.

On this page›

Any client that supports remote MCP servers over Streamable HTTP connects at https://codepanel.ai/mcp.

Note

Do the Quickstart up to adding a provider key first. Agents cannot add provider keys or change spending limits.

Setup

Step 1: Add the MCP server

~/.gemini/settings.json

{
  "mcpServers": {
    "codepanel": {
      "httpUrl": "https://codepanel.ai/mcp"
    }
  }
}

opencode.json

{
  "mcp": {
    "codepanel": {
      "type": "remote",
      "url": "https://codepanel.ai/mcp"
    }
  }
}

opencode.json

{
  "mcp": {
    "servers": {
      "codepanel": {
        "type": "remote",
        "url": "https://codepanel.ai/mcp"
      }
    }
  }
}

~/.copilot/mcp-config.json

{
  "mcpServers": {
    "codepanel": {
      "type": "http",
      "url": "https://codepanel.ai/mcp",
      "tools": ["*"]
    }
  }
}

cline_mcp_settings.json

{
  "mcpServers": {
    "codepanel": {
      "type": "streamableHttp",
      "url": "https://codepanel.ai/mcp"
    }
  }
}

settings.json

{
  "context_servers": {
    "codepanel": {
      "url": "https://codepanel.ai/mcp"
    }
  }
}

{
  "mcpServers": {
    "codepanel": {
      "type": "http",
      "url": "https://codepanel.ai/mcp"
    }
  }
}

OpenCode 2 (@opencode/cli) reads servers only from mcp.servers. Given the OpenCode 1 shape, it lists none.

Gemini CLI connects no MCP server, user-level ones included, in a folder it doesn't trust. Trust the folder when it asks (or with /permissions). In CI, where it can't ask, pass --skip-trust or set GEMINI_CLI_TRUST_WORKSPACE=true, and only for a repository whose code you trust.

A client with MCP sign-in (OAuth) opens CodePanel's consent page on first use; approve it there. Otherwise, create a personal token under Settings → API tokens and add it next to the URL:

"headers": { "Authorization": "Bearer cpk_..." }

Step 3: Add the skills

npx skills add Code-Panel-AI/codepanel-tools

The skills use the open Agent Skills format; the installer sets them up for the agents it detects. For an agent without skills, paste the Repository setup prompt: it writes the review loop into AGENTS.md, which most agents read.

Verify

Ask the agent: "Use the CodePanel whoami tool." It answers with your GitHub account and its permissions. Gemini CLI and OpenCode can also check the connection without a model: gemini mcp list or opencode mcp list shows codepanel as connected. Then ask: "Read CodePanel's review of owner/name#123." If either request fails, see Troubleshooting.

If your client reads its MCP config from the repository (such as opencode.json), commit it with the URL only, never a token, and each person signs in with their own GitHub account. The review loop in AGENTS.md (step 3) is shared once merged.

Local servers only

A client that only runs local (stdio) servers can run CodePanel's server from a source checkout, signed in with the CLI or given a token. See MCP server.

No MCP support

An agent without MCP works from the pull request: the review comment opens with instructions for agents, and the agent answers with /feedback replies. Scripts can use the CLI or the HTTP API; The review loop maps each step to all three.

Last updated 2026-10-17