IDE-адаптеры
Поддерживаются 30 целей, и у каждой есть собственный адаптер, который читает формат конфигурации цели, идемпотентно объединяет записи и сохраняет резервную копию исходного файла перед записью. MCP-конфигурация поддерживается во всех адаптерах с поддержкой MCP. Skills автоматически применяются на 22 целях, а rules — на 9. CLI также выполняет post-install verification, чтобы повторно проверить запись адаптера после сохранения.
Представительные цели
Каждый адаптер — это отдельный модуль в packages/adapters. Он определяет путь к конфигу цели, объединяет новые MCP-записи (и при необходимости skills/rules), создаёт резервную копию с timestamp перед записью и должен проходить этап post-install verification в CLI.
Cursor
MCP + Skills + Rules.cursor/mcp.json or ~/.cursor/mcp.json + .cursor/skills/ + .cursor/rules/Workspace-scoped or user-scoped MCP JSON plus native Cursor skills/rules folders. Project scope takes precedence when you apply at workspace scope.
Windsurf
MCP + Skills + Rules~/.codeium/windsurf/mcp_config.json + ~/.codeium/windsurf/skills/ or .windsurf/skills/ + global_rules.md or .devin/rules/Current Devin/Windsurf documentation prefers workspace rules under .devin/rules/, retains .windsurf/rules/ as a fallback, and keeps global rules in ~/.codeium/windsurf/memories/global_rules.md.
Visual Studio Code
MCP<VS Code User>/mcp.json or .vscode/mcp.jsonUses VS Code's native servers object in user or workspace mcp.json configuration.
Claude Code
MCP + Skills~/.claude.jsonAnthropic's Claude Code CLI reads mcpServers from the root ~/.claude.json file.
Gemini CLI
MCP + Skills~/.gemini/settings.json or .gemini/settings.json + .gemini/skills/Gemini CLI reads MCP settings from settings.json and discovers skills from .gemini/skills/ at user or workspace scope.
Codex CLI
MCP~/.codex/config.toml or .codex/config.tomlCodex CLI uses a TOML-formatted config for both user and trusted project scope. Remote MCP servers must serialize into Codex's native HTTP fields.
Antigravity
MCP~/.gemini/antigravity/mcp_config.jsonGoogle Gemini's Antigravity agent reads MCP config from its own scoped path.
Zed
MCP + Skills~/.config/zed/settings.json (context_servers) + ~/.agents/skills/ or .agents/skills/Zed uses context_servers inside settings.json and documents global/project Agent Skills under ~/.agents/skills/ and .agents/skills/.
JetBrains Junie
MCP~/.junie/mcp/mcp.json or .junie/mcp/mcp.jsonJetBrains Junie currently uses a dedicated .junie/mcp/mcp.json surface for user or project MCP configuration.
Kiro
MCP + Skills~/.kiro/settings/mcp.json + ~/.kiro/skills/ or .kiro/skills/Kiro stores MCP config in .kiro/settings/mcp.json and documents both global and workspace-scoped agent skills under .kiro/skills/.
Cline CLI
MCP~/.cline/data/settings/cline_mcp_settings.jsonCline CLI reads its own MCP settings file from the CLI data directory. Skills/rules auto-apply is intentionally not advertised yet.
DeepSeek-TUI
MCP~/.deepseek/mcp.jsonDeepSeek-TUI reads MCP configuration from its scoped home directory. Skills/rules auto-apply is not yet supported.
Continue
MCP + Skills~/.continue/config.yaml + .continue/prompts/*.promptContinue's current config surface is config.yaml. MCP servers serialize into the documented mcpServers YAML list, while VibeBasket writes prompt files and registers them under prompts.
Roo Code
MCP + Skills + Rules.roo/mcp.json or <VS Code globalStorage>/RooVeterinaryInc.roo-cline/settings/mcp_settings.json + .roo/skills/ + .roo/rules/MCP entries merge into Roo Code's project or global settings file. Skills and rules are written into Roo-native .roo directories.
Hermes
MCP + Skills~/.hermes/config.yaml + .hermesrulesMCP servers merge into the YAML config. Rules and skills are written into .hermesrules using idempotent block delimiters.
OpenClaw
MCP + Skills~/.openclaw/openclaw.json + .openclawrulesMCP entries merge into the JSON config. Rules and skills are written into .openclawrules using idempotent block delimiters.
GitHub Copilot
MCP + Skills + Rules.mcp.json + .github/copilot-instructions.mdPortable MCP entries are written to .mcp.json; rules and skills remain in Copilot's project instructions file.
Void Editor
MCP~/.void-editor/mcp.jsonThe current auto-apply surface is the official user-scope Void MCP config. Project-scoped skills/rules are intentionally not advertised until per-feature scope handling is modelled cleanly.
Aider
Skills + Rules.aider.conf.yml + .aiderinstructions.mdRegisters .aiderinstructions.md via the read flag in .aider.conf.yml. Rules and skills are written into the instructions Markdown file.
Cortex Code
MCP + Skills~/.snowflake/cortex/mcp.json + .cortex/skills/Snowflake's Cortex Code agent. MCP entries merge into the cortex JSON config. Skills are written as individual Markdown files under .cortex/skills/.
Goose
MCP~/.config/goose/config.yamlBlock/Anthropic's Goose agent reads MCP extensions from its YAML config file. Restart Goose after applying.
IBM Bob
MCP + Skills~/.bob/mcp_settings.json or .bob/mcp.jsonIBM Bob supports both user-global and project-scoped MCP config. Skills are written under .bob/skills/ as Markdown files.
CodeBuddy
MCP + Skills~/.codebuddy/.mcp.json or .mcp.jsonTencent Cloud CodeBuddy reads MCP config from user or project scope. Skills are written under .codebuddy/skills/ as Markdown files.
OpenCode
MCP + Skills + Rules~/.config/opencode/opencode.json or opencode.json + .opencode/skills/ + AGENTS.mdOpenCode uses the mcp object in opencode.json, plus .opencode/skills and AGENTS.md for reusable behavior. Reload the TUI after applying.
Ante
MCP + Skills~/.ante/settings.json (mcp_servers) + ~/.ante/skills/ or .ante/skills/Ante keeps MCP at user scope and discovers Agent Skills from native user or project directories.
Trae
MCP + Skills + Rules.trae/mcp.json + ~/.trae/skills/ or .trae/skills/ + .trae/rules/Trae MCP and rules are project-scoped, while Agent Skills support user or project scope. Enable project MCP, then reload the workspace.
Qoder
MCP + Skills + Rules~/.qoder/settings.json or .mcp.json + ~/.qoder/skills/ or .qoder/skills/ + .qoder/rules/Qoder supports user/project MCP and Agent Skills; rules are project-scoped. Run /mcp reload after applying.
OMP (Oh My Pi)
MCP + Skills + Rules~/.omp/agent/{mcp.json,skills/,rules/} or .omp/{mcp.json,skills/,rules/}OMP uses schema-backed, profile-aware user paths and matching project paths. PI_CONFIG_DIR, PI_CODING_AGENT_DIR, and OMP_PROFILE overrides are honored.
Autohand Code
MCP + Skills~/.autohand/config.json or .autohand/config.json (mcp.servers) + ~/.autohand/skills/ or .autohand/skills/Autohand uses a named server array under mcp.servers and native user/project Skill paths. AUTOHAND_CONFIG/AUTOHAND_HOME are honored; TOML or YAML configs are never overwritten.
Crush
MCP + Skills~/.config/crush/crushrc or .crushrc + ~/.config/crush/skills/ or .crush/skills/Crush MCP uses shell-quoted, idempotent managed blocks; Agent Skills use native user/project directories. Review executable crushrc changes before launch.