Model Context Protocol · MCP Server

Give your agents memory with receipts.

MemoryIntelligence as an MCP server. Your assistant recalls what matters and saves durable decisions on its own, each one backed by a receipt you can verify, across Claude Desktop, Claude Code, and Cursor. One command to set up. Your API key stays in your keychain, never in a config file.

What this is

MCP (Model Context Protocol) is the open standard that lets an AI assistant use external tools. This package is an MCP server: wire it in once, and your assistant gains three memory tools (capture, recall, and list) plus a proactive instinct to use them. Memories are stored as structured Unified Memory Objects, not raw transcripts. Not AI magic. Structured data, with citations.

Set up in one command

Works on macOS, Linux, and Windows. You'll need an API key. Grab one from the developer portal (free during beta).

1
Install the package
From PyPI. Or run it with no install at all via uvx.
$ pip install memoryintelligence-mcp # or, zero-install: uvx memoryintelligence-mcp
2
Run one-command setup
Prompts for your API key (hidden input), stores it securely in your OS keychain, wires Claude Desktop and Claude Code for you, and runs a diagnostic.
$ mi-mcp setup
Your key is never written into any config file. The launcher resolves it from your macOS Keychain (or a chmod 600 keyfile) at runtime. Restart your assistant and your memory tools are live.
Already installed? Re-run mi-mcp setup (or mi-mcp wire) after upgrading the package. An upgrade alone doesn't rewrite your existing config. As of 0.2.1 this also unifies your local .umo vault with the MemorySpace Desktop app (see below).
3
Just talk
No new habits. Your assistant recalls relevant memories before answering and captures durable decisions on its own. Or ask it directly: "remember that we ship releases on Tuesdays" / "what did I decide about the pricing tiers?"

Prefer to wire it by hand?

mi-mcp setup does this for you. If you'd rather edit the config yourself, add the server below. Note there's no key in the file. The launcher resolves it from your keychain.

Claude Desktop · claude_desktop_config.json
{ "mcpServers": { "memoryintelligence": { "command": "/Users/you/.memoryintelligence/mcp/run-mi-mcp.sh" } } } # point it at the launcher (absolute path); it resolves your key # from the keychain. `mi-mcp wire` writes this entry for you.
Claude Code · terminal
$ mi-mcp wire # writes the launcher config (recommended) # check it's healthy any time: $ mi-mcp doctor
VS Code / Copilot · .vscode/mcp.json
{ "servers": { "memoryintelligence": { "type": "stdio", "command": "/Users/you/.memoryintelligence/mcp/run-mi-mcp.sh" } } } # Copilot reads "servers" (not "mcpServers") + needs "type": "stdio". # Point command at the launcher so your key resolves from the # keychain; bare "mi-mcp" only reads MI_API_KEY from env. Use Agent mode.

The tools your assistant gets

Three tools are on by default, all most people need. The full set is opt-in with MI_MCP_FULL=1.

Default surface
ToolWhat it does
mi_captureSave a decision, fact, or preference as a structured memory.
mi_askSearch your memories in natural language. Answers come back with citations.
mi_listBrowse recent memories.
Full surface · MI_MCP_FULL=1
ToolWhat it does
mi_explainSee why a memory matched a query.
mi_verifyVerify a memory's provenance chain.
mi_forgetDelete a memory (with a receipt). Flagged destructive.
mi_batchCapture many items at once.
mi_uploadCapture from a file (PDF text today).
mi_matchCompare two memories for relatedness.
mi_accountAccount info and key status.

What works today

This is beta. Here's exactly what's live; we flag what isn't rather than oversell it.

LiveProactive memory: the assistant recalls and captures on its own (Claude Desktop, Claude Code, Cursor)
LiveCapture, recall (with citations), and list: the three core tools
LivePDF text upload (behind MI_MCP_FULL=1)
ComingAudio and image transcription on upload: not yet functional on the backend
PlannedLocal .umo vault: offline-first, owner-encrypted memory files. mi-mcp wire already points the vault at ~/Somewhere, the same folder the MemorySpace Desktop app reads, so they share one vault (unwired fallback: ~/MemoryIntelligence; an explicit MI_VAULT still wins).

Resources

Stop re-explaining yourself to your AI.