Skip to content

Add mnemoverse/mcp-memory-server to MCP Servers & Tools (Infrastructure) - #45

Open
OlyaTi wants to merge 1 commit into
BlockRunAI:mainfrom
OlyaTi:add-mnemoverse
Open

OlyaTi wants to merge 1 commit into
BlockRunAI:mainfrom
OlyaTi:add-mnemoverse

Conversation

@OlyaTi

@OlyaTi OlyaTi commented Sep 21, 2026

Copy link
Copy Markdown

One entry in MCP Servers & Tools -> Infrastructure, appended after stipend, with the 💰 Monetize: line the section format uses. No memory server is listed anywhere in that section today; the memory entries in the list (Mem0, Graphiti, memU under AI Agent Frameworks, openclaw-supermemory under OpenClaw Infrastructure) sit elsewhere.

mnemoverse/mcp-memory-server is the MIT-licensed MCP server for the hosted Mnemoverse memory engine, which has a free tier. It runs two ways: the hosted endpoint at mcp.mnemoverse.com/mcp with an OAuth sign-in, or locally with npx -y @mnemoverse/mcp-memory-server and an API key. The part worth a line in this list is the feedback loop: the agent reports whether a recalled memory helped or misled, and recall is re-ranked from those outcomes, so what keeps proving useful surfaces first as a store grows past what anyone curates by hand.

Checked before opening this PR: the hosted endpoint answers 401 missing_token without a bearer token and publishes OAuth metadata at /.well-known/oauth-protected-resource, while a bogus path on the same host returns 404; the package resolves on npm as @mnemoverse/mcp-memory-server.

Checklist from the Contributing section:

  • GitHub URL
  • Star count: left off, as on stipend directly above. The repo is at 21 stars, MIT with a LICENSE file, and was pushed this week, in case the maturity bar is the question
  • Clear description
  • How to monetize

Happy to rebase if the weekly brand sync moves the file under this branch.

Disclosure: I work on Mnemoverse.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant