@softspark/ai-toolkit 2.0.1 → 2.1.0

package/kb/reference/architecture-overview.md

@@ -3,10 +3,10 @@ title: "AI Toolkit - Architecture Overview"
 category: reference
 service: ai-toolkit
 tags: [architecture, overview, design, structure]
-version: "1.4.2"
+version: "1.4.4"
 created: "2026-03-23"
-last_updated: "2026-04-09"
-description: "Architecture of ai-toolkit: directory layout, global install model, skill tiers, and integration with projects."
+last_updated: "2026-04-13"
+description: "Architecture of ai-toolkit: directory layout, global install model, editor-aware MCP install, Codex translation layer, skill tiers, and integration with projects."
 ---
 
 # AI Toolkit Architecture
@@ -105,11 +105,13 @@ Machine (global)                              Project (local)
 **`ai-toolkit update`** — re-apply after `npm install -g @softspark/ai-toolkit@latest` or after `add-rule` / `remove-rule`. Same as `install` but semantically correct for update flows.
 
 **`ai-toolkit install --local`** — run per project. Always installs Claude Code configs (CLAUDE.md, settings.local.json, constitution.md, language rules). Editor configs are opt-in via `--editors`:
-- `--editors all` — install all 8 editors (Cursor, Windsurf, Cline, Roo, Aider, Augment, Copilot, Antigravity)
+- `--editors all` — install all 9 editors (Cursor, Windsurf, Cline, Roo, Aider, Augment, Copilot, Antigravity, Codex)
 - `--editors cursor,aider` — install only selected editors
 - (no flag) — auto-detect from existing project files; `update --local` picks up whatever editors already have configs
 
-Each editor gets directory-based format (`.cursor/rules/*.mdc`, `.windsurf/rules/*.md`, `.clinerules/*.md`, `.roo/rules/*.md`, `.augment/rules/ai-toolkit-*.md`, `.agent/rules/*.md`, `CONVENTIONS.md`). Hooks are global-only — not merged into project settings.
+Each editor gets directory-based format (`.cursor/rules/*.mdc`, `.windsurf/rules/*.md`, `.clinerules/*.md`, `.roo/rules/*.md`, `.augment/rules/ai-toolkit-*.md`, `.agent/rules/*.md`, `CONVENTIONS.md`). Codex local install additionally generates `AGENTS.md`, `.agents/rules/*.md`, `.agents/skills/*`, and `.codex/hooks.json`. Hooks are global-only — not merged into project settings except for editor-native local hook files such as Codex `.codex/hooks.json`. Experimental plugin packs can also layer a global Codex target in `HOME` (`~/AGENTS.md`, `~/.agents/`, `~/.codex/hooks.json`) when installed with `ai-toolkit plugin install --editor codex`.
+
+If a project already has `.mcp.json`, local install mirrors its `mcpServers` entries into `.claude/settings.local.json` plus any selected editors with project-scoped native MCP files (`.cursor/mcp.json`, `.github/mcp.json`).
 
 ## CLI Commands
 
