$ timeahead.in
/ servers/npm/@agentmemory/mcp
npm

@agentmemory/mcp

Standalone MCP server for agentmemory — thin shim that re-exposes @agentmemory/agentmemory's MCP entrypoint

22k stars26k/wkupdated 0d agogithub ↗
64fair
▣ Overview

What it does

Agentmemory provides persistent memory for AI coding agents—Claude Code, Cursor, GitHub Copilot CLI, and other MCP-compatible clients. Instead of starting from scratch each session, agents store and retrieve project context, code patterns, architecture decisions, debugging insights, and learned solutions. It builds on the iii knowledge engine with hybrid search (vector + keyword), confidence scoring, knowledge graphs, and automatic lifecycle management. The MCP server re-exposes the core agentmemory library as a standard MCP entrypoint, letting any agent tap into a unified memory layer across projects and sessions.

Who it's for

Engineers who work repeatedly with the same codebase or project domain using AI agents. This includes full-stack developers relying on Claude Code for iterative feature work, teams running agents across monorepos or microservices, and anyone frustrated when agents re-ask the same questions or re-solve problems they've already encountered.

Common use cases

  • Store and recall project structure, conventions, and build patterns so agents work correctly in unfamiliar codebases on the first try
  • Record failed approaches and lessons learned so agents can avoid repeating mistakes or dead-ends
  • Maintain debugging and refactoring recipes agents discover so similar issues can be fixed faster
  • Track API contracts, performance gotchas, and business logic rules as agents encounter them
  • Share context across multiple agent instances or sessions without pasting context windows

Setup pitfalls

  • Four secrets detected in package—rotate and externalize any credentials before production use; store API keys via environment variables or a secure config file, never in version control
  • Requires filesystem write access to persist memory state—ensure the MCP process has write permissions to its configured data directory and enough disk space for long-running agents
  • Makes network calls (likely to a backend or embedding service)—configure network timeouts and proxy settings if behind a corporate firewall
  • Marked high-risk on the registry—monitor logs for sensitive data leakage and review stored memory periodically to confirm no unintended secrets are being indexed
4 credentials detected in repository history via Gitleaks
▣ Score BreakdownMCPScore = Σ(raw × weight)
DimensionRawWeighted
Security
35%
20
7.0
Freshness
25%
100
25.0
Adoption
20%
93
18.6
Quality
10%
80
8.0
Trust
10%
50
5.0
Total
63.6
⚿ Capabilities & Risk Explainer
fs readfs writenetworkexecsecrets
◆ Risk level: high
fs read + fs write + network + exec + secrets active — can execute code, access credentials, and make external network calls.
⚙ Install config
Claude Desktop · Cursor · Windsurf · VS Code (Copilot) · Claude Code
add to your MCP client config:
{
  "mcpServers": {
    "agentmemorymcp": {
      "command": "npx",
      "args": [
        "-y",
        "@agentmemory/mcp"
      ]
    }
  }
}
📈 Score historylast 22 snapshots
5/20/20266/10/2026 · 22 snapshots
⚙ Maintenance health
63/ 100 · is this project alive?
contributors (1y)39
top contributor share84%
releases (1y)49
last release4d ago
ci✓ passing
⛁ Raw data
weekly downloads26k
github stars22k
forks2k
open issues286
license✓ present
readme length75786 chars
last publish0d ago
last commit0d ago
last updated1d ago
install verified✗ fail · 24d ago
owner of this server? claim your listing to get a verified badgeclaim →
🔔 Score drop alerts
get notified by email when this server's score drops 5+ points