Iris Code

io.github.DaiveedjayPublished by GitHub account Daiveedjayv0.2.2Updated Oct 29, 2026

Local code-quality rules, findings, preview-first safe fixes and gate results for coding agents.

VerifiedSTDIODesktop onlyDatabasesDeveloper Tools

Overview

AI-generated overview

Local MCP server that gives coding agents a project's code-quality rules, findings, preview-first safe fixes and quality-gate results.

What you can do
  • Run code checks and read located findings with code-health measurements
  • Inspect resolved project thresholds, rules and the rule details behind findings
  • Preview and apply provable mechanical fixes, and plan refactors with a captured baseline
  • Verify a refactor's improvement against that baseline and read quality-gate results with failing rules
  • Look up real database tables, columns and relations, plus dependency advisories and package risk before installation
When to use it
Useful when a coding agent should work against a project's actual quality rules rather than generic advice: checking code, applying safe mechanical fixes, planning and verifying refactors, or gating changes before they land.
Requirements
Node.js 18 or newer, run locally over stdio via npx. Clients normally supply the workspace root; otherwise pass --root with an absolute project path. Single-file workflows need no API key; fresh project work requires sign-in and applicable access. Dependency and advisory lookups need network consent.
Before you install
Applying fixes writes to project files, though it requires the preview's single-use token. Fresh project work needs sign-in and paid access adds broader capabilities, so check pricing. Dependency and advisory lookups send data over the network only with consent. The analysis engine's source is not in the public launcher repository.

Installation

In SourceWeft

  1. Open Iris Code in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Iris Code MCP launcher

Give coding agents your project's real code-quality rules, findings, safe fixes and gate results.

This repository contains the npm launcher and setup documentation for Iris Code's local MCP server. It starts the published @iris-code/cli package, which carries the implementation. The analysis engine's source is maintained separately and is not included here. The launcher declares the MIT license; this repository does not claim the whole Iris Code product is open source.

Install

Requires Node.js 18 or newer.

sh
npx -y @iris-code/mcp

Add this to your client's MCP configuration:

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

Clients normally supply the current workspace root. For a client that does not provide MCP roots, append --root and your absolute project path to args. In JetBrains IDEs, use Tools | Iris Code | Set Up MCP Server from the installed Iris Code plugin.

What agents can do

ToolPurpose
iris_checkLocated findings and code-health measurements
iris_configResolved project thresholds and rules
iris_fix_safePreview and apply provable mechanical fixes
iris_refactor_planLocated refactor suggestions and a captured baseline
iris_verify_refactorVerify improvement against a baseline
iris_schemaReal database tables, columns and relations
iris_explainRule details behind findings
iris_gateQuality-gate result and failing rules
iris_check_dependencyDependency advisory evidence
iris_check_packagePackage risk before installation

Single-file workflows are Free and require no API key. Fresh project work requires sign-in and applicable access. Reopening owned evidence does not spend another project action. Paid access adds broader enforcement and project capabilities. See current pricing and the MCP guide.

Boundaries

Analysis runs locally. The server has no general shell-execution tool. Secret values are masked, and requested paths are confined to the project root, including symlink resolution. Safe fixes preview first; applying needs the preview's single-use token. Dependency and advisory lookups require network consent. Repository handoff policy and access checks still apply.

Support and privacy

Registry metadata release

Version 0.2.2 adds the official MCP Registry ownership name io.github.Daiveedjay/iris-code. Launcher behavior and the CLI dependency range are unchanged. The npm package's repository URL identifies the existing private release owner because npm trusted publishing requires it to match the workflow repository. This public repository supplies launcher source and documentation; npm publication still runs from the private release workflow.

Official MCP Registry identity: io.github.Daiveedjay/iris-code, published version 0.2.2. Verify the public registry metadata. The entry uses local stdio transport, not a hosted endpoint.

Source: README.md at commit 96e46b8

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.2LatestOct 29, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts