Get Mnueron memory into every AI tool you already use.

The CLI is a small Node program. It detects every AI tool on your machine and configures each one to talk to Mnueron. Open a terminal and run:

npm install -g mnueron
mnueron setup

You'll see a checklist scroll by — "Claude Desktop ✓ added", "Cursor ✓ added", "Windsurf — not detected", and so on. Anything Mnueron found gets wired automatically.

MCP plugins load at app startup, so quit and reopen both Claude Desktop and Claude Code. In a fresh Claude Desktop chat, ask:

What MCP tools do you have available?

You should see six new tools listed: memory_save, memory_recall, memory_list, memory_delete, memory_namespaces, and memory_import_chat. If you see them, the connection works.

Two settings can disagree if you're not careful: the cloud dashboard's storage mode(what your org uses) and each AI tool's MCP config file on your machine (what the tool actually calls). The dashboard setting does NOT reach into your laptop and reconfigure Claude. So after Save, run this check.

Authoritative check (one command)

mnueron stats
# First line tells you the mode:
#   mode: local SQLite                        ← local
#   mode: hosted https://api.mnueron.com      ← cloud

Where each tool's MCP config file lives

The mnueron CLI prints the exact paths when you run mnueron setup. The common Windows paths (Microsoft Store install of Claude Desktop) are below — macOS / Linux fall back to the home-directory equivalents.

Claude Desktop  C:\Users\<you>\AppData\Local\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\claude_desktop_config.json
Claude Code     C:\Users\<you>\.claude\settings.json
Cursor          C:\Users\<you>\.cursor\mcp.json
Codex           C:\Users\<you>\.codex\config.toml
Cline (VSCode)  C:\Users\<you>\AppData\Roaming\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json
Continue        C:\Users\<you>\.continue\config.json

# macOS swaps the path roots:
~/Library/Application Support/Claude/claude_desktop_config.json
~/.claude/settings.json
~/.cursor/mcp.json
~/.codex/config.toml
~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
~/.continue/config.json

How to read which mode a tool is in

Open the file. Look at the mnueron server entry. The discriminator is the env block:

// HOSTED mode — talks to the cloud
"mnueron": {
  "command": "mnueron",
  "args": ["--mcp-stdio"],
  "env": {
    "MNUERON_API_URL":   "https://api.mnueron.com",
    "MNUERON_API_TOKEN": "mnu_..."
  }
}

// LOCAL mode — talks to ~/.mnueron/memories.db
"mnueron": {
  "command": "mnueron",
  "args": ["--mcp-stdio"]
  // no env, or env without MNUERON_API_URL / MNUERON_API_TOKEN
}

How to flip a tool

# All detected tools → local
mnueron setup

# All detected tools → hosted (cloud)
mnueron setup --hosted https://api.mnueron.com --token mnu_xxx

# A specific tool only
mnueron setup --only claude-desktop
mnueron setup --only codex
mnueron setup --only cursor

There are two dashboards. Local dashboard runs on your machine and shows the memories saved in your local SQLite. Hosted dashboard runs at app.mnueron.com and shows memories synced to the cloud (you'll set that up in step 4).

mnueron dashboard
# opens http://localhost:3122 in your browser

You'll land on the dashboard overview. Empty right now — you haven't saved anything yet. The sidebar has Memories, Chat, Mnueron Meet, Analytics, Entities, and a Settings link. Anything you save from Claude Desktop will show up here in real time.

Local-only is great for a single machine. The moment you want your laptop and desktop to share memories — or share with a teammate — you need a hosted account. The Free tier covers personal sync.

1. Visit /signup and create an account. You can sign up with Google or email + password.
2. Once you're in, open /account-settings/tokens and click Create token. Copy themnu_… value — you only see it once.
3. Back in your terminal, point the CLI at the cloud:

   mnueron setup --hosted https://api.mnueron.com --token mnu_xxx

4. Restart Claude Desktop. New memories now sync to the cloud AND your other devices.

Once you have a hosted account, you have three storage choices. You pick this in /account-settings/storage — the three cards live there.

Mnueron uses an LLM for summaries, decision extraction, and the Project classifier. Free and Basic plans use our shared key with reasonable rate limits. Pro and above can paste their own OpenAI or Anthropic key so the bill goes straight to them and there's no shared-pool ceiling.

1. Open /account-settings/keys.
2. Click Edit on the OpenAI or Anthropic card. Paste your sk-… key.
3. Click Test. A green tick means the key works and the upstream vendor accepts it.
4. Click Save. The key is encrypted server-side and used only when fulfilling your org's requests.

If you also want meeting capture (Granola / Fathom / Zoom / Teams), the Meet-specific quickstart at /docs/meet/getting-started takes you through connecting a meeting source, running the first sync, creating a project, and confirming auto-assignments. Five steps, takes about ten minutes.

The fastest way to feel why this matters. Open Claude Desktop (or Claude Code) and run this in one chat:

Save this as a memory for my project:
"Always use Tailwind v4 utility classes, never inline styles.
 Prefer rounded-2xl for cards and rounded-md for buttons."

Claude calls memory_save behind the scenes and confirms. Now close that chat and open a brand-new conversation (the equivalent of a fresh session). Type:

What's my CSS preference for this project?

Claude calls memory_recall, finds the convention you taught it five minutes ago, and reads it back. That's persistent memory across sessions, in two API calls, without you wiring anything up per-provider.