> ## Documentation Index
> Fetch the complete documentation index at: https://docs.memloom.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Setup

> Connect any MCP client to your memloom store

## Overview

memloom ships an MCP server over stdio. Every client comes down to the same command:

```bash theme={null}
npx -y @memloom/mcp
```

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.

<Note>
  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.
</Note>

***

## Your client

<CardGroup cols={3}>
  <Card title="Claude Code" icon="terminal" href="/mcp/clients/claude-code" />

  <Card title="Claude Desktop" icon="comment" href="/mcp/clients/claude-desktop" />

  <Card title="Cursor" icon="i-cursor" href="/mcp/clients/cursor" />

  <Card title="VS Code" icon="code" href="/mcp/clients/vs-code" />

  <Card title="Windsurf" icon="wind" href="/mcp/clients/windsurf" />

  <Card title="Cline" icon="robot" href="/mcp/clients/cline" />

  <Card title="Zed" icon="bolt" href="/mcp/clients/zed" />

  <Card title="Codex" icon="brain" href="/mcp/clients/codex" />

  <Card title="opencode" icon="laptop-code" href="/mcp/clients/opencode" />
</CardGroup>

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

***

## Where the API key goes

<Warning>
  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.
</Warning>

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](/mcp/tools).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.