Nowledge Mem Claude Desktop Extension

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.

Demo Screenshots

claude-mcp-ui-short.1.mp4

For more details, please refer to the Nowledge Mem Documentation.

End User Installation

See also the end user installation details at Nowledge Mem Documentation: Claude Desktop.

1. Make sure Nowledge Mem is already running on the same machine, and update Claude Desktop to the latest version.
2. Download the Nowledge Mem Claude Desktop extension and double-click the .mcpb file to install it.
3. Restart Claude Desktop once after installation.

Access Mem Anywhere (Remote Access)

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:

• macOS / Linux: ~/.nowledge-mem/config.json
• Windows: %USERPROFILE%\\.nowledge-mem\\config.json

If 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.

Troubleshooting

1. In Claude Desktop, click the + button in the chat box and open Connectors to confirm Nowledge Mem appears.
2. If it does not, open Settings → Extensions → Advanced Settings and inspect the extension status and logs there.
3. If you're using Access Anywhere, verify the shared config file above points to the correct URL and key.

Build From Source

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.js
• npm test rebuilds and runs the end-to-end MCP forwarding checks
• npm run smoke validates the built dist/index.js against a mock MCP server
• npm run pack builds, packages, and audits the final .mcpb
• npm run verify:package unpacks the finished bundle and checks the release invariants
• npm ci also installs the pinned mcpb packer locally, so npx @anthropic-ai/mcpb pack resolves to the tested version inside this repo
• the release archive excludes node_modules/, source files, and stale Python artifacts

Show Metadata Content

mcp-name: io.github.nowledge-co/server.json