Loomem — Quick start

Loomem gives your LLM agents memory that persists across conversations. It can store facts, decisions, and preferences you choose to share.

Local setup

1. Install and start the server

Install the prebuilt binaries (no sudo; they land in ~/.loomem) and put ~/.loomem/bin on your PATH — full steps in the Installation guide. Before starting, download the local embedding model as described there. The default configuration also requires an LLM key in OPENAI_API_KEY; alternatively, set LOOMEM_ALLOW_KEYLESS=1 for reduced functionality. Then start it:

cd ~/.loomem && loomem-server
# listens on http://localhost:3030 — auth is off by default for local use

2. Connect Claude Code

claude mcp add --transport http loomem http://localhost:3030/mcp

2b. Or connect the Claude desktop app (and Cowork)

The Claude desktop app connects to local servers over stdio, not HTTP, and its custom-connector box only accepts an https:// URL — so http://localhost won't paste in. Bridge it in claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json), then fully restart Claude. Native bridge, no Node (Loomem ≥ v0.2.1 — use the absolute path to loomem-cli):

{
  "mcpServers": {
    "loomem": {
      "command": "/Users/you/.loomem/bin/loomem-cli",
      "args": ["mcp-stdio", "--url", "http://127.0.0.1:3030"]
    }
  }
}

Or, with Node, the universal mcp-remote fallback:

{
  "mcpServers": {
    "loomem": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "http://127.0.0.1:3030/mcp", "--allow-http"]
    }
  }
}

3. Try it

Without an LLM key, memory_ingest returns an error and extracts no facts. It may still store the source text before extraction. Configure an LLM key to try extraction in the following example.

In Claude, say:

"Remember that I prefer dark mode in all my tools."

Then start a new conversation and ask:

"What do you know about my preferences?"

Claude can retrieve the answer from Loomem.

Connecting claude.ai or ChatGPT (remote)

These connect to remote MCP servers over HTTPS, so this is a separate, longer step: expose your instance behind TLS, set SERVER_ORIGIN, then add the connector pointing at https://your-domain/mcp (OAuth dynamic client registration works out of the box). Full walkthrough — TLS, reverse proxy, auth — in the Deployment guide.

How it works

Claude can store facts you share in memory
Claude can search memory before answering questions about you
Memory persists across conversations and sessions, and is available to devices that can access the server

Privacy

Your memory is stored on your own server. Depending on your configuration, LLM-backed features can use an external provider. See the Security overview.

User Guide — day-to-day usage
MCP Tools Reference — what Claude can do with memory