Dev Tools & GitMCP RegistryociB · 66

codeagent-memory MCP server

Name: codeagent-memory
Author: HanochZhu

io.github.HanochZhu · Updated 8d ago

Local code graph and solution memory for coding agents via CLI and MCP.

At a glance

codeagent-memory is an MCP server in the Dev Tools & Git category. It runs locally over stdio via `docker run -i --rm ghcr.io/hanochzhu/codeagent-memory:0.1.5`, and declares no required credentials. It scores B (66/100) on the MCP Skills Hub health score as of Oct 27, 2026.

Source 1

One-click install

VS Code VS Code Insiders Cursor

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install codeagent-memory in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install codeagent-memory in Claude CodeAnthropic's agentic CLI

Add the server

bash

claude mcp add codeagent-memory -- docker run -i --rm ghcr.io/hanochzhu/codeagent-memory:0.1.5

2
Verify it's connected
bash
```
claude mcp list
```
Sharing it with your team?
Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).
Use it in a session
Ask Claude to use the tools this server exposes. It discovers them automatically.

How to install codeagent-memory in Claude DesktopDesktop app (MCP config)

Open your MCP config
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this server

json

{
  "mcpServers": {
    "codeagent-memory": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/hanochzhu/codeagent-memory:0.1.5"
      ]
    }
  }
}

Restart Claude Desktop
The tools appear under the 🔌 menu once the app reloads.

How to install codeagent-memory in CursorAI-first code editor

Create / edit .cursor/mcp.json in your project

json

{
  "mcpServers": {
    "codeagent-memory": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/hanochzhu/codeagent-memory:0.1.5"
      ]
    }
  }
}

Enable it
Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.

How to install codeagent-memory in Codex CLIOpenAI coding agent

Add to ~/.codex/config.toml

toml

[mcp_servers.codeagent-memory]
command = "docker"
args = ["run", "-i", "--rm", "ghcr.io/hanochzhu/codeagent-memory:0.1.5"]

Run Codex
Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.

How to install codeagent-memory in WindsurfCodeium's agentic IDE

Edit ~/.codeium/windsurf/mcp_config.json

json

{
  "mcpServers": {
    "codeagent-memory": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/hanochzhu/codeagent-memory:0.1.5"
      ]
    }
  }
}

Reload
Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.

How to install codeagent-memory in ClineVS Code autonomous agent

Open Cline → MCP Servers → Configure
Adds to cline_mcp_settings.json.

Add the server

json

{
  "mcpServers": {
    "codeagent-memory": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/hanochzhu/codeagent-memory:0.1.5"
      ]
    }
  }
}

How to install codeagent-memory in VS CodeCopilot / MCP support

Create .vscode/mcp.json

json

{
  "servers": {
    "codeagent-memory": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/hanochzhu/codeagent-memory:0.1.5"
      ]
    }
  }
}

Start it
VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.

What tools does codeagent-memory expose?

This server runs as a local package. We only query remote servers for their tool list — asking this one would mean executing it, so its tools are listed in the documentation below.

What the code can do

Source analysis currently covers npm packages only. This server ships as a container image, whose contents are not readable the same way.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

Runs code on your machine — Executes as a Docker container with whatever mounts and env you pass it.
Downloads at launch — The package is fetched from its registry each run unless you pin a version.

Last commit 4 days ago — Actively maintained.
Repository created 1 month ago — Very new project with little track record yet.
1 GitHub stars — Very little community usage so far.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

B · 66

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

Maintenance30%100%
Last commit 4 days ago.
Adoption20%9%
1 stars.
Transparency20%75%
3/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✗ discoverable tool list.
Provenance15%75%
Links to its own repository; package linkage unverified.
Packaging15%50%
No pinned version — installs resolve to whatever is latest at launch.

Documentation

Full README

cam

English · 中文 · 日本語 · 한국어 · العربية · 🌐 Website

A local multi-turn conversational memory system purpose-built for coding agents

Code graph + memory · surgical reads · 100% local · MCP + CLI

Kernel written in Rust

Contents

Why cam?
Get Started
Key Features
How It Works
Agent Workflow
CLI Reference
Memory Rules
Configuration
Benchmarks
Supported Agents
Supported Languages
Supported Platforms
License

Guides: Interactive Showcase (Website) · Main Agent vs Subagent · MCP Configs by IDE · 中文说明

Why cam?

When an AI coding agent explores a repository, it usually rediscovers structure the slow way — running grep, glob, and full-file Read one file at a time — and forgets everything in the next session.

`cam` gives the agent two local retrieval planes in a single binary:

| Plane | What it stores | How the agent uses it | | --- | --- | --- | | Code Graph | Tree-sitter symbols (functions, types, methods) as a virtual filesystem + 1-hop callers/callees | ls, find, read src/file.rs/symbol, ref symbol --dir in\|out — surgical symbol reads instead of whole-file dumps | | Memory Tree | Project facts, architecture decisions, debugging write-ups, and user habits | recall (Vector + BM25 fused with RRF) and add (with branching --parent and revision --supersedes) |

One binary, two interfaces: The main agent calls cam over MCP (cam mcp); subagents (which rarely inherit MCP tools) call the exact same CLI (cam --json …). Both share .cam/cam.db on disk, 100% local, zero API cost.

Excerpt — the full document is on GitHub.

Alternatives to codeagent-memory

Maintain codeagent-memory? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown

[![codeagent-memory on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/io-github-hanochzhu-codeagent-memory)](https://mcp-skills-hub.vercel.app/mcps/io-github-hanochzhu-codeagent-memory)

Catalog data refreshed Oct 27, 2026. Something wrong? Report it.