Skip to content
Agentmart
Submit a tool

Montycat MCP - Shared Memory for AI Agents

Shared, persistent memory for AI agents, with semantic recall and live updates.

Connector by MontyGovernance · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)★ 24
Write a review

Chalk Labs

Need help deploying Montycat MCP - Shared Memory for AI Agents?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/montygovernance-montycat-mcp

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Shared, persistent memory for AI agents, with semantic recall and live updates.

Use cases: agent-memory, knowledge-base

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.

Tools
9 read · 12 write · 2 delete · 2 not yet classified
Secrets
1 (API keys, tokens or passwords)
Install scripts
None found
Runs as
Python package

Tools by what they do 25

Read from the source code; the running server may list different tools.

Read 9 · Look things up without changing anything.

  • montycat_list_enforced_schemas
  • montycat_list_keyspaces
  • montycat_list_memories
  • montycat_policy_explain
  • montycat_policy_history
  • montycat_policy_view
  • montycat_recall
  • montycat_semantic_search
  • montycat_semantic_status

Write 12 · Create, change, send or run things.

  • montycat_create_keyspace
  • montycat_disable_semantic
  • montycat_enable_external_vectors
  • montycat_enable_semantic
  • montycat_install_engine
  • montycat_reembed_semantic
  • montycat_remember
  • montycat_remember_bulk
  • montycat_start_snapshots
  • montycat_stop_snapshots
  • montycat_update
  • montycat_update_cache

Delete 2 · Delete, drop, revoke or wipe things.

  • montycat_forget
  • montycat_remove_keyspace

Not yet classified 2 · We could not tell from the name and description.

  • montycat_await_memory_change
  • montycat_clean_snapshots

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

  • MONTYCAT_URI

Other settings (environment variables or headers).

  • MONTYCAT_TLS
  • MONTYCAT_TLS_CERTIFICATE_FINGERPRINT
  • MONTYCAT_TLS_CERTIFICATE_PATH
  • MONTYCAT_TLS_VERIFY

Network hosts it talks to 6

  • downloads.montygovernance.com · found in code
  • github.com · found in code
  • infra.montygovernance.com · found in code
  • json.schemastore.org · found in code
  • montygovernance.com · found in code
  • repo-deb.montygovernance.com · found in code

Files it touches

  • /opt/homebrew/bin/montycat_bin
  • Your home directory (~)

