Supported hosts
Every coding host and MCP client Strata19 can be installed into, and how each one is configured
Strata19 is one stdio MCP server. Any client that can start a local MCP server can run it; what differs between hosts is how the server gets registered, and whether the host also loads the plugin's skills and lifecycle hooks.
Hosts with a shipped manifest
These hosts have a manifest inside the plugin, so they load its skills and — where the host supports them — its hooks, not just the MCP tools.
| Host | Install | Manifest | What is different about it |
|---|---|---|---|
| Claude Code | Marketplace command | .claude-plugin/plugin.json | the only host that substitutes ${CLAUDE_PLUGIN_ROOT} before spawning the server, so the launcher finds its bundle without searching for it |
| Codex | Marketplace command | .codex-plugin/plugin.json | hooks are non-managed: they are installed but inert until you trust them once with /hooks |
| Antigravity | Copy, then register | plugin.json | performs no variable substitution in its MCP config, and a plugin-local MCP config does not start the server — the same entry has to reach the global config too |
| Claude Desktop | Copy, then register | manifest.json | the only manifest that can carry a user-supplied model key into the server environment, because Desktop substitutes ${user_config.*} and keeps the value in the OS keychain |
Every other MCP client
These have no Strata19 manifest, so they get the MCP tools and nothing else: no skills,
no hooks, and therefore no completion gate. Registration is a hand-written entry in the
host's own config, pointing at server/facade-stdio.js inside a copy of the plugin directory.
The grouping key column is the one that costs people time. Hosts disagree about it, and a server registered under the wrong key is accepted and then ignored — the host starts cleanly and lists no Strata19 tools.
| Client | Grouping key | Config location |
|---|---|---|
| Claude Desktop † | mcpServers | ~/Library/Application Support/Claude/claude_desktop_config.json (macOS), or a .mcpb extension |
| Cursor | mcpServers | .cursor/mcp.json (project) or ~/.cursor/mcp.json (global) |
| Windsurf | mcpServers | ~/.codeium/windsurf/mcp_config.json |
| VS Code / GitHub Copilot Chat | servers | .vscode/mcp.json (project) |
| GitHub Copilot CLI | mcpServers | ~/.copilot/mcp-config.json (or $COPILOT_HOME/mcp-config.json) |
| Zed | context_servers | settings.json → context_servers |
| Gemini CLI | mcpServers | ~/.gemini/settings.json (global) or .gemini/settings.json (project) |
| Kiro | mcpServers | ~/.kiro/settings/mcp.json (global) or .kiro/settings/mcp.json (project) |
| Antigravity IDE † | mcpServers | ~/.gemini/config/mcp_config.json |
| Cline | mcpServers | ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json |
| Continue | mcpServers | ~/.continue/config.yaml (global) or .continue/config.yaml (project) |
| Hermes Agent | mcp_servers | ~/.hermes/config.yaml → mcp_servers: |
| JetBrains AI Assistant | n/a — settings dialog | Settings → Tools → AI Assistant → Model Context Protocol |
| OpenCode | mcp | opencode.json (project) or ~/.config/opencode/opencode.json (global) |
† Claude Desktop and Antigravity IDE also have a shipped manifest. Prefer that route — it is listed in the first table, and it brings the skills and hooks this one does not.
What each level of support actually means
A host appearing in either table above means its configuration is known and recorded. It does not mean every host has been installed and exercised end to end — most have not. Two have been driven against the real shipped bundle rather than a template:
- Claude Desktop, Code tab — the installed bundle was spawned from its own
.mcp.json, spoke real MCP (initialize,tools/list,resources/list, a realtools/call), and served its tools and the widget resource. - OpenCode — registered, connected, and a real turn called a Strata19 tool and received a real result.
For the rest, the configuration shape is researched from that host's own documentation
and the server it points at is the same shipped bundle every other host runs. If you
get one working, or find one that does not, that is evidence this project does not
have — report it with strata19.submit_feedback.
Related
- Install the plugin — the four hosts with a shipped manifest
- Install in any MCP client — the manual route, step by step
- How Strata19 runs — what happens after the server starts
- Troubleshooting — when a host lists the plugin but no tools