IDE and agent plugins

MergeHarbor works inside the coding agents your team already uses. Each one signs in as you, so it sees and changes only what you can in the console. The console’s Settings → Coding agents page has every command below with your organization’s address filled in.

VS Code, Cursor and other editors

The MergeHarbor extension reviews your changes from the editor, shows findings on the lines they are about with fixes you can apply, and shows your branch’s pull request and merge gate. Install it from the Visual Studio Marketplace (VS Code) or Open VSX (Cursor, Windsurf, VSCodium), then run MergeHarbor: Sign in.

Claude Code

/plugin marketplace add mergeharbor/integrations
/plugin install mergeharbor@mergeharbor

The first time Claude uses a MergeHarbor tool, run /mcp, choose mergeharbor and sign in. Your browser opens MergeHarbor’s consent page, where you pick the organization and approve the agent. Nothing is stored in the plugin: it signs in with OAuth and acts as you.

The plugin adds five skills. Claude uses them when your request fits, or you run them by name:

• /mergeharbor:review-my-changes — reviews your local changes with mh review (--staged, --committed, --deep, or paths) and summarizes the score, findings and credits used.
• /mergeharbor:explain-findings — explains the findings on your branch’s pull request against your code, fixes them when you ask, and marks them addressed after you push. It stops after three fix-and-review rounds, since each review uses credits.
• /mergeharbor:ask-codebase — answers questions about the repository from its knowledge base, past reverts and incidents, and team rules, with sources.
• /mergeharbor:start-shipyard-task — estimates a Shipyard coding task, confirms the credits with you, starts it and follows it to its pull request.
• /mergeharbor:check-merge-readiness — reports the merge gate verdict, readiness score, open findings and change risk of a pull request, and what is left to do.

Local reviews use the command-line client: brew install mergeharbor/tap/mh && mh login.

Self-hosted MergeHarbor. The plugin’s server is MergeHarbor Cloud. Add your own installation’s server as well, then turn off the plugin’s mergeharbor server in /mcp; the skills work with either:

claude mcp add --transport http --scope user mergeharbor-self-hosted https://<your MergeHarbor address>/mcp

Or bridge through the command-line client’s sign-in: mh login --url https://<your MergeHarbor address>, then claude mcp add --scope user mergeharbor-self-hosted -- mh mcp.

Claude (web and desktop)

Add MergeHarbor to Claude as a connector: in Claude, open Customize → Connectors, choose Add custom connector and enter https://app.mergeharbor.com/mcp, or find MergeHarbor in Claude’s connector directory. Select Connect, then pick the organization on MergeHarbor’s consent page. The connector also works in Claude’s mobile apps.

Claude connector covers the sign-in, every tool and whether it reads or changes data, data handling, disconnecting and troubleshooting.

Codex

codex mcp add mergeharbor -- mh mcp

Copy the prompts for /mergeharbor-review and /mergeharbor-fix from the integrations repository:

git clone --depth 1 https://github.com/mergeharbor/integrations /tmp/mergeharbor
mkdir -p ~/.codex/prompts && cp /tmp/mergeharbor/integrations/codex/prompts/*.md ~/.codex/prompts/

Add the section in integrations/codex/AGENTS.md to your repository’s AGENTS.md so Codex reviews before pushing.

Cursor

Save this as .cursor/mcp.json (use your console’s address on a self-hosted installation):

{ "mcpServers": { "mergeharbor": { "url": "https://app.mergeharbor.com/mcp" } } }

integrations/cursor in the integrations repository has a rule and two commands to copy into .cursor/.

What agents can do through MCP

Codex, Cursor and other MCP clients get the same tools as Claude; see the tool list. See Integrations for more on the MCP server.