Repository navigation
Releases
v1.1.0
The suite reaches more installers: a Claude Code plugin, the VS Code extension as a vsix on GitHub Releases, the five servers on the MCP Registry, and the IRIS-side classes through IPM. All eight @iris-mcp/* packages are at 1.1.0, one shared version, and npx -y @iris-mcp/<server>@1 picks it up with no change. The "1.1.0 detail" sections below are the per-story record of everything in this release. No tool, prompt, governance or wire change is made: no tool or tool count changes, the frozen governance baseline stays at hash 1e62c5ad5bf7 (141 keys), and the frozen goldens and the tools-list snapshot are byte-unchanged. BOOTSTRAP_VERSION moves from 1.0.0+2.244fe8623c76 to 1.1.0+2.244fe8623c76: the marker follows the version, and the class content and the sequence are unchanged.
Added
- A Claude Code plugin.
/plugin marketplace add jbrandtmse/iris-execute-mcp-v2, then/plugin install iris-mcp@iris-mcp. It brings the five servers (eachnpx -y @iris-mcp/<name>@1) and the skills, and asks once for the IRIS host, web port, namespace, HTTPS, user name and password (the password goes to the system keychain).iris-mcp-clients skills install --client claude-codesees the plugin and installs only the always-on rule, andiris-mcp-clients doctorreports anyiris-*-mcpentry that would make every tool appear twice beside it. - The VS Code extension as a vsix. The IRIS MCP launcher is attached to the
v1.1.0GitHub Release asiris-mcp-launcher-1.1.0.vsix: install it with Extensions: Install from VSIX… orcode --install-extension iris-mcp-launcher-1.1.0.vsix, and install later versions the same way. It is not on the Visual Studio Marketplace or Open VSX yet: the release's Marketplace channel is off until the publisheriris-mcpis registered (DW-719), and Open VSX is skipped until its namespace exists. The Story 42.7 detail below describes both store channels as they work once they are set up. - The MCP Registry. The five servers are listed on the MCP Registry (in preview) at
1.1.0. - IPM.
zpm "install iris-execute-mcp-v2"installs the IRIS-side classes from the IPM registry, through the existing Open Exchange listingIRIS-MCP-Server-Suite-2. Use it only where the servers cannot install those classes themselves: the first server to connect deploys and upgrades them automatically, and once IPM owns them, upgrades go throughzpmtoo. - Two more clients. Pi and JetBrains Junie are supported by
iris-mcp-clients apply,status,doctorand the other commands, and the skills installer gains anantigravitytarget.
Changed
- A project-scope write from your home directory is refused.
apply,diff,enable,disable,removeandrestorewith--scope project, andskills installandskills uninstall, exit 1 and write nothing when the project directory is your home directory, where the project file would be the user file or would be read for every project. - Current client data (
2026-11-21.1). WithCLAUDE_CONFIG_DIRset, Claude Code's user file is$CLAUDE_CONFIG_DIR/.claude.json; Goose's Windows path is%APPDATA%\Block\goose\config\config.yaml; Windsurf is "Devin Desktop (formerly Windsurf)", Kimi CLI is archived and Roo Code is discontinued, each keeping its adapter so that existing entries can be removed. - The install docs describe the published install. One path per client, every
npxcommand pinned to@1, and the clone-and-build steps in the README's Contributing section. - The release. npm is published with trusted publishing (OIDC, no token) and provenance. The VS Code Marketplace channel is off (
skipped: not enabled) until the owner can register the publisher, and the channels after it still run. A store that is not set up is skipped and listed, never a failure; IPM is the owner's manual step after the tag and never fails or blocks a run; and the Marketplace's rehearsalreadysays that the publisher is not checked.
v0.1.0-alpha
Initial Alpha release. Please see README for installation and usage instructions.