Tools (25)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • montycat_await_memory_changeWait for Memory Change

    Wait until memory CHANGES — returns the moment another agent or session writes, updates, or deletes something in this memory. This is a live subscription to the database, not a poll: it sleeps until a change actually happens and then returns immediately. Use it to coordinate with other agents sharing a scope ("tell me when someone adds to our shared memory"), or to confirm a write from another session landed. Do NOT call it in a tight loop as a substitute for searching — to *find* things, use montycat_semantic_search. Returns `{changes: [...], next_seq, oldest_seq, cursor_expired, timed_out}…

  • montycat_clean_snapshotsDelete Memory Snapshots

    Delete snapshot files for one existing in-memory keyspace. This is destructive to the keyspace's snapshot history but does not delete its currently loaded in-memory records. Montycat performs the final authorization check. Args: keyspace: Explicit in-memory keyspace whose snapshots are cleaned.

  • montycat_create_keyspaceCreate Memory Keyspace

    Create a new memory namespace using the configured owner's authority. A delegated owner can create a keyspace when its governance policy grants `provision-keyspace` for the requested store, storage type, and semantic model, but its store must already exist. With superowner credentials, the engine creates a missing configured store and this first keyspace together in the same provisioning request. The engine remains the final authorization boundary. Args: keyspace: Name of the keyspace to create. storage: Preferred storage type: "persistent" or "inmemory". Defaults to "pe…

  • montycat_disable_semanticDisable Semantic Search

    Disable semantic search for one explicit keyspace. Stored vectors are retained by default so re-enabling can resume without a full rebuild. Set `drop_vectors` only when intentionally clearing vectors, such as before changing embedding models. The engine enforces all governance authority and explicit denials. Args: keyspace: Explicit keyspace to unenroll. store: Target store. Defaults to the configured store. drop_vectors: Also delete stored vectors for this keyspace.

  • montycat_enable_external_vectorsEnable External Vectors

    Enroll a keyspace for caller-supplied embeddings instead of text embedding.

  • montycat_enable_semanticEnable Semantic Search

    Enable semantic search for one explicit keyspace. The engine enforces `manage-semantic`, creator authority, explicit denials, and allowed-model constraints. Existing records are backfilled by the engine. This tool never enables semantic search database-wide. Args: keyspace: Explicit keyspace to enroll and backfill. store: Target store. Defaults to the configured store. semantic_model: Optional model: "minilm", "bge-small", "bge-base", or "e5-small". Omit to use the engine/policy default. field: Optional JSON field to embed instead of the whole stored value…

  • montycat_forgetDelete Memory

    Delete a stored record from memory by key or custom key. Args: keyspace: Memory namespace (defaults to the configured one). key: Montycat-generated key to delete. custom_key: Custom key to delete. wait_for_index: For persistent keyspaces, wait for secondary indexes before returning. Defaults to the engine setting.

  • montycat_install_engineInstall Montycat Engine

    Install the Montycat engine on THIS computer, then start it. Call this only when memory tools report that no engine is running and the user has agreed to install one. Tell them what it does first: it downloads the Montycat Semantic package (~18 MB) and opens your operating system's installer, which asks for an administrator password. On Linux it runs the documented APT installation with `sudo`. Refuses when MONTYCAT_URI is set or the configured host is not this machine — Montycat MCP is pointed at an engine elsewhere, and installing a local one would create a second database and write memori…

  • montycat_list_enforced_schemasList Enforced Schemas

    List schemas enforced on a keyspace, including field data types. Use this before a structured write or retrieval when the target keyspace's required fields or types are unknown. For retrieval, it helps construct correctly typed field filters. This inspection is read-only and never creates a missing keyspace. Args: keyspace: Explicit keyspace name. Takes precedence over scope. scope: Owner/user memory scope (maps to its configured keyspace). Use "shared" for the common keyspace. When both inputs are omitted, the configured default keyspace is inspected.

  • montycat_list_keyspacesList Memory Keyspaces

    List the available memory stores and keyspaces on this Montycat engine.

  • montycat_list_memoriesList Memories

    Browse stored memories — enumerate what is remembered, not search by meaning. Returns up to `limit` records with their keys. Use this to review or list memory; for meaning-based recall use montycat_semantic_search, and for exact lookups use montycat_recall. Args: keyspace: Memory namespace (defaults to the configured one). limit: Max records to return (default 25). recent: Return the most recently written records first (default True). Persistent keyspaces order by key, which is a strict write order; in-memory keyspaces have no ordered read, so there the …

  • montycat_policy_explainExplain Policy Decision

    Explain whether the configured owner may perform a proposed action. This is a read-only policy check for planning and diagnostics; executing the action still requires a separate tool call and fresh engine authorization. The explanation identifies applicable grants, denials, creator authority, and storage/model constraints. Args: capability: One of "provision-keyspace", "remove-keyspace", "manage-snapshots", "manage-semantic", "manage-schema", or "manage-access". store: Target store. Defaults to the configured store. keyspace: Optional target keyspa…

  • montycat_policy_historyView Policy History

    View governance history visible to the configured owner. This is read-only and owner-scoped by the authenticated Montycat credential. It can show when authority was delegated, denied, revoked, or transferred without allowing the MCP caller to select another owner. Args: store: Optional store filter. Defaults to the configured store. keyspace: Optional keyspace filter.

  • montycat_policy_viewView Memory Policy

    View the configured owner's effective Montycat governance policy. This is read-only. It reports the authenticated owner's effective grants, denials, accessible and owned keyspaces, automatic creator capabilities, provisioning constraints, and policy health. The engine filters the result and remains the authorization boundary. Args: store: Optional store to inspect. Defaults to the store configured by MONTYCAT_URI or MONTYCAT_STORE.

  • montycat_recallRecall Memories

    Recall memory by exact key or by field filter (not by meaning). Provide `key`/`custom_key` to fetch a single record, or `filters` (a map of field -> value) to look up all records matching those fields. For meaning-based recall use montycat_semantic_search instead. Args: keyspace: Memory namespace (defaults to the configured one). key: Montycat-generated key to fetch. custom_key: Custom key to fetch. filters: Field equality filters, e.g. {"user": "alice", "topic": "billing"}. limit: Max results for a filter lookup (default 25).

Show 10 more tools
  • montycat_reembed_semanticRebuild Semantic Vectors

    Replace an enrolled keyspace's text embedding model and backfill it. This clears its current vectors, then has the engine rebuild them. Use `montycat_semantic_status` to observe the resulting configuration.

  • montycat_rememberStore Memory

    Store a fact or record in memory; it is embedded and indexed automatically. Later recall it by meaning with montycat_semantic_search, or by key with montycat_recall. Returns the generated key in `payload`. Every record is auto-stamped with an indexed `_created_at` (UTC ISO-8601) unless the value already carries one — this powers time-range recall (`since`/`until` on montycat_semantic_search). Top-level fields are indexed, so they can be used as `filters` in hybrid search (e.g. store `{"project": "x", ...}`, later filter on it). Args: value: The record to store (a JSON object). scope…

  • montycat_remember_bulkStore Multiple Memories

    Store many memories at once; all are embedded and indexed automatically. Args: values: A list of records (JSON objects) to store. keyspace: Memory namespace (defaults to the configured one). timestamp: Index a `_created_at` on each record for time-range recall. Defaults to MONTYCAT_AUTO_TIMESTAMP (on). Pass False for large imports that will never be recalled by time — it skips a server-side timestamp parse per record. wait_for_index: For persistent keyspaces, wait for secondary indexes before returning. Defaults …

  • montycat_remove_keyspaceDelete Memory Keyspace

    Permanently remove a memory namespace using the owner's authority. This is a destructive lifecycle operation. Before removal Montycat MCP closes the keyspace's live watch and releases MCP resource-subscription ownership so the engine cannot deadlock on a lingering subscriber. The engine then enforces `remove-keyspace`, creator authority, and explicit denials. Args: scope: Owner/user scope to remove (maps to keyspace mem_<scope>). Use "shared" for the configured shared keyspace. keyspace: Explicit keyspace override (advanced; bypasses scope).

  • montycat_semantic_searchSearch Memories

    Search stored memory by MEANING, by KEYWORD, or both. Use this to recall relevant facts, documents, or past context for RAG and agent memory. Returns the top matches ranked by relevance, each with its key, a score, and the stored value. Ranking modes (`mode`): - "semantic" (default) — vector similarity. Finds a memory whose wording differs from the query. Scores are cosine similarity in [-1, 1]. - "keyword" — BM25 over the stored text. Use it when the query contains an exact term that must appear: an identifier, error code, or file name. BM25 scores are unbounded and comparab…

  • montycat_semantic_statusView Semantic Search Status

    Read the engine's actual semantic configuration and backfill state. Pass both `store` and `keyspace` for one keyspace. Omitting both asks for the database-wide view, which may require superowner authority.

  • montycat_start_snapshotsStart Memory Snapshots

    Start scheduled snapshots for one existing in-memory keyspace. Montycat enforces `manage-snapshots`, creator authority, and explicit denials. If the response says "Snapshot rate is not set", snapshot scheduling is not configured on the engine; that is an environmental configuration error, not an authorization denial. This tool cannot alter the global snapshot rate. Args: keyspace: Explicit in-memory keyspace to snapshot.

  • montycat_stop_snapshotsStop Memory Snapshots

    Stop scheduled snapshots for one existing in-memory keyspace. Existing snapshot files are retained. Montycat performs the final authorization check. Args: keyspace: Explicit in-memory keyspace whose snapshot schedule stops.

  • montycat_updateUpdate Memory

    Revise an existing memory in place (memory is mutable). Use this when a stored fact changes — a corrected value, an updated preference — instead of storing a duplicate. Only the fields you pass are changed. Identify the record by `key` or `custom_key`. Args: updates: Fields to change, e.g. {"status": "resolved"} or {"name": "Alice"}. keyspace: Memory namespace (defaults to the configured one). key: Montycat-generated key of the record to update. custom_key: Custom key of the record to update. wait_for_index: For persistent keyspaces, wait for secondary indexes …

  • montycat_update_cacheUpdate Keyspace Cache

    Change the cache capacity of an existing persistent keyspace. Args: cache: Cache capacity in MB. Must be a positive integer. scope: Owner/user scope (maps to keyspace mem_<scope>). Use "shared" for the configured shared keyspace. keyspace: Explicit keyspace override (advanced; bypasses scope).

Signals

Stars
24
Forks
6
Open issues
2
Contributors
4
Weekly downloads
83
Last commit
Oct 4, 2026 (26 days ago)
Last release
Oct 4, 2026 (26 days ago)
Last package publish
Oct 4, 2026 (26 days ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name
io.github.MontyGovernance/montycat-mcp
Version
1.1.6
Auth
API key
Packages
pypi montycat-mcpoci docker.io/montygovernance/montycat-mcp:1.1.6
License
MIT
Repository
github.com/MontyGovernance/montycat-mcp
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
Official MCP Registrygithub-graphql

More from MontyGovernance

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get Montycat MCP - Shared Memory for AI Agents running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying Montycat MCP - Shared Memory for AI Agents?

CallGet help
Cite this page

Montycat MCP - Shared Memory for AI Agents. Agent Mart. https://agentmart.dev/connectors/montygovernance-montycat-mcp (last updated 2026-10-24)