Use this reference when your MCP client can only connect to a web address and cannot run the Durmem plugin on your computer. Durmem offers a hosted MCP endpoint that gives such a client the core memory tools for one store.
The Durmem plugin remains the recommended way to use Durmem: it gives your agent every Durmem tool and the guidance that goes with them. Use the web endpoint only when the plugin is not an option.
The endpoint is https://durmem.ai/api/mcp. It accepts MCP requests over HTTPS and answers with JSON. Listing the tools needs no key. Calling a tool needs your store key, sent as a bearer token:
Authorization: Bearer YOUR_STORE_KEYReplace YOUR_STORE_KEY with the store_key of the store you want to open. Each key opens only its own store. See Local Durmem configuration for where the key is kept. Anyone who holds the key can read and change that store, so keep it out of chats, tickets and public repositories, and send it only in the header of the request.
The endpoint offers six tools:
whoami shows which store your key opens.loom_describe_store describes what the store holds.loom_query looks things up in the store: facts by type or label, a fact's history, text search, and the shape of what the store holds. It only reads; anything else is refused.loom_read_probe_bundle finds the facts most relevant to a question.loom_save saves one fact. It cannot save Kanban or worker-fleet records; use the plugin or the durmem command for those.loom_nearest_types suggests existing types close to some text, so you can reuse one.It does not create, delete or revoke stores, retract facts, change rules, or manage Kanban boards. Use the plugin or the durmem command for those.
Requests are limited in size, and each key and each address can make a limited number of requests per minute. When you exceed the limit, the endpoint answers with a "rate limited" error; wait a minute and retry. A missing or wrong key always gets the same "authentication required" answer.