| Claude Code | - The project `.mcp.json` is shared by convention with the team; never inline a literal API key into it.
- For stdio, `claude mcp add <name> -- <command> [args...]`; for HTTP, `claude mcp add --transport http <name> <url>`.
- Use `--scope user` for a global alternative to the shared project file.
|
| Cursor | - The project `.cursor/mcp.json` is shared by convention; never inline a literal API key into it.
|
| Devin | - In Devin, open Settings → MCP Marketplace → Add Your Own. Configure the server in that UI; Devin does not document a local JSON configuration file for custom MCP servers.
- For LyraShield's remote server, select HTTP (Streamable HTTP) and OAuth, enter the endpoint, then use Test listing tools before enabling it for work.
|
| Devin Desktop / Cascade | - This surface is Devin Desktop's legacy Cascade agent. The Devin Local agent uses separate CLI configuration; cloud Devin is configured in its web MCP Marketplace.
- Teams may disable MCP or restrict servers through allowlists. Cascade has no one-click MCP marketplace; Devin Local uses a separate marketplace.
- Cascade skills live in `.devin/skills`; Cascade hooks are separately configured and must remain opt-in.
|
| GitHub Copilot in VS Code (MCP config) | - VS Code uses `servers`, not `mcpServers`; using `mcpServers` silently fails.
- VS Code stdio entries require `type: "stdio"`; remote entries use `type: "http"`.
- For a user-profile server, run MCP: Open User Configuration or MCP: Add Server. VS Code owns the profile-specific mcp.json path, so do not edit settings.json for MCP configuration.
|
| OpenAI Codex | - Explicit values belong in `[mcp_servers.lyrashield.env]`. Codex reserves `env_vars` for an array of environment-variable names inherited from the parent process.
- Codex remote MCP authentication uses `bearer_token_env_var` or `http_headers`; a `headers` table is not the documented field.
|
| Cline | - Cline CLI reads `~/.cline/data/settings/cline_mcp_settings.json` (override with `CLINE_MCP_SETTINGS_PATH`); IDE extensions expose their own MCP settings JSON through the Cline panel.
- Cline defaults to legacy SSE when `type` is omitted; the remote endpoint needs `type: "streamableHttp"` explicitly.
|
| OpenCode | - OpenCode's global config is `~/.config/opencode/opencode.json`; project `opencode.json` overrides it.
- OpenCode uses single-brace `{env:VAR}` syntax, not `${VAR}`; wrong syntax passes the literal string through.
- OpenCode local entries use `type: "local"`, a command array and `environment`; remote entries use `type: "remote"`.
- OpenCode stores servers under the top-level `mcp` object and uses `enabled: false` to disable an entry.
|
| OpenCode V2 | - OpenCode V2 uses mcp.servers and a nested per-server object; the stable OpenCode entry represents V1 mcp root and is not interchangeable.
- V2 MCP remote connections use OAuth by default and can be authorized through opencode mcp auth lyrashield; do not add a bearer header when using OAuth.
- V2 skill discovery still uses .opencode/skills and ~/.config/opencode/skills and is compatible with the portable Agent Skills layout.
|
| Kilo Code | - Kilo Code uses single-brace `{env:VAR}` syntax, not `${VAR}`; wrong syntax passes the literal string through.
- Kilo Code's file is JSONC; a JSON.parse/stringify round-trip destroys the user's comments.
- Kilo Code local entries use `type: "local"`, a command array and `environment`; remote entries use `type: "remote"`.
|
| Zed | - Current Zed settings use flat command, args and env fields under context_servers. Legacy nested command.path entries should be updated through Zed settings.
- A remote URL without an Authorization header starts Zed's OAuth flow. Keep existing stdio connections unless you deliberately migrate.
- Zed's global settings path is `~/.config/zed/settings.json`; verify it for your platform.
|
| Gemini CLI | - GEMINI.md is the default context file. If context.fileName is customized in settings.json, use one of those configured filenames instead.
- Gemini CLI expands `$VAR_NAME` and `${VAR_NAME}` references in MCP `env` and `headers`; use a reference instead of a literal secret.
- Streamable HTTP servers use `httpUrl`; the `url` field is for SSE endpoints.
- Server name must not contain underscores; use `lyrashield`, never `lyra_shield`.
|
| JetBrains AI Assistant | - JetBrains AI Assistant has no stable MCP file path; use its Settings UI and review the displayed connection status and tool list.
- MCP can be configured for AI Assistant directly. Hosted Claude Agent and Codex have separate entries because their MCP forwarding and skill paths differ.
- Organization-managed IDE Services/Central policies can preconfigure servers or prevent users from adding them.
|
| Junie IDE | - Junie IDE MCP files use the mcpServers JSON object. Keep credentials out of shared project files and provide local environment values outside committed configuration.
- Junie IDE and Junie CLI have separate entries because only the current CLI guide explicitly documents remote OAuth authorization.
- Project settings and skills load only in a trusted project; inspect the IDE connection status and tool list after activation.
|
| Junie CLI | - Junie CLI remote OAuth is available through /mcp and browser authorization. Use that flow instead of a static hosted API key.
- Project MCP and skill configuration is loaded only after project trust. Untrusted projects use temporary isolated project configuration.
- Junie extensions package skills, MCP configurations, commands, guidelines and hooks; the LyraShield extension listing remains PREPARATION.
|
| JetBrains Claude Agent | - The embedded Claude Agent supports Agent Skills and uses Claude-specific project instructions in CLAUDE.md.
- MCP server configuration is shared through AI Assistant settings; the embedded agent provider login does not authenticate the LyraShield MCP connection.
|
| JetBrains Codex Agent | - Codex skills and AGENTS.md are supported in the embedded agent. MCP servers configured in AI Assistant are not exposed until Pass custom MCP servers is enabled.
- The embedded Codex provider login is separate from the LyraShield MCP connection; use local stdio credentials for this guided setup.
|
| Amp | - Amp takes no --env flags for its local stdio CLI; use a local OAuth credential or export a key. Remote HTTP/OAuth is a separate client-managed definition.
- Amp can use global or workspace settings. The CLI command adds an always-available server; use an Agent Skill when the tools should only load for a relevant task.
|
| Pi | - Pi has built-in MCP and OAuth. User servers belong in `~/.pi/agent/mcp.json`; project servers belong in `.pi/mcp.json` and load only after project trust is granted.
- Pi stores OAuth credentials separately from mcp.json. A third-party MCP adapter can replace the built-in MCP support; check `pi mcp list` if configured servers do not load. Pi also discovers shared `.agents/skills` paths, but this installer targets its native user/project skill directories.
|
| OpenClaw | - OpenClaw manages client-side servers with `openclaw mcp add`, `set` and `configure` or in its Control UI at /settings/mcp. Do not use mcporter configuration for OpenClaw-managed servers.
- Local entries use `command` and repeated `--arg` flags. For Streamable HTTP, use `transport: "streamable-http"`; then run `openclaw mcp doctor --probe` for a live tool-list check.
|
| Hermes | - Hermes stores MCP entries under `mcp_servers` in ~/.hermes/config.yaml. It also supports `hermes mcp add` and `hermes mcp test <name>` from the CLI.
- Hermes resolves `${env:VAR}` and `${VAR}` in its YAML configuration. Prefer the environment reference over storing a key in config.yaml.
|
| Antigravity | - Antigravity uses `serverUrl`, not `url`, for HTTP servers — `url` is rejected.
- This registry surface targets Antigravity IDE/2.0. The CLI uses `~/.gemini/antigravity-cli/skills` globally, while its project skills use `.agents/skills`.
- Rules can live in `AGENTS.md`, `GEMINI.md` or `.agents/rules/*.md`; Antigravity 2.0 and the CLI also have distinct global rule directories.
- Antigravity 2.0 and the IDE discover native plugins from `.agents/plugins/` or `~/.gemini/config/plugins/`; the Antigravity CLI installs a local package with `agy plugin install`. LyraShield's plugin artifact is prepared for direct installation, but no public listing or client runtime receipt is confirmed.
|
| GitHub Copilot CLI | - Copilot CLI stdio entries use `type: "local"` (or `"stdio"`); remote uses `type: "http"`.
- Each entry may carry a `tools` array (e.g. ["*"]) to allowlist server tools.
- GitHub's own MCP server is built in — you don't add it manually.
|
| GitHub Copilot Cloud Agent | - Cloud Agent and Copilot code review share repository MCP settings; configured MCP tools are used autonomously, so allowlist read-only tools and review the target repository before enabling them.
- The planned read-only skill set, withheld until a surface-safe bundle is validated, is `get-started`, `review-changes` and `launch-readiness`; the tool allowlist includes only read-only calls. Recorded scans, fixes and retests require an OAuth-capable client.
- GitHub documents `$COPILOT_MCP_...` substitutions for remote headers and requires those values to come from Agents secrets or variables. The key authenticates read-only calls; it cannot grant hosted mutations, which return `connect_required` without a connected OAuth delegation.
- Remote MCP OAuth is not supported by Copilot Cloud Agent. Portable plugin and skills discovery is separate from service authentication; a plugin install or skill discovery is not evidence that the LyraShield MCP server connected.
|
| Goose | - Goose configures MCP servers as `extensions` in ~/.config/goose/config.yaml (YAML, nested map) — not a `mcpServers` JSON dict. Stdio entry: {type: stdio, cmd, args}; remote: {type: streamable_http, uri, headers}.
- Goose has no MCP rules file; project hints live in .goosehints.
|
| Aider | - Aider's official configuration reference has no `mcp-servers` setting or `--mcp-servers` CLI option.
- Use LyraShield's standalone CLI and CI paths until Aider ships an official MCP client contract.
|
| Devin CLI | - Devin CLI v3000.3+ uses dedicated mcp_config files; older main-config mcpServers entries migrate on startup. Inspect and migrate an existing legacy entry before adding a duplicate.
- Remote HTTP uses a bare url and `devin mcp login lyrashield` for OAuth; stdio remains available. MCP tools are namespaced mcp__<server>__<tool>.
|
| Roo Code | - Remote entries MUST use `type: "streamable-http"` (hyphenated); `type: "http"` or `streamableHttp` fails — Roo validates the literal string.
- Project `.roo/mcp.json` overrides the global `mcp_settings.json` in VS Code globalStorage. Entries may carry `alwaysAllow: string[]` and `disabled: boolean`.
|
| MiMo Code | - Root key is `mcp`, not `mcpServers` — using `mcpServers` silently fails.
- Local uses `type: "local"` with `command` as an ARRAY (["npx","-y","<cmd>"]) and `environment` (not `command`+`args`+`env`), plus an `enabled` boolean.
- Remote uses `type: "remote"` with `url` + `headers` and `enabled`; OAuth is handled automatically.
|
| Codebuff | - Codebuff searches project `.agents/mcp.json`, then a parent `.agents/mcp.json`, then global `~/.agents/mcp.json`; later locations override earlier ones.
- Codebuff resolves `$VAR_NAME` references from the launching shell. Never put a literal key in a shared `.agents/mcp.json`.
|
| Oh-My-Pi | - Project config is `.omp/mcp.json`; user config is `~/.omp/agent/mcp.json` (profile-aware at `~/.omp/profiles/<profile>/agent/mcp.json`). Oh-My-Pi also auto-discovers MCP servers from other tools like Claude Code and Cursor.
- Remote uses `type: "http"` for Streamable HTTP; stdio `type` may be omitted (default stdio `{command, args, env}`). Supports OAuth via `auth`/`oauth` fields, plus `/mcp add` and `omp plugin`.
|
| Auggie CLI | - Auggie persists MCP servers in `~/.augment/settings.json`; the documented `auggie mcp add` command also manages this file. HTTP uses a `type: "http"` entry.
- Auggie documents bearer headers for HTTP MCP but does not document OAuth for that transport. A hosted API key does not grant hosted mutation delegation; use stdio with a user-scoped credential for that authorization path.
- Auggie plugins support skills, commands, rules, hooks and MCP, and also accept Claude Code plugin layouts. LyraShield's Auggie marketplace listing remains PREPARATION.
|
| Augment for VS Code | - Skills, commands, MCP servers and rules are configured separately from Auggie CLI plugins. This entry has no persistent MCP config file because the IDE docs provide Settings Panel and JSON import rather than a stable on-disk path.
- Custom MCP remote HTTP/SSE configuration is documented, but generic OAuth or bearer-header authentication for arbitrary custom servers is not. Use local stdio with the LyraShield CLI credential store unless Augment documents that auth contract.
- VS Code Skills and custom commands are Public Beta opt-ins from extension 0.789.0. User guidelines have a separate VS Code extension version gate; see the official rules guide.
|
| Augment for JetBrains | - Skills, commands, MCP servers and rules are configured separately from Auggie CLI plugins. This entry has no persistent MCP config file because the IDE docs provide Settings Panel rather than a stable on-disk path.
- Custom MCP remote HTTP/SSE configuration is documented, but generic OAuth or bearer-header authentication for arbitrary custom servers is not. Use local stdio with the LyraShield CLI credential store unless Augment documents that auth contract.
- JetBrains Skills and custom commands are Public Beta opt-ins from extension 0.428.8; the official docs give no runtime receipt for this registry entry.
|
| Factory Droid | - Droid's plugin system bundles skills, slash commands, hooks, MCP servers and other components. User and project marketplace scopes are separate.
- Remote HTTP MCP uses OAuth Dynamic Client Registration by default and stores tokens in the system keyring or a fallback file. Keep secrets out of project-level `.factory/mcp.json`; the hosted LyraShield endpoint is read-only unless an authorized browser-confirmed delegation is recorded.
- Skills can also be installed in `.factory/skills` or `~/.factory/skills`; avoid committing credentials in project settings.
|
| Qoder IDE | - Qoder IDE MCP and skill import use Extensions UI; the CLI's `.qoder/settings.json` and `.qoder/skills` paths belong to the separate Qoder CLI surface.
- Qoder IDE supports imported plugins bundling skills, MCP, commands, rules and hooks. LyraShield's client package is still in preparation.
- Review MCP permissions and connector authentication in the UI before use; this IDE entry does not inherit Qoder CLI's OAuth flow or configuration paths.
|
| Qoder CLI | - Qoder CLI uses `mcpServers` in `~/.qoder/settings.json` or project `.qoder/settings.json`; project entries require trust and may prompt for approval.
- Remote HTTP OAuth is built into Qoder CLI. Use its `qoder mcp auth` command or `/mcp` flow; do not configure a static hosted API key for delegated actions.
- Native CLI skills live in `.qoder/skills` and `~/.qoder/skills`. Qoder plugins can bundle MCP, commands, skills, hooks and workflows; the LyraShield plugin listing remains PREPARATION.
|
| Qwen Code | - Qwen Code's documented HTTP setting is `httpUrl`; remote OAuth is discovered and handled by the client. Restart the client or use `/mcp` after adding a server.
- Native Qwen extensions can bundle MCP servers, a context file, commands and skills. The extension loader uses `qwen-extension.json`; Agent Plugins v1 is a separate supported format and needs its own tested artifact.
- For cloud-hosted Qwen sessions, configure a reachable OAuth redirect URI; the default localhost redirect works only when the user's browser can reach that session.
|
| Continue | - Continue's project MCP blocks are YAML files under `.continue/mcpServers/`; the required wrapper fields are `name`, `version` and `schema: v1`, with MCP servers represented as a list.
- Continue documents Streamable HTTP but its MCP guide does not document OAuth. This registry entry uses local stdio; do not put a hosted API key in a shared project file.
- Rules are separate files under `.continue/rules`. This entry covers the IDE configuration contract; the Continue CLI surface requires separate acceptance.
|
| Mistral Vibe Code CLI | - The CLI and VS Code extension share configuration, but this registry entry documents the CLI surface. Vibe Code Web is a separate hosted surface.
- Vibe skills can expose slash commands with `user-invocable: true`. Project-level skills load only after the workspace is trusted.
- The official MCP reference says OAuth is not yet supported; static credentials such as an environment-backed API key are required for remote MCP.
|
| Lovable | - Lovable imports skills as Agent Skills from a GitHub URL or ZIP; it does not expose a project-local skill directory for registry-managed writes.
- Custom MCP connectors are workspace chat/build-time tools. They are distinct from integrations embedded in an app generated with Lovable.
- The connector setup defaults to OAuth and supports bearer/API keys as an alternative. Use the OAuth route for hosted delegated workflows.
|
| v0 | - v0 supports custom remote MCP servers with OAuth, bearer tokens or custom headers. No local project config file is documented.
- Vercel Marketplace integrations are a separate route from v0's bring-your-own MCP server configuration; listing eligibility and approval are not established here.
|
| Replit Agent | - Replit supports OAuth dynamic client registration when the MCP server supports it and offers static custom headers as a fallback. LyraShield has a dynamic registration endpoint; client runtime acceptance is still pending.
- Project skills use `/.agents/skills`; workspace-level skills are managed in Workspace Settings. No plugin package format is claimed for Replit Agent.
- Replit scans MCP tool definitions and planned executions; its cloud workspace and permissions remain distinct from local CLI credentials.
|
| Claude Desktop (Remote Connector) | - Claude Desktop remote connectors are brokered from Anthropic's cloud and require a public-reachable MCP server. Local Desktop Extensions are a separate local-only mechanism.
- Team and Enterprise workspaces require an Owner to register the custom connector before individual users connect and authenticate.
|
| Claude Web (Remote Connector) | - Claude web remote connectors use Anthropic's cloud MCP proxy and require a public-reachable endpoint. Local MCP servers and Desktop Extensions are not available on web.
- Team and Enterprise workspaces require an Owner to register the custom connector before individual users connect and authenticate.
|
| Claude Code (Agent Plugin) | - Claude Code may also discover `.claude-plugin/plugin.json`; the package includes a manifest shim in that directory.
- Authenticate through the client-hosted OAuth flow when connecting the remote MCP server.
|
| Cursor (Agent Plugin) | - Cursor discovers Agent Plugins from `~/.cursor/plugins/local/`; the portable `plugin.json` at the plugin root is the manifest.
- Authenticate through the client-hosted OAuth flow when connecting the remote MCP server.
|
| GitHub Copilot in VS Code (Agent Plugin) | - VS Code reads the portable root `plugin.json`; there is no VS Code-specific shim directory. Our manifest declares the Agent Plugins 1.0 `$schema`, so VS Code classifies it as Agent Plugins 1.0 and takes MCP servers from the root `mcp.json`.
- Auto-registration is NOT wired yet, so this path is a staging copy rather than a discovery path. VS Code only auto-discovers plugins under `~/.copilot/installed-plugins/`; everything else arrives via a configured marketplace, Install-from-Source or an explicit entry in the `chat.pluginLocations` setting.
- If plugin installation is unavailable, use the documented `.vscode/mcp.json` MCP configuration fallback. Agent plugins additionally require the `chat.plugins.enabled` setting. Configuration does not establish authenticated client acceptance.
- Authenticate through the client-hosted OAuth flow when connecting the remote MCP server.
|
| OpenAI Codex (Agent Plugin) | - The marketplace preparation branch is not a released install artifact. Use the pinned stdio MCP fallback until a reviewed immutable plugin release exists.
- Local CLI OAuth authentication, Codex server discovery and a successful authenticated read are separate checks.
|
| GitHub Copilot (Agent Plugin) | - GitHub Copilot CLI scans each plugin directory for a `plugin.json` manifest at the root.
- For the current stdio fallback, local CLI OAuth, client discovery and an authenticated read are separate checks.
|
| Kiro (Agent Plugin) | - Import the Kiro Power as the primary setup. The exported `.mcp.kiro.json` merge is a conditional compatibility route when Power import is unavailable; staging a plugin directory alone does not establish MCP discovery.
- Kiro also supports remote HTTP/OAuth using a URL-only MCP entry. Keep stdio as the default until the hosted path has a retained client-runtime receipt.
|
