Package Exports

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 (@nightwatcher314/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

@nightwatcher314/agentmemory-mcp

Standalone MCP server for agentmemory.

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

Usage

npx -y @nightwatcher314/agentmemory-mcp

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

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

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

npx @nightwatcher314/agentmemory mcp

Both commands do the same thing.

Why does this package exist?

The upstream package uses a scoped shim because npm's name-similarity policy blocks the unscoped agentmemory-mcp name. This fork follows the same shape under the @nightwatcher314 scope so MCP clients can depend on a dedicated standalone package without installing the full package first.

License

Apache-2.0