Skip to content
Claude Code

Shared memory for your team’s Claude Code

MemScope is a shared memory your team’s AI coding agents read and write over a remote MCP server. Each person’s Claude Code recalls what teammates’ agents learned, limited to what that person is permitted to see.

The problem

One developer’s agent works out why a build step fails, which service owns a table, or why a convention exists. The next developer’s agent, on the same codebase, relearns it from scratch.

A file in the repository is the usual fix, and it works for what everyone may read. But a file in git is all-or-nothing: whoever can read the repository reads the whole file. Anything meant for one team or one project has nowhere to go.

How MemScope fits

Claude Code connects to MemScope as an MCP server and saves explicit memories: facts, decisions, conventions and owners. When a teammate’s Claude Code asks, MemScope returns the memories that person may read. AI suggests labels such as sensitivity and topic, but a deterministic policy decides access. Organization admins get no read bypass, MemScope staff see XXX unless the customer grants time-limited, audited support access, and every change is audited.

How access is decided and audited

Install in Claude Code

Add it with the claude CLI.

Run in a terminal

claude mcp add --transport http --scope user memscope https://mcp.memscope.ai/mcp

In Claude Code run /mcp, pick memscope and choose Authenticate. You sign in using the browser.

New to MemScope? Create an account at https://memscope.ai/signup, choose your organization and approve. The same steps, for every client, are on the MCP setup page.

What CLAUDE.md and auto memory do

CLAUDE.md files are instructions you write; Claude Code reads them at the start of every session, and can read a repository’s AGENTS.md in place of CLAUDE.md. A project file is shared with everyone who has the repository, through git, and versioned with the code. Auto memory is separate: notes Claude writes itself, kept on your machine and not shared across machines. Those docs describe no per-person access inside a shared file.

Source: Claude Code docs: How Claude remembers your project, checked November 2026.

Compare: MemScope vs CLAUDE.md and AGENTS.md files · All comparisons

Example: same question, two answers

An illustration. Teammates’ agents have saved two memories: one shared with the whole organization, one limited to the Payments team.

  • Shared with everyone

    Webhook handlers must be idempotent, because the provider redelivers events.

  • Payments team only

    The provider contract renews next quarter; do not commit to a new integration before then.

Both teammates ask their Claude Code: “What should I know before changing the payments webhook?”

  • A teammate on Payments

    Recalls both memories.

  • A teammate on another team

    Recalls only the idempotency convention. The contract memory is not returned to them.

Who it is for

Teams whose developers use Claude Code, Cursor, ChatGPT or other MCP clients, and who want agents to share what they learn without every memory being readable by everyone.

Price

$15 per connected user per month after a 60-day trial with 3 connected users. You pay only for people who connect an AI client.