Agentmemory Agents
Run agentmemory connect for your host (Claude Code, Cursor, Codex, Cline, Copilot CLI, etc.) so MCP points at persistent memory without hand-editing JSON.
Overview
agentmemory-agents is an agent skill most often used in Build (also Operate infra) that maps agentmemory connect adapters for 17 coding agents over MCP and documented hook paths.
Install
npx skills add https://github.com/rohitg00/agentmemory --skill agentmemory-agentsWhat is this skill?
- agentmemory connect <agent> registers the memory server with 17 host adapters
- Per-agent protocol notes: MCP for Cursor, Claude Code, Codex, Gemini CLI; YAML/JSON paths documented
- Codex Desktop hooks workaround flag documented for openai/codex#16430
- Autogen from src/cli/connect/index.ts—regenerate with npm run skills:gen when adapters change
- 17 connect adapters
Adoption & trust: 3 installs on skills.sh; 21.9k GitHub stars; trending (+300% hot-view momentum).
What problem does it solve?
You want persistent agent memory but do not know which config file or MCP block your IDE or CLI actually reads.
Who is it for?
Solo builders standardizing on one AgentMemory instance across Claude Code, Cursor, or Codex without per-tool guesswork.
Skip if: Projects that need only raw HTTP integration with no MCP host—skip to agentmemory-rest-api.
When should I use this skill?
You are adding or fixing AgentMemory MCP or hook configuration for a supported coding agent host.
What do I get? / Deliverables
Your chosen agent is connected via the documented adapter name and config path, with hooks called out where required.
- Correct connect command and config path for the chosen agent
- MCP/hook setup notes including Codex --with-hooks when applicable
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Build → agent-tooling is the first journey moment you wire memory into coding agents—canonical shelf even though you revisit configs in Operate. Agent-tooling covers host-specific MCP configs, hooks, and plugins—the connect adapters table is exactly that wiring matrix.
Where it fits
Run connect cursor on day one so every session shares checkpoints via MCP.
Enable Copilot CLI MCP plugin plus connect copilot-cli for full hooks coverage noted in the table.
Re-run the adapter docs after cloning dotfiles to a new machine so Cline VS Code JSON matches CLI paths.
How it compares
Connect-adapter catalog for MCP hosts, not a brainstorming or planning methodology skill.
Common Questions / FAQ
Who is agentmemory-agents for?
Indie developers using multiple AI coding CLIs or IDEs who want one memory server wired correctly per host.
When should I use agentmemory-agents?
At Build agent-tooling when onboarding a new repo; in Operate infra when rebuilding MCP configs after OS migration; anytime you switch from Gemini CLI to Antigravity per the documented sunset note.
Is agentmemory-agents safe to install?
Connect steps edit local MCP and hook configs that can expose tools to the network—review the Security Audits panel on this Prism page and keep secrets out of committed JSON.
Workflow Chain
Then invoke: agentmemory rest api
SKILL.md
READMESKILL.md - Agentmemory Agents
# agentmemory connect adapters reference Generated from `src/cli/connect/index.ts`. Do not edit the block below by hand; run `npm run skills:gen` after adding or removing an adapter. <!-- AUTOGEN:agents START - generated by scripts/skills/generate.ts, do not edit by hand --> `agentmemory connect <agent>` wires the memory server into a host agent. 17 adapters: | Agent | Name | Protocol | | --- | --- | --- | | Antigravity | `antigravity` | Using MCP via mcp_config.json. Antigravity replaces Gemini CLI (sunset 2026-06-18). | | Claude Code | `claude-code` | Using MCP. Hooks are also available, see docs/claude-code.md. | | Cline | `cline` | Using MCP via ~/.cline/mcp.json (CLI). VS Code users: add the same block via Cline Settings → MCP Servers → Edit JSON. | | Codex CLI | `codex` | Using MCP. Hooks ship via the Codex plugin; on Codex Desktop, also pass --with-hooks to install the global hooks.json workaround for openai/codex#16430. | | Continue | `continue` | Using MCP via ~/.continue/config.yaml (preferred) or config.json (legacy, only when no yaml). | | GitHub Copilot CLI | `copilot-cli` | Using MCP. Install the plugin too for full hooks/skills coverage. | | Cursor | `cursor` | Using MCP (the only protocol Cursor speaks). Memory bridge runs at :3111 underneath. | | Droid (Factory.ai) | `droid` | Using MCP via ~/.factory/mcp.json. The `/mcp` slash command inside droid lists configured servers. | | Gemini CLI | `gemini-cli` | Using MCP (the only protocol Gemini CLI speaks). Memory bridge runs at :3111 underneath. | | Hermes Agent | `hermes` | Using MCP. Hooks are also available, see docs/hermes.md. | | Kiro | `kiro` | Using MCP via ~/.kiro/settings/mcp.json (user-level). Workspace overrides live in .kiro/settings/mcp.json. | | OpenClaw | `openclaw` | Using MCP. Hooks are also available, see docs/openclaw.md. | | OpenHuman | `openhuman` | Using native hooks (REST API at :3111). MCP not required. | | pi | `pi` | Using native hooks (REST API at :3111). MCP not required. | | Qwen Code | `qwen` | Using MCP via ~/.qwen/settings.json. Qwen Code's hook system can also be wired separately, see docs. | | Warp | `warp` | Using MCP via ~/.warp/.mcp.json. Skills auto-discover from .claude/skills/ if the Claude Code plugin is also installed. | | Zed | `zed` | Using MCP via ~/.config/zed/settings.json (key: context_servers). | <!-- AUTOGEN:agents END --> --- name: agentmemory-agents description: How agentmemory wires into host coding agents via the connect command. Use when installing agentmemory into a specific agent, when asked which agents are supported, or when a connect adapter writes the wrong config path. user-invocable: false --- `agentmemory connect <agent>` merges the memory server into a host agent's config and preserves any existing servers. REST is the underlying protocol; for MCP-only hosts the adapter wires the stdio MCP bridge. ## Quick start ```bash agentmemory connect claude-code # or cursor, codex, gemini-cli, ... ``` After wiring, restart the host or run its MCP reload (for example `/mcp` in Claude Code) so it picks up the server. Then confirm the agent lists agentmemory's tools. ## Workflow 1. Detect the calling agent. If unknown, default to `claude-code`. 2. Run `agentmemory connect <name>` using a name from the table in REFERENCE.md. 3. Verify: the host should show the full tool set with a server running. Only 7 tools means the MCP shim could not reach a server (see ../_shared/TROUBLESHOOTING.md). ## Notes - The action skills (remember, recall, and the rest) are installed separately with `npx skills add rohitg00/agentmemory`. `connect` makes tools available; skills teach the agent when to use them. - Windows: use WSL2. Native Windows runs the server but `connect` is not supported there. ## See also - agentmemory-mcp-tools, agentmemory-rest-api, agentmemory-hooks. ## Reference The full adapter list with display names and protocol notes lives in REFERENCE.md, generated from `src/cli/connect/`.