Agent Setup
Configure mem/ctl in any MCP-compatible AI agent
Agent Setup
Every agent below connects to mem/ctl the same way - run npx memctl auth once, then add your org and project to the agent's MCP config. No token in project files.
npx memctl auth
npx memctl hook-adapter --agent all --writeQuick reference
| Agent | Config location | Config key | Auto-setup | Instruction file |
|---|---|---|---|---|
| Claude Code | .mcp.json | mcpServers | memctl init --claude | generate --claude |
| Cursor | .cursor/mcp.json | mcpServers | memctl init --cursor | generate --cursor-rule |
| VS Code + Copilot | .vscode/mcp.json | servers | memctl init --vscode | generate --copilot |
| Windsurf | ~/.codeium/windsurf/mcp_config.json | mcpServers | memctl init --windsurf | generate --windsurf |
| Codex | .codex/config.toml | mcp_servers | memctl init --codex | generate --codex |
| OpenCode | opencode.json | mcp | memctl init --opencode | generate --opencode |
| Cline | Extension UI | mcpServers | Manual | generate --cline |
| Roo Code | .roo/mcp.json | mcpServers | memctl init --roo | generate --roo |
| Continue | .continue/config.yaml | mcpServers | Manual | Manual (copy AGENTS.md) |
| Zed | Zed settings | context_servers | Manual | N/A |
| JetBrains | Settings UI | - | Manual | N/A |
| Amazon Q | .amazonq/mcp.json | mcpServers | memctl init --amazonq | generate --amazonq |
| Aider | N/A | - | - | export agents_md |
For automatic per-turn memory capture, use CLI Hooks.
Configuration
Inline token (CI / shared environments)
If you prefer not to use memctl auth, include the token directly in the config:
{
"env": {
"MEMCTL_TOKEN": "your-token",
"MEMCTL_ORG": "your-org",
"MEMCTL_PROJECT": "your-project"
}
}Verify
After configuring, run npx memctl doctor or ask your agent to call the memory tool with the capacity action.