Skip to main content

​
Overview

memloom ships an MCP server over stdio. Every client comes down to the same command:
It routes through the daemon rather than opening the store itself, so agents, the CLI and the viewer share one store with no lock conflicts. Run several clients at once and a memory saved from one is instantly recallable from the others.
No separate install needed, npx fetches it on first launch. If you prefer, npm install -g @memloom/mcp puts memloom-mcp on your PATH to use as the command with no args.

​
Your client

Claude Code

Claude Desktop

Cursor

VS Code

Windsurf

Cline

Zed

Codex

opencode

Any other MCP client works: point it at npx -y @memloom/mcp as a stdio server.

​
Where the API key goes

Put OPENROUTER_API_KEY in ~/.memloom/config.env, not in the client config. The daemon owns every provider call; the MCP server never talks to OpenRouter itself.
An env block in the client config only matters when the MCP process is the one that auto-starts the daemon, because real environment variables win over the file. Keeping the key in config.env gives every surface the same behaviour. Restart the daemon after changing it.

​
Verify

Ask your client:
Save a memory: the staging database runs on Postgres. What do you know about the staging database?
You should see save_memory and recall_memory tool calls, and the memory appears in memloom ui alongside everything saved from the CLI. Full tool list on Tools.