@@ -122,6 +124,8 @@ Each editor gets directory-based format (`.cursor/rules/*.mdc`, `.windsurf/rules
 | `uninstall` | `~/.claude/` | Strips toolkit components (preserves user content) |
 | `add-rule <file>` | `~/.softspark/ai-toolkit/rules/` | Register rule — auto-applied on every `update` |
 | `remove-rule <name>` | `~/.softspark/ai-toolkit/rules/` + `~/.claude/CLAUDE.md` | Unregister rule and remove its block |
+| `mcp add <name...>` | `./.mcp.json` | Merge canonical MCP template(s) into project config |
+| `mcp install --editor <name...>` | native editor config | Render MCP template(s) into editor-native config files |
 | `validate` | toolkit | Integrity check |
 | `doctor` | toolkit | Install health, hooks, benchmark freshness, and artifact drift diagnostics |
 | `benchmark-ecosystem` | toolkit | Benchmark snapshot for official Claude Code and external ecosystem repos |
@@ -140,6 +144,9 @@ Each editor gets directory-based format (`.cursor/rules/*.mdc`, `.windsurf/rules
 | `conventions-md` | `./` | Generates `CONVENTIONS.md` (Aider auto-loaded) |
 | `augment-dir-rules` | `./` | Generates `.augment/rules/ai-toolkit-*.md` |
 | `antigravity-rules` | `./` | Generates `.agent/rules/` + `.agent/workflows/` |
+| `codex-md` | `./` | Generates Codex-facing `AGENTS.md` |
+| `codex-rules` | `./` | Generates `.agents/rules/*.md` |
+| `codex-hooks` | `./` | Generates `.codex/hooks.json` |
 | `agents-md` | toolkit | Regenerates `AGENTS.md` |
 | `llms-txt` | `./` | Generates `llms.txt` |
 | `generate-all` | `./` | Generates all platform configs at once |
@@ -191,6 +198,38 @@ Skills that spawn real parallel agents use:
 
 `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` must be set for Agent Teams (tmux-based) support.
 
+### Codex Translation Layer
+
+Codex does not expose Claude's `Agent`, `Team*`, and `Task*` primitives with the
+same runtime semantics. To keep the skill catalog aligned, local Codex install
+uses a translation layer:
+
+- native Codex-compatible skills are linked directly
+- Claude-only orchestration skills are emitted as generated wrappers
+- wrapper guidance maps delegation to `spawn_agent`, `send_input`, `wait_agent`, `close_agent`, and `update_plan`
+
+Codex therefore receives the full skill catalog, but not the full Claude hook
+surface or tmux-backed Agent Teams lifecycle. Plugin packs reuse the same
+translation and hook-compatibility model when targeting the global Codex layer.
+
+See `kb/reference/codex-cli-compatibility.md` for the detailed mapping.
+
+## MCP Rendering Layer
+
+`.mcp.json` is the canonical project-level template format. ai-toolkit can render that configuration into editor-native MCP files through `scripts/mcp_editors.py`.
+
+Current native adapters:
+- Claude Code: `.claude/settings.local.json` and `~/.claude/settings.json`
+- Cursor: `.cursor/mcp.json` and `~/.cursor/mcp.json`
+- GitHub Copilot: `.github/mcp.json` and `~/.copilot/mcp-config.json`
+- Gemini CLI: `.gemini/settings.json` and `~/.gemini/settings.json`
+- Windsurf: `~/.codeium/windsurf/mcp_config.json`
+- Cline: `~/.cline/data/settings/cline_mcp_settings.json`
+- Augment: `~/.augment/settings.json`
+- Codex CLI: `~/.codex/config.toml`
+
+See `kb/reference/mcp-editor-compatibility.md` for the support matrix and scope rules.
+
 ## Quality Guardrails
 
 ### Anti-Rationalization Tables

package/kb/reference/claude-ecosystem-expansion-foundations.md

@@ -5,8 +5,8 @@ service: ai-toolkit
 tags: [benchmark, claude-code, ecosystem, hooks, plugins, architecture]
 version: "1.0.0"
 created: "2026-03-27"
-last_updated: "2026-04-01"
-description: "Reference summary of the ecosystem signals and implementation foundations adopted in ai-toolkit."
+last_updated: "2026-04-13"
+description: "Reference summary of the ecosystem signals and implementation foundations adopted in ai-toolkit, including runtime-aware plugin packaging."
 ---
 
 # Claude Ecosystem Expansion Foundations
@@ -19,13 +19,13 @@ This document captures the architectural foundations adopted in `ai-toolkit` aft
 2. official Claude Code patterns,
 3. selected external benchmark repositories.
 
-The outcome is a toolkit that is now positioned as a more modular, Claude-native, benchmark-backed system with stronger lifecycle automation and extension tooling.
+The outcome is a toolkit that is now positioned as a more modular, Claude-first, benchmark-backed system with stronger lifecycle automation and extension tooling.
 
 ## Implemented Foundations
 
 ### 1. Plugin-oriented structure
 
-`ai-toolkit` now treats plugin packaging as a first-class capability.
+`ai-toolkit` now treats plugin packaging as a first-class capability, with runtime-aware install surfaces for Claude and optional global Codex layering.
 
 Implemented artifacts:
 - `app/.claude-plugin/plugin.json`

package/kb/reference/codex-cli-compatibility.md

@@ -0,0 +1,136 @@
+---
+title: "AI Toolkit - Codex CLI Compatibility"
+category: reference
+service: ai-toolkit
+tags: [codex, compatibility, install, skills, hooks]
+version: "1.0.0"
+created: "2026-04-12"
+last_updated: "2026-04-13"
+description: "Reference for how ai-toolkit maps Claude-oriented skills, hooks, and plugin packs to Codex CLI."
+---
+
+# AI Toolkit - Codex CLI Compatibility
+
+## Summary
+
+Codex CLI now receives the full `ai-toolkit` skill catalog during local install.
+
+Native Codex-compatible skills are linked directly into `.agents/skills/`. Skills
+that depend on Claude-only orchestration primitives are generated as Codex
+wrappers that preserve the original workflow intent while translating execution
+to Codex subagents and plan tracking.
+
+Experimental plugin packs can also target a global Codex surface with
+`ai-toolkit plugin install --editor codex`, which layers plugin-specific skills,
+rules, and hooks into `HOME` without changing the project-local core install
+model.
+
+## Local Install Outputs
+
+`ai-toolkit install --local --editors codex` generates:
+
+- `AGENTS.md`
+- `.agents/rules/*.md`
+- `.agents/skills/*`
+- `.codex/hooks.json`
+
+## Global Plugin Outputs
+
+`ai-toolkit plugin install --editor codex <pack>` bootstraps or reuses:
+
+- `~/AGENTS.md`
+- `~/.agents/rules/*.md`
+- `~/.agents/skills/*`
+- `~/.codex/hooks.json`
+
+Plugin packs only add their own runtime-specific layer on top of the generated
+Codex base. Shared hook scripts and plugin scripts still live in
+`~/.softspark/ai-toolkit/`.
+
+## Skill Translation Model
+
+Two delivery modes are used for Codex:
+
+| Mode | How it is installed | Use case |
+|------|----------------------|----------|
+| Native | Symlink to `app/skills/<name>/` | Skills whose `allowed-tools` are already supported in Codex |
+| Adapted | Generated wrapper directory in `.agents/skills/<name>/` | Skills that rely on Claude-only `Agent`, `Team*`, or `Task*` primitives |
+
+Adapted skills keep the same support assets (`reference/`, `scripts/`, `assets/`)
+via symlinks, but rewrite `SKILL.md` to Codex-native guidance.
+
+## Claude-to-Codex Tool Mapping
+
+The adapter rewrites Claude-specific delegation guidance to the closest Codex
+runtime primitives:
+
+| Claude-oriented primitive | Codex replacement |
+|---------------------------|------------------|
+| `Agent(...)` | `spawn_agent(..., fork_context=True, ...)` |
+| `SendMessage` | `send_input` |
+| `TaskCreate` / `TaskList` / `TaskUpdate` | `update_plan` or explicit checklist tracking |
+| `TaskGet` / `TaskOutput` | `wait_agent` |
+| `TaskStop` / `TeamDelete` | `close_agent` |
+| Agent teams | Multiple spawned subagents with explicit file ownership |
+
+## Adapted Skill Classes
+
+The main adapted group is multi-agent orchestration:
+
+- `/orchestrate`
+- `/workflow`
+- `/swarm`
+- `/teams`
+- `/subagent-development`
+
+The adapter also covers skills that previously depended only on Claude's
+`Agent` primitive, such as:
+
+- `/tdd`
+- `/write-a-prd`
+- `/qa-session`
+- `/triage-issue`
+- `/architecture-audit`
+
+## Hook Compatibility
+
+Codex does not expose the full Claude hook event surface. The Codex hook
+generator emits only the events supported by Codex runtime integration:
+
+- `SessionStart`
+- `PreToolUse`
+- `PostToolUse`
+- `UserPromptSubmit`
+- `Stop`
+
+This means Claude-only events such as `TaskCompleted`, `TeammateIdle`,
+`SubagentStart`, `SubagentStop`, `PreCompact`, `SessionEnd`, and
+`Notification` are not available in `.codex/hooks.json`.
+
+## Behavioral Limits
+
+Codex wrappers preserve workflow intent, but not every Claude runtime behavior
+has a perfect one-to-one equivalent.
+
+Known limits:
+
+- No native Codex equivalent of tmux-backed Agent Teams lifecycle events
+- No separate task object model equivalent to Claude `Task*` APIs
+- Hook event coverage is narrower than Claude Code
+
+These are runtime platform limits, not installation defects.
+
+## Verification
+
+The Codex compatibility path is verified by:
+
+1. Generator contract tests for `generate_codex.py`
+2. Local install tests for `.agents/skills/` and `.codex/hooks.json`
+3. Plugin install tests for global Codex rules, hooks, and cleanup paths
+4. CLI tests for `codex-md` and `codex-hooks`
+
+## Related
+
+- `kb/reference/skills-catalog.md`
+- `kb/reference/architecture-overview.md`
+- `kb/reference/global-install-model.md`

package/kb/reference/extension-api.md

@@ -2,11 +2,11 @@
 title: "Extension API Reference"
 category: reference
 service: ai-toolkit
-tags: [extension-api, inject-rule, inject-hook, mcp-templates, integration]
-version: "1.3.8"
+tags: [extension-api, inject-rule, inject-hook, mcp-templates, integration, editors]
+version: "1.3.9"
 created: "2026-04-07"
-last_updated: "2026-04-07"
-description: "Reference for ai-toolkit's extension API: inject-rule, inject-hook, remove-rule, remove-hook, and mcp template management."
+last_updated: "2026-04-12"
+description: "Reference for ai-toolkit's extension API: inject-rule, inject-hook, remove-rule, remove-hook, and editor-aware MCP template management."
 ---
 
 # Extension API Reference
@@ -27,6 +27,7 @@ This design is intentional: ai-toolkit is a generic toolkit. Consumers (MCP serv
 | `remove-hook <name>` | `~/.claude/settings.json` | Strip all entries with matching `_source` | Yes |
 | `add-rule <file.md>` | `~/.softspark/ai-toolkit/rules/` | File copy + re-inject all rules on next `update` | Yes |
 | `mcp add <name...>` | `.mcp.json` | Merge `mcpServers` block from template | Yes |
+| `mcp install --editor <name...>` | Native editor MCP config | Render canonical template into editor format | Yes |
 
 ## inject-rule
 
@@ -103,7 +104,7 @@ npx @softspark/ai-toolkit remove-hook my-tool-hooks
 
 The argument is the source name (file stem used during `inject-hook`). If no entries with that source are present, the command exits 0 silently.
 
-## mcp add
+## mcp add / install
 
 Merges one or more MCP server templates from `app/mcp-templates/` into the project's `.mcp.json`.
 
@@ -111,13 +112,24 @@ Merges one or more MCP server templates from `app/mcp-templates/` into the proje
 ai-toolkit mcp add github                # add a single template
 ai-toolkit mcp add github postgres slack  # add multiple at once
 ai-toolkit mcp list                       # list all available templates
+ai-toolkit mcp editors                    # list supported native adapters
 ai-toolkit mcp show github                # print a template's JSON
+ai-toolkit mcp install --editor cursor --scope project github --target .
+ai-toolkit mcp install --editor codex context7
 ai-toolkit mcp remove github             # remove an entry from .mcp.json
+ai-toolkit mcp remove github --editor cursor --scope project --target .
 ```
 
 **Implementation:** `scripts/mcp_manager.py`.
 
-The `add` command merges the `mcpServers` block from the template into `.mcp.json`. If `.mcp.json` does not exist, it is created. If the server name already exists, the entry is overwritten. See [mcp-templates.md](mcp-templates.md) for the full list of available templates.
+The `add` command merges the `mcpServers` block from the template into `.mcp.json`. If `.mcp.json` does not exist, it is created. If the server name already exists, the entry is overwritten.
+
+The `install` command renders the same canonical template into a native editor config format. Supported adapters currently cover:
+- JSON clients with `mcpServers`: Claude Code, Cursor, Gemini CLI, Windsurf, Cline, Augment
+- JSON clients with additional required metadata: GitHub Copilot
+- TOML clients: Codex CLI
+
+When `install` runs with `--scope project`, ai-toolkit also updates `.mcp.json` so the project-level config remains the source of truth for later sync and local install flows.
 
 ## Architecture
 
@@ -132,6 +144,7 @@ The `add` command merges the `mcpServers` block from the template into `.mcp.jso
 │    remove-hook  <name>        → settings.json        │
 │    add-rule     <file.md>     → rules/ registry      │
 │    mcp add      <template>    → .mcp.json            │
+│    mcp install  <template>    → editor-native MCP    │
 │                                                      │
 │  Idempotent: markers (rules) / _source tags (hooks)  │
 │  ai-toolkit NEVER calls external services            │
@@ -157,6 +170,9 @@ npx @softspark/ai-toolkit inject-hook ./hooks/my-tool-hooks.json
 
 # Add an MCP server template
 npx @softspark/ai-toolkit mcp add github
+
+# Render the same template into Cursor project config
+npx @softspark/ai-toolkit mcp install --editor cursor --scope project github --target .
 ```
 
 To uninstall:
@@ -172,4 +188,5 @@ All operations are idempotent — safe to run on every install or update.
 
 - [PATH: kb/reference/hooks-catalog.md] — built-in hooks reference
 - [PATH: kb/reference/mcp-templates.md] — available MCP server templates
+- [PATH: kb/reference/mcp-editor-compatibility.md] — native editor MCP support matrix
 - [PATH: kb/reference/architecture-overview.md] — overall install model

package/kb/reference/global-install-model.md

@@ -2,11 +2,11 @@
 title: "Global Install Model"
 category: reference
 service: ai-toolkit
-tags: [install, global, claude, local-setup]
-version: "1.4.2"
+tags: [install, global, claude, codex, plugins, local-setup]
+version: "1.4.4"
 created: "2026-03-26"
-last_updated: "2026-04-09"
-description: "Reference description of the global install target, local project setup, and command responsibilities in ai-toolkit."
+last_updated: "2026-04-13"
+description: "Reference description of the global install target, project-local editor setup, global Codex plugin layering, and command responsibilities in ai-toolkit."
 ---
 
 # Global Install Model
@@ -17,6 +17,10 @@ description: "Reference description of the global install target, local project
 
 That means one machine-level install provides agents, skills, hooks, and rules to every project without committing toolkit boilerplate into each repository.
 
+Codex remains project-local for the core toolkit install, but experimental
+plugin packs can now layer a global Codex target in `HOME` when explicitly
+installed with `ai-toolkit plugin install --editor codex`.
+
 ## Command Responsibilities
 
 | Command | Target | Purpose |
@@ -29,6 +33,11 @@ That means one machine-level install provides agents, skills, hooks, and rules t
 | `ai-toolkit update --local` | current project | refresh project configs; auto-detects editors from existing files |
 | `ai-toolkit add-rule` | `~/.softspark/ai-toolkit/rules/` | register a global rule |
 | `ai-toolkit remove-rule` | `~/.softspark/ai-toolkit/rules/` | unregister a global rule |
+| `ai-toolkit mcp add <name...>` | current project | merge MCP templates into `.mcp.json` |
+| `ai-toolkit mcp install --editor <name...>` | editor-native config | render MCP templates into editor-specific config files |
+| `ai-toolkit plugin install --editor claude|codex|all <name>` | runtime-native config | install plugin pack for selected runtime(s) |
+| `ai-toolkit plugin update --editor claude|codex|all <name>` | runtime-native config | re-apply plugin pack after toolkit updates |
+| `ai-toolkit plugin remove --editor claude|codex|all <name>` | runtime-native config | remove plugin pack from selected runtime(s) |
 
 ## Why global install is the default
 
@@ -39,10 +48,17 @@ That means one machine-level install provides agents, skills, hooks, and rules t
 
 ## What remains project-local
 
-These files still stay local to a repository:
+These files still stay local to a repository as part of the core install model:
 - `CLAUDE.md`
 - `.claude/settings.local.json`
+- `.mcp.json`
+- `.cursor/mcp.json`
+- `.github/mcp.json`
 - `.claude/constitution.md`
+- project `AGENTS.md`
+- project `.agents/rules/*.md`
+- project `.agents/skills/*`
+- project `.codex/hooks.json`
 - `.github/copilot-instructions.md`
 - `.clinerules`
 - `.roomodes`
@@ -54,7 +70,48 @@ These files still stay local to a repository:
 
 Hooks do **not** live in project-local settings. They are merged only into global `~/.claude/settings.json`.
 
+Codex is the exception in terms of file location, not hook ownership: its local
+`.codex/hooks.json` points to hook scripts already installed globally in
+`~/.softspark/ai-toolkit/hooks/`.
+
+## Codex Local Install Behavior
+
+`ai-toolkit install --local --editors codex` creates:
+
+- `AGENTS.md`
+- `.agents/rules/*.md`
+- `.agents/skills/*`
+- `.codex/hooks.json`
+
+Native Codex-compatible skills are linked directly. Claude-oriented skills that
+depend on `Agent`, `Team*`, or `Task*` primitives are translated into generated
+Codex wrappers so the project still receives the full skill catalog.
+
+## Codex Global Plugin Layer
+
+`ai-toolkit plugin install --editor codex <pack>` additionally targets:
+
+- `~/AGENTS.md`
+- `~/.agents/rules/*.md`
+- `~/.agents/skills/*`
+- `~/.codex/hooks.json`
+
+This is not the default core install path. It is an explicit, opt-in plugin
+layer used only for plugin packs. Runtime state is tracked in
+`~/.softspark/ai-toolkit/plugins.json` per target (`claude`, `codex`).
+
+## MCP Local Sync Behavior
+
+If `.mcp.json` exists in the current project, `ai-toolkit install --local` mirrors its `mcpServers` block into:
+- `.claude/settings.local.json`
+- `.cursor/mcp.json` when `--editors cursor` is selected
+- `.github/mcp.json` when `--editors copilot` is selected
+
+Global-only editor MCP configs are not written during `install --local`. Use `ai-toolkit mcp install --editor <name...>` for those targets.
+
 ## Related Documents
 
 - `kb/reference/distribution-model.md`
 - `kb/reference/merge-friendly-install-model.md`
+- `kb/reference/codex-cli-compatibility.md`
+- `kb/reference/mcp-editor-compatibility.md`

package/kb/reference/mcp-editor-compatibility.md

@@ -0,0 +1,62 @@
+---
+title: "AI Toolkit - MCP Editor Compatibility"
+category: reference
+service: ai-toolkit
+tags: [mcp, editors, compatibility, codex, cursor]
+version: "1.0.0"
+created: "2026-04-12"
+last_updated: "2026-04-12"
+description: "Official MCP support matrix and native config targets for editors supported by ai-toolkit."
+---
+
+# MCP Editor Compatibility
+
+## Overview
+
+ai-toolkit keeps `.mcp.json` as the project-level canonical template format and can render that config into native editor MCP files where the editor exposes a stable, documented configuration surface.
+
+## Supported Native Adapters
+
+| Editor | Scope | Native Config Path | Adapter Behavior |
+|--------|-------|--------------------|------------------|
+| Claude Code | project + global | `.claude/settings.local.json`, `~/.claude/settings.json` | Merges `mcpServers` while preserving other settings keys |
+| Cursor | project + global | `.cursor/mcp.json`, `~/.cursor/mcp.json` | Mirrors `mcpServers` directly |
+| GitHub Copilot | project + global | `.github/mcp.json`, `~/.copilot/mcp-config.json` | Adds Copilot-required `type` and `tools` fields |
+| Gemini CLI | project + global | `.gemini/settings.json`, `~/.gemini/settings.json` | Merges `mcpServers` into settings JSON |
+| Windsurf | global | `~/.codeium/windsurf/mcp_config.json` | Global-only JSON config |
+| Cline | global | `~/.cline/data/settings/cline_mcp_settings.json` | Global-only JSON config |
+| Augment | global | `~/.augment/settings.json` | Global-only JSON settings file |
+| Codex CLI | global | `~/.codex/config.toml` | Renders JSON templates as TOML `mcp_servers` tables |
+
+## Unsupported for Automatic Install
+
+These editors are still supported by ai-toolkit for rules and instructions, but ai-toolkit does not currently auto-write MCP config because a stable official file target was not adopted:
+
+| Editor | Reason |
+|--------|--------|
+| Roo Code | MCP support exists, but no verified official file path was adopted in ai-toolkit |
+| Aider | No verified native MCP config surface was adopted in ai-toolkit |
+| Google Antigravity | MCP can be configured via UI/import flows, but no stable file target was adopted in ai-toolkit |
+
+## CLI
+
+```bash
+ai-toolkit mcp editors
+ai-toolkit mcp install --editor cursor --scope project github --target .
+ai-toolkit mcp install --editor codex context7
+ai-toolkit mcp remove github --editor cursor --scope project --target .
+```
+
+## Install Flow Integration
+
+When `.mcp.json` exists in a project, `ai-toolkit install --local` mirrors its servers into:
+- `.claude/settings.local.json`
+- `.cursor/mcp.json` when `--editors cursor` is selected
+- `.github/mcp.json` when `--editors copilot` is selected
+
+Global-only clients are configured explicitly via `ai-toolkit mcp install --editor ...`.
+
+## Related
+
+- [PATH: kb/reference/mcp-templates.md] — template catalog and CLI
+- [PATH: kb/reference/extension-api.md] — extension API surface

package/kb/reference/mcp-templates.md

@@ -2,33 +2,58 @@
 title: "MCP Server Templates"
 category: reference
 service: ai-toolkit
-tags: [mcp, templates, servers, configuration]
-version: "1.0.0"
+tags: [mcp, templates, servers, configuration, editors]
+version: "1.1.0"
 created: "2026-04-07"
-last_updated: "2026-04-07"
-description: "Reference for 25 MCP server configuration templates: GitHub, PostgreSQL, Slack, Sentry, and more."
+last_updated: "2026-04-12"
+description: "Reference for 25 MCP server templates plus native editor MCP installation support."
 ---
 
 # MCP Server Templates
 
 ## Overview
 
-ai-toolkit ships 25 ready-to-use MCP server configuration templates in `app/mcp-templates/`. Each template is a JSON file that defines the `mcpServers` block for a specific service. Templates are merged into the project's `.mcp.json` via the `ai-toolkit mcp` CLI subcommand.
+ai-toolkit ships 25 ready-to-use MCP server configuration templates in `app/mcp-templates/`. Each template is a JSON file that defines the canonical `mcpServers` block for a specific service. Templates can be merged into the project's `.mcp.json` and rendered into editor-native MCP config files via the `ai-toolkit mcp` CLI subcommand.
 
 ## CLI
 
 ```bash
 ai-toolkit mcp list               # List all available templates
+ai-toolkit mcp editors            # List editors with native MCP adapters
 ai-toolkit mcp show <name>        # Print a template's JSON config
 ai-toolkit mcp add <name>         # Merge a template into .mcp.json
 ai-toolkit mcp add <n1> <n2>      # Add multiple templates at once
-ai-toolkit mcp remove <name>      # Remove a server entry from .mcp.json
+ai-toolkit mcp install --editor cursor --scope project github --target .
+ai-toolkit mcp install --editor codex context7
+ai-toolkit mcp remove <name>      # Remove from .mcp.json or native editor config
 ```
 
 **Implementation:** `scripts/mcp_manager.py`
 
 The `add` command merges the `mcpServers` block from the template into `.mcp.json`. If `.mcp.json` does not exist it is created. If the server name already exists in `.mcp.json`, the entry is overwritten with the template version.
 
+The `install` command renders the same canonical template into an editor-native config format:
+- JSON clients with `mcpServers` blocks: Claude Code, Cursor, Gemini CLI, Windsurf, Cline, Augment
+- JSON clients with additional transport metadata: GitHub Copilot
+- TOML clients: Codex CLI (`[mcp_servers.<name>]`)
+
+When `install` runs with `--scope project`, ai-toolkit also updates the project's `.mcp.json` so it remains the source of truth for later syncs.
+
+## Editor Support Matrix
+
+| Editor | Scope | Native Config Path | Notes |
+|--------|-------|--------------------|-------|
+| `claude` | project + global | `.claude/settings.local.json`, `~/.claude/settings.json` | Preserves existing hooks and env keys |
+| `cursor` | project + global | `.cursor/mcp.json`, `~/.cursor/mcp.json` | Mirrors canonical `mcpServers` |
+| `copilot` | project + global | `.github/mcp.json`, `~/.copilot/mcp-config.json` | Adds `type` and `tools: ["*"]` automatically |
+| `gemini` | project + global | `.gemini/settings.json`, `~/.gemini/settings.json` | Uses Gemini CLI `mcpServers` format |
+| `windsurf` | global | `~/.codeium/windsurf/mcp_config.json` | Global-only official config |
+| `cline` | global | `~/.cline/data/settings/cline_mcp_settings.json` | Global-only official config |
+| `augment` | global | `~/.augment/settings.json` | Global-only settings file |
+| `codex` | global | `~/.codex/config.toml` | Rendered as TOML `mcp_servers` tables |
+
+Project-local `ai-toolkit install --local` also mirrors `.mcp.json` into Claude project settings plus selected project editors that have official repository/workspace MCP files (`cursor`, `copilot`).
+
 ## Template List
 
 | Name | Description | Required Env Vars |
@@ -108,3 +133,4 @@ export GITHUB_PERSONAL_ACCESS_TOKEN=ghp_...
 
 - [PATH: kb/reference/extension-api.md] — `mcp add` as part of the extension API
 - [PATH: kb/reference/architecture-overview.md] — overall install model
+- [PATH: kb/reference/mcp-editor-compatibility.md] — native editor MCP support matrix