Skip to content Products / Hosted MCPs
/ ExplicitMem MCP
MCP Available
Memory that survives across agent sessions
ExplicitMem MCP stores named memory objects and retrieves them in later agent sessions with their source records attached.
Best for
Teams running agents over long projects where context must survive sessions.
Access and usage
Available through the hosted catalog. Calls count against the shared allowance on the account plan.
Compare usage plans
Why it exists
Store named memory objects and retrieve them in later agent sessions without relying on chat history that disappears between sessions.
Generic terminals, provider APIs, and custom prompts can cover parts of the work, but the caller must supply permission limits, output requirements, failure handling, and usage accounting.
Connection and contract
Connect from an MCP-aware client with an account-scoped Monarchic key. The hosted route checks access, runs the named product contract, and records the operation on the account receipt.
The product-specific schema defines the inputs and outputs used by clients and downstream automation.
Current limits
The gateway checks ownership. Supplying another workspace identifier does not grant access. Project and usage limits still apply.
Requires an authenticated, entitled account and a write-enabled key for remember. Recall can use a read-only key. Replace the workspace and project identifiers with your own.
What you get
- Persist facts, preferences, goals, and working context
- Retrieve bounded context with source records
- Audit memory objects and changes
Core use case
Store named memory objects and retrieve them in later agent sessions without relying on chat history that disappears between sessions.
Outcomes
- Persist facts, preferences, goals, and project context
- Retrieve relevant context with the source memory objects
- Audit what an agent remembered and how it changed
Primary workflows
Write memory Search memory Retrieve context Audit objects
Research
Published benchmark Use dated, versioned artifacts for LongMemEval-S, LoCoMo, cross-dataset retrieval policy, and generic-answer support checks.
Each result applies only to its named dataset, configuration, metric, and artifact. The studies do not establish a cross-product ranking, general agent accuracy, or hosted latency guarantee.
Read benchmark Request
“Remember that production releases require two reviewers, then find that rule.”
Execution
Tool call payload [
{
"tool": "explicitmem_hosted_remember_v1",
"arguments": {
"tenant": "your-workspace-id",
"project": "your-project-id",
"content": {
"text": "Production releases require two reviewers."
},
"scope": {
"kind": "project"
},
"kind": "constraint"
}
},
{
"tool": "explicitmem_hosted_recall_v1",
"arguments": {
"tenant": "your-workspace-id",
"project": "your-project-id",
"query": "What are the release approval requirements?",
"scope": {
"kind": "project"
},
"kinds": [
"constraint"
],
"limit": 5
}
}
]
Stores the constraint in the authorized private project, then retrieves matching memories with provenance.
The remember call returns a storage result. Recall returns a bounded context brief and supporting memories; identifiers and scores depend on the stored project.
Usage rating
Usage is recorded for each operation. Included allowance quantities are not yet published.
- explicitmem_hosted_remember_v1
- explicitmem_hosted_recall_v1
Top ↑