agentmemory-agents
rohitg00/agentmemory
Wire agentmemory memory server into Claude Code, Cursor, Codex, or other coding agents.
What is agentmemory-agents?
Agentmemory's connect command merges a persistent memory server into your host coding agent's configuration, preserving existing servers and using REST or MCP protocols as needed. Use this when installing agentmemory into a specific agent or troubleshooting connection issues.
- Detects your host agent (Claude Code, Cursor, Codex, Gemini CLI, etc.) and wires the memory server into its config
- Preserves any existing servers during integration
- Bridges stdio MCP protocol for MCP-only hosts using a REST adapter
- Requires agent restart or MCP reload to activate the memory tools
- Validates successful connection by checking tool availability in the host
How to install agentmemory-agents
npx skills add https://github.com/rohitg00/agentmemory --skill agentmemory-agents- agentmemory installed via npx skills add rohitg00/agentmemory
- A supported host agent: Claude Code, Cursor, Codex, Gemini CLI, or similar
- WSL2 on Windows (native Windows not supported for connect)
How to use agentmemory-agents
- 1.Run agentmemory connect <agent-name> with your host agent name (e.g., claude-code, cursor)
- 2.Restart your host agent or trigger MCP reload (e.g., /mcp in Claude Code)
- 3.Confirm the agent displays the full agentmemory tool set (7+ tools)
- 4.If only 7 tools appear, check TROUBLESHOOTING.md for server connectivity issues
Use cases
- Installing agentmemory into Claude Code or Cursor after initial setup
- Switching agentmemory between different coding agents on the same machine
- Troubleshooting when the connect adapter writes to an incorrect config path
- Verifying that all 7+ agentmemory tools are available in your host agent
- Re-enabling agentmemory after updating or reinstalling your coding agent
- Developers using Claude Code, Cursor, Codex, or Gemini CLI
- Teams managing agentmemory across multiple coding agents
- Users on WSL2 or Linux/macOS (Windows native not supported)
agentmemory-agents FAQ
Claude Code, Cursor, Codex, Gemini CLI, and others listed in REFERENCE.md. If your agent is unknown, the default is claude-code.
No. The connect command is only needed to wire tools into a host agent. For REST-only use, skip this skill.
Connect wires the server into your agent's config; the action skills (remember, recall, etc.) teach the agent when to use the tools.
The MCP shim cannot reach the memory server. Check TROUBLESHOOTING.md and ensure the server is running and accessible.
Use WSL2. Native Windows can run the server but the connect command is not supported there.
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 for memory capture, retrieval, and knowledge management.
agentmemory-rest-api
HTTP REST API for agentmemory memory server; use when MCP is unavailable or integration requires HTTP.
commit-context
Trace code back to the agent session that created it—answer 'why is this here' and 'what was the agent doing'.