@iris-code/mcp

Give your AI coding agent your project's real code-health rules, over the Model Context Protocol.

Iris Code analyses your code locally and answers with the same numbers your quality gate uses, so an agent works against your committed standard instead of guessing at one.

Install

npx -y @iris-code/mcp

That is the whole install. This package is a thin launcher for @iris-code/cli, which carries the server; there is no separate binary to download.

Client setup

Register it as an MCP server in your client's configuration:

{
  "command": "npx",
  "args": ["-y", "@iris-code/mcp"]
}

Claude Code, Cursor, Windsurf, Copilot agent mode and Zed all accept a command of this shape. Because it names no folder, you can register it once at the user level and every project you open is covered: Iris Code asks your editor which workspace is open and roots itself there, falling back to the directory the server was launched in.

Pass --root <directory> only to pin that boundary deliberately, and pin it per project. The flag skips the question to your editor, so one pinned entry reused across several workspaces answers all of them about the folder it names, writes included. --root . pins nothing - it is the launch directory, which is already the fallback.

The bare command resolves the current release each run, so you pick up fixes without editing anything. Write @latest if you want that explicit:

npx -y @iris-code/mcp@latest

In controlled environments, where a client must not pick up a change you have not reviewed, append an exact version from the versions tab instead.

If your editor already bundles the Iris Code language-server binary, use iris-lsp --mcp instead - it serves the same tools with no Node install.

Tools

| Tool | Free | Pro | | --- | --- | --- | | iris_check | One file | Folder and workspace scope | | iris_config | Yes | Yes | | iris_fix_safe | One file | Folder and workspace scope | | iris_explain | No | Yes | | iris_gate | No | Yes | | iris_check_dependency | No | Yes |

iris_check also reports which files import each checked file, so an agent knows what else to re-check after a change. On Free that is the file's direct importers; Pro adds how many files reach it through a chain.

Pro tools stay listed and describe themselves as Pro rather than hiding, so your agent can tell you what it could do with an upgrade. Entitlement is checked when a tool runs, not when it is listed.

What it will not do

Analysis stays on your machine; your code is never uploaded. There is no shell-execution tool. Secret values are always masked, never returned raw. iris_fix_safe previews by default and applies only the changes a previous preview already showed you, refusing per finding anything it cannot prove safe. Every requested path must stay inside --root, symlinks included.

Dependency and advisory checks are the one exception to staying local: they query public registries and OSV.dev, and they ask before doing so.

Docs

Full documentation at docs.iriscode.co.