LedgerMem MCP Server
OfficialClick on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@LedgerMem MCP ServerRemember that my name is Alice and I work at Acme Corp."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
getmnemo-mcp
Model Context Protocol server for Mnemo Memory — exposes long-term memory tools to any MCP client (Claude Desktop, Cursor, Windsurf, VS Code, Zed).
Tools
Tool | What it does |
| Hybrid 7-strategy retrieval over the workspace memory store. |
| Store an atomic fact with optional metadata. |
| Fetch one memory by ID within the configured container. |
| Patch an existing memory's content or metadata. |
| Soft-delete a memory by ID so it leaves retrieval. |
| Paginate through memories (cursor-based). |
Remote HTTP calls are scoped by the user's Mnemo OAuth grant. The user signs in, chooses a workspace and memory container, and the server derives that scope from the access token. The model cannot set or change it.
Related MCP server: mcp-memory
Install
Local stdio clients
npx -y getmnemo-mcpOr wire it into the client config directly. Example for Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"getmnemo": {
"command": "npx",
"args": ["-y", "getmnemo-mcp"],
"env": {
"GETMNEMO_API_KEY": "prfly_live_...",
"GETMNEMO_WORKSPACE_ID": "ws_...",
"GETMNEMO_CONTAINER_TAG": "user:jane"
}
}
}
}Get an API key at https://app.mnemohq.com/settings/api-keys.
Hosted remote MCP clients
For clients that support remote MCP and OAuth 2.1, use:
https://mcp.mnemohq.com/mcpThe client should discover OAuth metadata, open Mnemo sign-in, and return to the client after the user selects a workspace and container. No API key, workspace header, or container configuration is required for this path.
Develop
npm install
cp .env.example .env # fill in API-key/container values for stdio
npm run dev # stdio
npm run dev:http # Streamable HTTP on :8787
npm run build # bundle to dist/Architecture
stdio (
src/cli.ts): one process per MCP client connection, env-configured.Streamable HTTP (
src/http.ts): hosted transport for public OAuth sessions, with private API-key compatibility for trusted deployments.Both transports share
src/server.ts(tool registration + dispatch) andsrc/api-client.ts(typed REST wrapper).
The public hosted transport uses Mnemo's OAuth 2.1 authorization server and resource-bound tokens. Header-selected containers remain disabled by default; they are only a private compatibility path for a trusted gateway.
The server deliberately does NOT depend on getmnemo (the JS SDK) so it can ship independently.
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityDmaintenanceProvides persistent memory for AI assistants via MCP, enabling them to store and recall facts, preferences, and tasks across conversations using either local file storage or a cloud backend with semantic search.514MIT
- AlicenseAqualityDmaintenanceProvides persistent memory with semantic search for MCP-based AI agents, enabling them to store and recall information across sessions using vector embeddings.41MIT
- AlicenseNot gradedqualityCmaintenanceEnables persistent memory for AI agents, combining episodic and semantic memory with LLM reasoning, accessible via MCP.2MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to have a living memory with atomic knowledge storage, multi-factor recall, organic decay, automatic learning, and graph traversal via MCP.1MIT
Related MCP Connectors
Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.
Your memory, everywhere AI goes. Build knowledge once, access it via MCP anywhere.
Cross-vendor AI memory over MCP. One semantic store, readable and writeable from every MCP client.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ledgermem/getmnemo-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server