Package Exports

@agentmemory/mcp

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@agentmemory/mcp) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

@agentmemory/mcp

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.

License

Apache-2.0