CONNECTORS

Claude Code

One command wires Memuron into Claude Code over remote MCP. Sign in through the browser once and every session after that can recall what the last one learned — no API key in your shell history.

Run this

claude mcp add --transport http --scope user memuron https://api.memuron.com/mcp

claude — ~/code/acme

❯

A real session, replayed — add the server, approve in the browser tab it opens, then ask.

Set up Claude Code in 4 steps

No API keys to paste, no glue code — sign in once and your agent keeps the memory.

Remote MCP4 steps · about 40 seconds

Run one claude mcp add command
Open /mcp and press enter to authenticate
Approve Memuron in the browser tab it opens
Ask a question that needs history

Add the MCP server

Claude Code speaks streamable HTTP MCP natively, so there is no wrapper process and nothing to install. Register the endpoint once at user scope and it is available in every repository you open.

--scope defaults to local, which registers the server for the current directory only. Use --scope user to get it everywhere, or --scope project to commit it in .mcp.json so teammates inherit it.

local

Written to ~/.claude.json keyed to the project path. Yours, in that one directory.

user

Written to ~/.claude.json globally. Yours, in every repository you open.

project

Written to .mcp.json in the repo. Anyone who checks it out and approves it.

Approve it once

Selecting the server in /mcp opens a browser tab at the Memuron console — the panel you see land over the session above. Sign in with the org you want the agent to read and write, and approve. Memuron issues a short-lived OAuth token bound to that organization; no key is ever pasted into a prompt.

Afterwards /mcp reports connected and the Memuron tools show up in the tool picker. Tokens refresh silently; you only see that screen again if you revoke access or switch organizations.

What Claude Code can do once connected

Every action is a typed MCP tool. Destructive calls carry a confirmation flag, so the agent cannot drop a memory on a hunch.

memuron_list_spaces

Discover which spaces exist before guessing a path.

memuron_query

Pipe semantic search, traversal, and regex over the graph.

memuron_get

Fetch one memory and its links once you have an ID.

memuron_ingest

Queue content for the Guardian to create, update, or link.

memuron_updateconfirm

Patch content or scope on a memory you already found.

memuron_deleteconfirm

Remove a memory — never without an explicit confirmation.

memuron_document_source

Resolve any chunk back to the file and page it came from.

memuron_job_status

Poll an async ingest until the Guardian commits or rejects it.

When something looks wrong

Symptom	Fix
`/mcp` does not list memuron	You added it at `local` scope from a different directory. Re-run with `--scope user`.
Stuck on “needs authentication”	The browser tab was closed before approval. Select the server in `/mcp` and authenticate again.
Tools appear but every call is empty	You approved a different organization. Check the active org in the console, then reconnect.

For folder sync, CI ingest, and shell queries, see the Memuron CLI.