Skip to content

CloudAEye in VS Code with Copilot

Connect CloudAEye to GitHub Copilot to describe changes and review code in VS Code's Agent mode. See the prerequisites.

1. Install the plugin

Use a current VS Code with agent plugin support and GitHub Copilot enabled. Sign in to Copilot, then:

  1. Run Chat: Install Plugin From Source from the Command Palette.
  2. Enter https://github.com/CloudAEye/claude-plugin.
  3. Review and approve the plugin's trust prompt.
  4. Reload VS Code and start a new chat.

If plugin support is disabled, enable chat.plugins.enabled in Settings. See VS Code plugin installation.

2. Verify the MCP connection

The plugin supplies its MCP connection through the root .mcp.json; you do not need to configure a URL separately when it already targets the hosted service.

Run MCP: List Servers, select CloudAEye, and inspect its configuration. Confirm that the bundled connection uses https://api.cloudaeye.com/mcp. VS Code uses direct HTTP; the Cursor OAuth bridge is not needed.

If the URL points to localhost, stop before authenticating. Update to a hosted-compatible CloudAEye plugin package, reload VS Code, and check again. If it still points to localhost, ask CloudAEye for a hosted-compatible release; do not start a local server or edit generated plugin-cache files as a workaround.

Do not create a duplicate .vscode/mcp.json entry for the bundled connection. MCP registration alone does not install skills. See the MCP configuration reference.

3. Authenticate and run

  1. Run MCP: List Servers, select CloudAEye, and start the connection.
  2. Approve trust if prompted, then select Authenticate when required.
  3. Complete CloudAEye browser sign-in and consent.
  4. Open Chat, select Agent mode in a workspace session, and enable CloudAEye tools in the tool selector.
  5. Type / and select CloudAEye's init, then describe.

Copilot login does not authenticate CloudAEye. Select review for uncommitted changes, or append #412 for an eligible PR. Results appear in Chat. Follow the shared workflow for scope and approvals.

3.1 Help and Commands

For the complete command catalog, run CloudAEye's help or see Skills & Commands reference guide.

Troubleshooting

Problem Action
Skills missing Confirm the plugin is installed and enabled. Reload and start a new chat.
Tools missing Start MCP, enable its tools, and disable duplicate connections.
MCP points to localhost Obtain a hosted-compatible plugin package, reload VS Code, and verify the URL before authenticating.
Authentication does nothing Open MCP: List Servers > CloudAEye > Show Output and inspect OAuth discovery errors.
Repeated 401 Complete CloudAEye OAuth and check the endpoint and issuer.
Expired MCP session Reconnect after a server restart.

For discovery CORS errors, ask the administrator to allow cross-origin GET and OPTIONS requests to public OAuth discovery routes. Login and token endpoints must retain their existing restrictions. Do not disable CORS globally.

For client controls, see MCP setup and skill selection.