Add coding-agent MCP bootstrap

README.md

@@ -194,8 +194,21 @@ cmdforge mcp add remote --transport streamable-http --url https://example.com/mc
 cmdforge mcp connect remote
 cmdforge mcp serve                    # Expose approved tools over stdio
 cmdforge mcp serve --transport streamable-http  # Loopback-only HTTP by default
+
+# Connect a coding agent and add a managed project policy
+cmdforge mcp configure codex --dry-run
+cmdforge mcp configure codex
+cmdforge mcp configure claude-code --scope project
 ```
 
+`mcp configure` registers CmdForge's stdio server through the host's own CLI
+and adds an idempotent managed block to `AGENTS.md` (Codex) or `CLAUDE.md`
+(Claude Code). It preserves all text outside that block. Preview with
+`--dry-run`, skip the policy with `--no-policy`, or deliberately replace an
+existing registration with `--force`. Setup never broadens the MCP exposure
+allowlist: review tools and add their names under `server.expose` in
+`~/.cmdforge/mcp.yaml`.
+
 `cf` searches the public registry when no local tool matches. Registry results
 show available relevance and quality evidence and install on selection.
 When local pipeline discovery is explicitly enabled, `cf` also suggests
@@ -226,7 +239,9 @@ echo "Create a conventional commit-message tool" | forge-tool --name commit-msg
 `run-once` honors `cmdforge config set default_provider NAME`, then selects an
 available configured provider when no default is set. Configure CmdForge as an
 MCP server when the assistant supports MCP so approved tools appear in its
-native tool catalog.
+native tool catalog. `cmdforge mcp configure codex` and
+`cmdforge mcp configure claude-code` automate the host registration and add
+the discovery policy shown above to the host's project instruction file.
 
 ### Running Tools