Montycat MCP — Shared AI Memory

One shared, persistent memory across AI agents and systems, with semantic recall and live updates.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "montycat-mcp-shared-ai-memory": {
      "command": "npx",
      "args": [
        "-y",
        "montycat-mcp-shared-ai-memory"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

Montycat MCP - Shared Memory for AI Agents

A self-hosted MCP server that gives AI agents persistent, searchable memory. Claude, Codex, Cursor, and any Model Context Protocol client write to one memory and read each other's.

Memory that survives the chat. Decisions, preferences, and project context carry into the next session.
One memory, many agents. Every MCP client you use works from the same facts.
Recall by meaning, keyword, or both. Vector search finds a memory when the wording differs, BM25 nails exact identifiers, and hybrid mode fuses the two. Exact-key and metadata lookup too.
Yours. Server, engine, and embeddings run on your machine. No hosted memory service, no cloud embedding API.

Install

Claude Desktop — download montycat-mcp.mcpb and drag it into Claude Desktop. No Python needed. That link always serves the current release; every release also carries a version-named copy and a .sha256 to check it against.

Claude Code — install uv, then:

text

/plugin marketplace add MontyGovernance/montycat-mcp
/plugin install montycat-mcp@montygovernance

/mcp confirms the montycat server is connected.

Codex, Cursor, other MCP clients — point your client's stdio config at uvx montycat-mcp (Python 3.10+). For Codex:

bash

codex mcp add montycat -- uvx montycat-mcp

The engine

Memory lives in a Montycat Semantic engine. Montycat MCP starts a local one for you, so most people can stop reading here.

Point it at an engine you already run:

server.ts

export MONTYCAT_URI="montycat://memory-agent:password@localhost:21210/memories"
export MONTYCAT_TLS=true   # remote engines only

Or start one yourself with Docker:

Terminal

docker run -d --name montycat -p 21210:21210 -p 21211:21211 \
  -e MONTYCAT_SUPEROWNER=admin -e MONTYCAT_PASSWORD=change-me \
  -v montycat_data:/var/lib/.montycat \
  montygovernance/montycat:semantic

On Apple Silicon use the arm64-semantic tag instead — semantic is the amd64 image, and it crashes under emulation. Port 21211 carries live memory watches.

Use it

Talk to your agent normally; it picks the tool.

Remember that the team chose PostgreSQL for the billing service.

What did we decide about the billing database?

Save this to the shared engineering scope.

scope decides where a memory lives — alice for private, engineering for a team, shared for common. It is a namespace, not a security boundary: for real isolation, give each MCP server its own least-privilege Montycat credential.

Tools

Need	Tools
Store	`montycat_remember`, `montycat_remember_bulk`, `montycat_update`, `montycat_forget`
Recall	`montycat_semantic_search`, `montycat_recall`, `montycat_list_memories`
Inspect schemas	`montycat_list_enforced_schemas` — check field names and data types before structured writes or filtered retrieval
Collaborate	`montycat_await_memory_change` — wait for another agent's write, no polling
Namespaces	`montycat_list_keyspaces`, `montycat_create_keyspace`, `montycat_remove_keyspace`
Admin	semantic index, snapshot, and policy tools — see the plugin guide

Destructive tools are declared as such, so your client's confirmation prompts apply.

Configuration

Variable	Purpose
`MONTYCAT_URI`	Connection string: `montycat://user:password@host:port/store`
`MONTYCAT_TLS`	`true` for a remote TLS engine
`MONTYCAT_DEFAULT_KEYSPACE`	Memory namespace; `memory` by default
`MONTYCAT_SCOPE`	Default scope when a call omits one
`MONTYCAT_AUTO_PROVISION`	Create a permitted scope on first use; `true` by default
`MONTYCAT_AUTOSTART`	`off` to require an already-running engine

Compose setup and the full variable list: compose.yaml and the plugin guide.

Changelog · Privacy · Issues · Docs · Docker Hub

Existing MemoCat installs keep working: memocat-mcp, MEMOCAT_*, and memocat:// are still supported. New setups should use the Montycat names.

MIT

Read the full README →View source on GitHub →

Related MCP Servers

View all in Knowledge & Memory View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Montycat MCP — Shared AI Memory

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "montycat-mcp-shared-ai-memory": { "command": "npx", "args": ["-y", "Montycat MCP — Shared AI Memory"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Montycat MCP — Shared AI Memory AllMCPs Directory Badge

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/montycat-mcp-shared-ai-memory?style=directory)](https://allmcps.com/mcp/montycat-mcp-shared-ai-memory)

HTML Embed

<a href="https://allmcps.com/mcp/montycat-mcp-shared-ai-memory"><img src="https://allmcps.com/api/badge/montycat-mcp-shared-ai-memory?style=directory" alt="Montycat MCP — Shared AI Memory on AllMCPs" /></a>

Technical Specs & Signals

CategoryKnowledge & Memory

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Featured

AllMCPs Server

The official MCP server for AllMCPs.com - submit and manage tools directly from your AI. The open directory for MCP servers. Connect Claude, Cursor, Windsurf, and AI agents to databases, tools, files, and APIs. Explore 10,000+ servers. AllMCPs is the premier, open directory for discovering, evaluating, and installing Model Context Protocol (MCP) servers to equip AI agents and LLMs with real-world superpowers.

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 🧠 Knowledge & Memory →Best MCP servers for Memory & Knowledge →Alternatives to Montycat MCP — Shared AI Memory →Install in Claude Desktop Install in Cursor Install in VS Code