Labsco
moorcheh-ai logo

Memanto MCP

★ 1,600

from moorcheh-ai

MEMANTO is a memory agent. It remembers, recalls, and answers — so your agents can achieve long-term goals and avoid confusion.

🔥🔥🔥✓ VerifiedAccount requiredNeeds API keys
#devops#git#memory

Memanto MCP Server

Persistent semantic memory for any MCP-compatible agent.

This package exposes Memanto's memory primitives — remember, recall, answer, and friends — as Model Context Protocol (MCP) tools so any MCP client (Claude Desktop, Cursor, Windsurf, Cline, Continue, Goose, custom agents, …) can plug into long-term memory in a single config line.

One Moorcheh API key → typed semantic memory across every agent that shares the namespace, with sub-90 ms retrieval, conflict detection, and zero ingestion latency.

Available tools

The server registers 7 memory tools by default. Set MEMANTO_EXPOSE_ADMIN=true to also expose 4 agent-management tools.

Memory tools (always on)

Tool When the agent should call it remember Persist a single new fact/preference/decision/goal/instruction. batch_remember Persist up to 100 memories in one call (e.g. extracted from a document). recall Semantic search — always check here before asking the user to repeat stable info. recall_recent "What did we just decide?" — newest-first, no query needed. recall_as_of Point-in-time recall — "what did we know on 2025-11-01?" recall_changed_since Differential — "what's new since I last checked?" answer RAG: grounded LLM answer synthesized over the agent's memories.

Agent admin tools (opt-in)

Enabled when MEMANTO_EXPOSE_ADMIN=true:

Tool Purpose create_agent Create a new memory namespace. list_agents List every agent the API key can see. get_agent Look up an agent's metadata. delete_agent Remove an agent's local metadata.

Memory types accepted by remember / batch_remember: fact, preference, goal, decision, artifact, learning, event, instruction, relationship, context, observation, commitment, error.

Provenance values: explicit_statement, inferred, corrected, validated, observed, imported.

How it works

Copy & paste — that's it
┌──────────────┐ MCP/stdio ┌──────────────────┐ Moorcheh API ┌─────────────┐
│ Claude / IDE │ ──────────────► │ memanto-mcp │ ────────────────► │ Moorcheh │
│ (client) │ ◄────────────── │ (this package) │ ◄──────────────── │ Service │
└──────────────┘ tool calls └──────────────────┘ HTTPS+API key └─────────────┘
 │
 └─ uses memanto.cli.client.SdkClient
 (same client the Memanto CLI uses)

  • On startup, settings are validated; the API key is verified lazily on first tool call.

  • On the first memory tool invocation for a given agent, the server ensures the agent exists (auto-creates if needed) and activates a JWT session. Sessions auto-renew before expiry, so long-running MCP connections never hit a session-expired error mid-conversation.

  • The server intentionally keeps the session alive on shutdown: JWT sessions are TTL-bound and other Memanto clients (CLI, REST) may want to share them.

Programmatic embedding

If you're building a custom MCP host or wiring this server into a larger process, you can construct the FastMCP instance yourself:

Copy & paste — that's it
from memanto_mcp import MCPServerSettings, build_server

settings = MCPServerSettings() # reads env / .env
mcp = build_server(settings)

# Add your own tools alongside Memanto's, then run.
mcp.run(transport="stdio")

License

MIT — same as the Memanto project. See LICENSE.

Links