Clients
Where Iris is verified to run, and where it is claimed to.
Iris runs inside an MCP client. This is the list of the clients it names, one row each, with what was actually checked: 1 verified by a test on every CI run, 9 claimed from the client's own documentation. Any other MCP client works the same way the claimed rows do — the configuration is one block — and gets a row here when someone checks it.
- verified means
- A test in the repository drives that client's real integration surface — the hook scripts, the manifest, a real ingest read back from the store — on every CI run. The evidence column links the test.
- claimed means
- The installer writes the configuration shape the client's own documentation describes, and that writer is tested on the shape. Nobody on the Iris side has watched that client connect. The source column is the page the shape was read from, with the date.
| Client | What the installer writes | What was checked, and the evidence | Source |
|---|---|---|---|
Claude Code verified | ~/.claude.json, written by claude mcp add; the capture plugin installs from the repository's plugin marketplace | The capture plugin's three hooks (UserPromptSubmit, PostToolUse, Stop) are driven through the real hook scripts with the payload shapes Claude Code documents, ending in a real ingest read back from the store — on every CI run. The MCP plugin's manifest is checked by the docs contract. What is not verified by a test: a live claude session listing the tools; the stranger harness connects over the SDK client, not the product. | the client's MCP documentation read 2026-09-21 |
Claude Desktop claimed | claude_desktop_config.json in the Claude application-data directory, an mcpServers block | The installer writes the mcpServers entry into a dedicated JSON file at the path Claude Desktop documents, keeping existing servers; the writer is tested on that shape. No test launches Claude Desktop. | the client's MCP documentation read 2026-09-21 |
Cursor claimed | ~/.cursor/mcp.json (or a workspace .cursor/mcp.json), an mcpServers block; a one-click install link on the site | The installer writes the mcpServers entry into mcp.json as Cursor's documentation describes; the writer is tested on that shape. No test launches Cursor. | the client's MCP documentation read 2026-09-21 |
Windsurf claimed | ~/.codeium/windsurf/mcp_config.json, an mcpServers block | The installer writes the mcpServers entry into mcp_config.json as Windsurf's documentation (now hosted by Cognition) describes; the writer is tested on that shape. No test launches Windsurf. | the client's MCP documentation read 2026-09-21 |
Continue claimed | ~/.continue/config.json, an mcpServers block beside Continue's other settings | The installer embeds the mcpServers entry in Continue's config.json without touching its other top-level fields; the writer is tested on that shape. No test launches Continue. | the client's MCP documentation read 2026-09-21 |
VS Code claimed | mcp.json in the VS Code user directory (or .vscode/mcp.json in a workspace), a servers block — VS Code's own key, not mcpServers | The installer writes under servers, the key VS Code's native MCP support documents, and uninstalls only its own entry; the writer is tested on that shape. No test launches VS Code. | the client's MCP documentation read 2026-09-21 |
Cline claimed | cline_mcp_settings.json in Cline's global storage under VS Code, an mcpServers block | The installer writes the mcpServers entry into Cline's own settings file as its documentation describes; the writer is tested on that shape. No test launches Cline. | the client's MCP documentation read 2026-09-21 |
Zed claimed | Zed's settings.json, a context_servers entry with a nested command object | The installer writes a nested command object under context_servers, Zed's own key, and preserves unrelated settings; the writer is tested on that shape. No test launches Zed. | the client's MCP documentation read 2026-09-21 |
OpenAI Codex CLI claimed | ~/.codex/config.toml, an [mcp_servers.iris-eval] section | The installer writes an [mcp_servers.iris-eval] TOML section as the Codex configuration reference describes; the writer is tested on that shape. No test launches Codex. | the client's MCP documentation read 2026-09-21 |
Gemini CLI claimed | ~/.gemini/settings.json, an mcpServers block | The installer writes the mcpServers entry into Gemini CLI's settings.json as its documentation describes; the writer is tested on that shape. No test launches Gemini CLI. | the client's MCP documentation read 2026-09-21 |
How a row moves
A claimed row becomes verified when a test in the repository drives that client's real integration surface on every CI run, or when a session in that client is reported with the client's version and the tool list it showed. A row that stops being true is changed, not removed: the rows are locked to the installer's client profiles, so no client is called supported without one. Report a row or read the file itself: clients.json. The install itself is on the home page.