Bridges Claude Desktop to Nowledge Mem, a local knowledge base that runs on your machine or remote server. Exposes tools to search your stored memories, add new context during conversations, update existing knowledge, and trigger inline graph views. Ships as a one-click MCPB package that uses Claude Desktop's bundled Node runtime, so there's no separate Python or Node setup. Connects to localhost by default but reads a shared config file for remote instances when you enable Access Anywhere. Reach for this when you want Claude to remember facts, entities, and context across sessions by querying and writing to your personal Mem database in real time.
One-click Claude Desktop integration for Nowledge Mem on macOS and Windows, with no separate Python or Node installation required. After installation, Claude can search your memories, save important context, update existing knowledge, and open Mem's inline graph views during any conversation.
https://github.com/user-attachments/assets/a99a1daa-e73c-429e-a17b-0183b2f9671a
For more details, please refer to the Nowledge Mem Documentation.
See also the end user installation details at Nowledge Mem Documentation: Claude Desktop.
.mcpb file to install it.By default the extension connects to your local Mem at 127.0.0.1:14242.
For remote access, the extension reads the same shared config file as the nmem CLI:
~/.nowledge-mem/config.json%USERPROFILE%\\.nowledge-mem\\config.jsonIf you start Access Anywhere from Nowledge Mem Desktop on the same machine, this file is usually written for you automatically.
If you need to point Claude Desktop at a remote Mem manually, create the file with:
{
"apiUrl": "https://mem.example.com",
"apiKey": "nmem_your_key"
}
Use your server root URL in apiUrl. If you already have an older config ending in /remote-api or /mcp, the extension accepts that too.
Restart Claude Desktop after changing the file.
+ button in the chat box and open Connectors to confirm Nowledge Mem appears.The extension uses the Node runtime that ships with Claude Desktop, so end users do not need to install Python or Node.
npm ci
npm test
npm run smoke
npm run pack
For maintainers:
npm run build bundles the bridge into dist/index.jsnpm test rebuilds and runs the end-to-end MCP forwarding checksnpm run smoke validates the built dist/index.js against a mock MCP servernpm run pack builds, packages, and audits the final .mcpbnpm run verify:package unpacks the finished bundle and checks the release invariantsnpm ci also installs the pinned mcpb packer locally, so npx @anthropic-ai/mcpb pack resolves to the tested version inside this reponode_modules/, source files, and stale Python artifactsmcp-name: io.github.nowledge-co/server.json
csoai-org/pdf-document-mcp
xt765/mcp-document-converter
io.github.xjtlumedia/markdown-formatter
io.github.ai-aviate/better-notion
suekou/mcp-notion-server
meterlong/mcp-doc