Octopus MCP Server
# Octopus Code Review — editor plugin
Bring [Octopus](https://octopus-review.ai) AI code review into your editor. This repo is both:
- an **MCP server** (`@octp/mcp`) that exposes Octopus as tools, and
- a **plugin** for the **Cursor** and **Claude** marketplaces that wires the server in.
## Tools
| Tool | What it does |
|---|---|
| `octopus_status` | Verify the connection and show which Octopus org your token belongs to. |
| `octopus_review_changes` | Review your working changes. Pass a `diff`, or a `repoPath` and it runs `git diff` for you. Returns findings + a summary. |
| `octopus_review_pr` | Trigger a full server-side review of an open pull/merge request; Octopus posts findings as comments on the PR. Pass a PR number or URL. |
| `octopus_ask` | Ask Octopus about your code or a past review (answers use your indexed repos + review history). |
## Skills & commands
- **`/octopus-review`** — review your working changes, or pass a PR number/URL to review a pull request.
- **autofix** skill — say "octopus autofix" to scan your open PRs for Octopus review-bot comments, apply the fixes, push, and re-trigger review.
## Get a token
The tools authenticate with an Octopus **org API token** (`oct_...`):
```bash
npx @octp/cli login
```
or create one in your [octopus-review.ai](https://octopus-review.ai) settings. Put it in the plugin's config (never in a repo).
## Install
**Cursor** — install "Octopus Code Review" from the marketplace, then set your `OCTOPUS_TOKEN` in the plugin config.
**Claude** — add this marketplace and install the plugin:
```bash
claude plugin marketplace add octopusreview/octopus-plugin
claude plugin install octopus-review
```
then set your token when prompted (stored as a sensitive user config value).
**Any MCP client** — run the server directly:
```bash
OCTOPUS_TOKEN=oct_... npx -y github:octopusreview/octopus-plugin
```
## Config
| Variable | Required | Default |
|---|---|---|
| `OCTOPUS_TOKEN` | yes | — |
| `OCTOPUS_API_URL` | no | `https://octopus-review.ai` (set this for self-hosted Octopus) |
## Develop
```bash
npm install
npm run build
OCTOPUS_TOKEN=oct_... node build/index.js # a stdio MCP server
```
MIT licensed. Octopus itself is a separate product; this plugin only calls its public API on your behalf.
TDQS
Scored across 3 tools
Each tool handles a clearly distinct responsibility: verifying connectivity, reviewing a diff, and asking follow-up questions. There is zero overlap that could cause an agent to select the wrong tool.
All tools follow the same snake_case convention with the `octopus_` prefix, creating a predictable pattern. The verb-like suffixes (`status`, `review_changes`, `ask`) are consistent in style and clearly convey action.
At 3 tools, the server is at the minimal end of the ideal range, yet each tool genuinely earns its place and the count is well-scoped for the server's purpose. A couple of additional tools (e.g., configuration or history browsing) could make it feel more substantial.
The core workflow of connect → review → ask follow-ups is fully covered. Minor gaps include the lack of a direct way to list past reviews without using `octopus_ask` and no configuration or preference settings, but these are workable for common use cases.