agentmemory-agents
rohitg00/agentmemory
Wire agentmemory memory server into your coding agent via the connect command.
What is agentmemory-agents?
Integrates agentmemory's memory server into host coding agents like Claude Code, Cursor, and others. Use this skill when installing agentmemory into a specific agent, determining which agents are supported, or troubleshooting config path issues.
- Merges memory server into host agent config while preserving existing servers
- Supports multiple agents: claude-code, cursor, codex, gemini-cli, and others
- Uses REST protocol with stdio MCP bridge adapter for MCP-only hosts
- Detects calling agent automatically; defaults to claude-code if unknown
- Preserves full tool set availability after wiring
How to install agentmemory-agents
npx skills add https://github.com/rohitg00/agentmemory --skill agentmemory-agents- agentmemory installed via npx skills add rohitg00/agentmemory
- Host coding agent installed (Claude Code, Cursor, Codex, Gemini CLI, etc.)
- WSL2 on Windows (native Windows not supported for connect command)
How to use agentmemory-agents
- 1.Run agentmemory connect <agent-name> with your agent name (e.g., claude-code, cursor)
- 2.Restart your host agent or run its MCP reload command (e.g., /mcp in Claude Code)
- 3.Verify the agent lists agentmemory's full tool set in its interface
- 4.If only 7 tools appear, check troubleshooting guide—MCP shim cannot reach server
Use cases
- Install agentmemory into Claude Code and enable memory tools immediately
- Connect agentmemory to Cursor for persistent agent memory across sessions
- Wire memory server into Gemini CLI or other supported coding agents
- Troubleshoot missing tools when MCP shim cannot reach the server
- Verify successful integration by checking tool availability in host agent
- Developers using Claude Code, Cursor, or other supported coding agents
- Teams needing persistent memory across agent sessions
- Users troubleshooting agentmemory integration issues
agentmemory-agents FAQ
The full adapter list with display names lives in REFERENCE.md, generated from src/cli/connect/. Supported agents include claude-code, cursor, codex, gemini-cli, and others.
The connect command wires the memory server into your agent's config and makes tools available. The action skills (remember, recall, etc.) are installed separately and teach the agent when to use those tools.
This means the MCP shim could not reach the memory server. Check the troubleshooting guide in _shared/TROUBLESHOOTING.md for resolution steps.
No. The server runs on native Windows but the connect command is not supported. Use WSL2 instead.
No. After running connect, just restart your host agent or reload MCP (e.g., /mcp in Claude Code) to pick up the server.
Full instructions (SKILL.md)
Source of truth, from rohitg00/agentmemory.
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
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
- Detect the calling agent. If unknown, default to
claude-code. - Run
agentmemory connect <name>using a name from the table in REFERENCE.md. - 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.connectmakes tools available; skills teach the agent when to use them. - Windows: use WSL2. Native Windows runs the server but
connectis 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/.
Related skills
More from rohitg00/agentmemory and the wider catalog.
agentmemory-architecture
Understand agentmemory's architecture: iii engine primitives, hybrid retrieval, storage lifecycle, and ports.
agentmemory-config
Configure agentmemory environment variables, ports, API keys, and feature flags.
agentmemory-hooks
Automatic memory capture hooks across agent sessions—zero-LLM observation recording.
agentmemory-mcp-tools
Index of agentmemory MCP tools: which tool to call, exact parameters, and when to use each.
agentmemory-rest-api
HTTP REST API for agentmemory memory server—save and recall agent knowledge over HTTP.
commit-context
Trace code back to the agent session that created it—answer 'why is this here' and 'what was the agent doing'.