Source: Source pull request number: 121 in rohitg00/agentmemory (URL omitted to avoid GitHub cross-reference)
Title: fix: correct standalone MCP invocation to use --package flag
Author: JasonLandbridge
State: closed
Draft: no
Merged: yes
Head: JasonLandbridge/agentmemory:fix/standalone-mcp-npx-command @ 2665981
Base: main @ 2a5cb12
Labels: (none)
Changed files: 0
Commits: 0
Created: 2026-04-13T09:43:30Z
Updated: 2026-04-13T12:06:41Z
Closed: 2026-04-13T11:23:36Z
Merged at: 2026-04-13T11:23:35Z
Original PR body:
Problem
npx agentmemory-mcp fails with a 404 from the npm registry because there is no standalone npm package named agentmemory-mcp. The agentmemory-mcp binary is registered inside the @agentmemory/agentmemory package (dist/standalone.mjs).
Running npx agentmemory-mcp as documented causes:
npm error 404 Not Found - GET https://registry.npmjs.org/agentmemory-mcp
Fix
The correct invocation is:
npx --package @<!-- -->agentmemory/agentmemory agentmemory-mcp
And in MCP config JSON:
{
"mcpServers": {
"agentmemory": {
"command": "npx",
"args": ["--package", "@<!-- -->agentmemory/agentmemory", "agentmemory-mcp"]
}
}
}
Changes
Updated all documentation examples to use the correct --package flag:
README.md — standalone MCP section, quick-start table, and agent-specific prompts (OpenClaw, Hermes, Cursor, OpenCode, Gemini CLI, Codex CLI, Claude Desktop)
integrations/openclaw/README.md
integrations/hermes/README.md
Verification
Confirmed working locally:
$ echo '{"jsonrpc":"2.0","id":1,"method":"initialize",...}' | npx --package @<!-- -->agentmemory/agentmemory agentmemory-mcp
[agentmemory-mcp] Standalone MCP server v0.8.1 starting...
{"jsonrpc":"2.0","id":1,"result":{"protocolVersion":"2024-11-05",...,"serverInfo":{"name":"agentmemory","version":"0.8.1"}}}
closes #120
Summary by CodeRabbit
- Documentation
- Refreshed MCP server configuration examples with updated OpenCode schema and setup instructions.
- Added dedicated section documenting OpenCode agent configuration options.
Local branch:
Fork PR:
Fork decision:
Verification:
Notes:
Source: Source pull request number: 121 in rohitg00/agentmemory (URL omitted to avoid GitHub cross-reference)
Title: fix: correct standalone MCP invocation to use --package flag
Author: JasonLandbridge
State: closed
Draft: no
Merged: yes
Head: JasonLandbridge/agentmemory:fix/standalone-mcp-npx-command @ 2665981
Base: main @ 2a5cb12
Labels: (none)
Changed files: 0
Commits: 0
Created: 2026-04-13T09:43:30Z
Updated: 2026-04-13T12:06:41Z
Closed: 2026-04-13T11:23:36Z
Merged at: 2026-04-13T11:23:35Z
Original PR body:
Problem
npx agentmemory-mcpfails with a 404 from the npm registry because there is no standalone npm package namedagentmemory-mcp. Theagentmemory-mcpbinary is registered inside the@agentmemory/agentmemorypackage (dist/standalone.mjs).Running
npx agentmemory-mcpas documented causes:Fix
The correct invocation is:
And in MCP config JSON:
{ "mcpServers": { "agentmemory": { "command": "npx", "args": ["--package", "@<!-- -->agentmemory/agentmemory", "agentmemory-mcp"] } } }Changes
Updated all documentation examples to use the correct
--packageflag:README.md— standalone MCP section, quick-start table, and agent-specific prompts (OpenClaw, Hermes, Cursor, OpenCode, Gemini CLI, Codex CLI, Claude Desktop)integrations/openclaw/README.mdintegrations/hermes/README.mdVerification
Confirmed working locally:
closes #120
Summary by CodeRabbit
Local branch:
Fork PR:
Fork decision:
Verification:
Notes: