Skip to content

Setup

This page connects the CloudAEye MCP server to your coding agent and installs the review skills. Setup is one-time per machine, plus a small per-project policy snippet.

This guide covers Claude Code. The MCP tools work with any MCP client, but the slash-command skills and configuration shown here are Claude Code specific. Setup for other IDEs — Cursor, OpenAI Codex, and others — differs and is not yet documented; those guides are coming.

Prerequisites

  • The URL of your CloudAEye review server (provided by CloudAEye or your team).
  • Claude Code installed, with a ~/.claude/ directory.
  • git and curl on your PATH (the skills use both).

Step 1 — Connect the MCP server

Add the server to ~/.claude/mcp.json:

{
  "mcpServers": {
    "cloudaeye": {
      "type": "http",
      "url": "<cloudaeye-server>"
    }
  }
}

Replace <cloudaeye-server> with the URL CloudAEye provides.

This registers all mcp tools in every project on your machine.

Step 2 — Install the skills

The skills wrap the session / upload / tool-call sequence into a single slash command. Copy them into your skills directory:

macOS / Linux 

cp cloudaeye-inspect.md cloudaeye-describe.md cloudaeye-check-task.md ~/.claude/skills/

Windows (PowerShell) 

Copy-Item cloudaeye-inspect.md,cloudaeye-describe.md,cloudaeye-check-task.md "$env:USERPROFILE\.claude\skills\"

After copying, the commands are available in every Claude Code session.

Command naming. The skill files currently register as /cloudaeye-inspect, /cloudaeye-describe, and /cloudaeye-check-task. This documentation refers to them by their short product names — /inspect, /describe, /check_task — which are the target naming. Use whichever your installed skills expose.

Step 3 — Add the finish-of-task reminder (optional)

To be reminded to run a review every time the agent finishes, add a Stop hook to ~/.claude/settings.json. This prints a reminder in the terminal when Claude completes a task; the enforcement lives in Step 4.

Step 4 — Add the review policy to your project

Paste this into your project's CLAUDE.md so the coding agent treats a review as part of "done":

## Code inspect policy (cloudaeye)

After completing any coding task, before reporting done:

1. Run `/inspect`
2. Surface the findings to the user. Don't auto-fix unless asked.

The Stop hook is a reminder; this snippet is what actually makes the agent run the check before it reports a task complete.