MCP serverCurated by metahubEval warnings

@agentmemory/mcp

Name: @agentmemory/mcp
Author: rohitg00

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

pinned to #93ae9bcupdated 2 weeks ago

7/11Verified publisherCurated by MetaHubActively maintainedLicensedDocumentedRunnableClean repo

Ask your AI client: “install mcps/agentmemory-mcp”.

Requires the metahub MCP server installed in your client. Set up MCP.

mh install mcps/agentmemory-mcp

metahub onboarded this repo on the author's behalf.

If you own github.com/rohitg00/agentmemory on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.

Claim this repo

Stars

24,963

Last commit

2 weeks ago

93ae9bc

Latest release

published

2 weeks ago

#agent
#agentmemory
#agents
#ai
#claude
#claudecode
#codex
#copilot
#cursor
#genai
#harness
#hermes
#mcp
#memory
#openclaw

What this server exposes

Surfaces parsed from this server's source at publish time.

Launches: agentmemory-mcp

Evaluation report

Warnings

Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.93ae9bc· 2 weeks ago

Kind-specific

MCP: launch path
bin: agentmemory-mcp
MCP: @modelcontextprotocol/sdk in dependencieswarn
No @modelcontextprotocol/sdk dependency declared
Run `npm i @modelcontextprotocol/sdk` so consumers can audit your stack.
MCP: ESM package
"type": "module"
MCP: server surface
0 tools

Release history

releasecurrent93ae9bcwarn2 weeks ago

View on GitHub

Standalone MCP server for agentmemory.

This is a thin shim package that re-exposes the standalone MCP entrypoint from @agentmemory/agentmemory, so MCP client configs that say npx @agentmemory/mcp work out of the box without installing the full package first.

Usage

npx -y @agentmemory/mcp

Or wire it into your MCP client (Claude Desktop, OpenClaw, Cursor, Codex, etc.):

{
  "mcpServers": {
    "agentmemory": {
      "command": "npx",
      "args": ["-y", "@agentmemory/mcp"]
    }
  }
}

This package depends on @agentmemory/agentmemory and forwards to its dist/standalone.mjs entrypoint. If you already have @agentmemory/agentmemory installed, you can call the same entrypoint directly:

npx @agentmemory/agentmemory mcp

Both commands do the same thing.

Why does this package exist?

The original plan in issue #120 was to publish agentmemory-mcp as an unscoped package, but npm's name-similarity policy blocks that name because of an unrelated package called agent-memory-mcp. Publishing under the @agentmemory scope sidesteps the conflict and keeps the "dedicated standalone package" UX — npx @agentmemory/mcp is one character longer than npx agentmemory-mcp and works on the live registry.