From 1044361e4e96add77908ca25653851791dad47ae Mon Sep 17 00:00:00 2001 From: Hoang Nguyen Date: Sat, 10 Oct 2026 13:13:54 +0000 Subject: [PATCH] docs: fix stale memory MCP setup to setup-first wiring Generated with [Devin](https://devin.ai) Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com> --- web/content/docs/6-memory.md | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/web/content/docs/6-memory.md b/web/content/docs/6-memory.md index d198d6b17..e4f5c8e0e 100644 --- a/web/content/docs/6-memory.md +++ b/web/content/docs/6-memory.md @@ -33,14 +33,23 @@ This is the most powerful way to use Memory. Your AI (Cursor, Claude, etc.) gain ### Setup -Add the server to your MCP configuration file: +Run `ai-devkit setup` once per machine. It wires the memory MCP server — named `ai-devkit-memory`, launched with `npx -y @ai-devkit/memory` — into the global config of every MCP-capable agent it detects: + +| Agent | MCP wiring | +|-------|-----------| +| Claude Code, Codex, Gemini, Cursor, opencode, Grok | Automatic via `setup` | +| Pi | No MCP support by design — use the `memory` skill or `ai-devkit memory` CLI instead | + +`ai-devkit status` reports the wiring state per agent, so you can confirm the server is connected before relying on it. + +If an agent's config is managed manually, you can still add the server yourself: ```json { "mcpServers": { - "memory": { + "ai-devkit-memory": { "command": "npx", - "args": ["@ai-devkit/memory"] + "args": ["-y", "@ai-devkit/memory"] } } }