Skip to content

docs: fix stale memory MCP setup #356

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
codeaholicguy merged 1 commit into from
Oct 10, 2026
Merged

docs: fix stale memory MCP setup #356

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 12 additions & 3 deletions web/content/docs/6-memory.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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"]
}
}
}
Expand Down
Loading