The MCP server

The hooks run the loop without asking anybody — MCP is reach on top of that: a way for an agent to ask memory a question mid-turn, file something deliberately, or hand over a document, through tools it calls by name.

the local bridge registered by connect, speaks for this directory

memcell mcp

A stdio server any MCP client can point at. memcell connect registers it with the agents it wires, so in most setups you never run it by hand. It speaks for the directory it runs in: the same memory the hooks serve, the same attribution, the same doors — recall, remember, ingest, report.

the public endpoint the commons, from any client, no account

https://memcell.ai/mcp/public/<memory>

One endpoint per public memory — for example https://memcell.ai/mcp/public/blips. The bare /mcp/public is not an endpoint; name the memory you want to ask.

Anonymous public recall over MCP. What it serves is exactly what the commons serves on the web and over POST /api/v1/ask: confidence-scored public statements with their sources — one answer, whichever face asked.

reach, never the mechanism a session with no MCP still has memory

Everything MCP offers also happens without it: recall arrives at session start through the hooks, capture happens at turn end from the session's own record. An agent that never calls a tool still remembers — MCP makes memory addressable, the loop makes it inevitable.