Memory infrastructure for agents
Mnemolog gives agents durable memory. Your assistant brings the judgment.
Connect with OAuth
Add the MCP URL, approve access, and use the owner's vault without copying a token.
Connect →API Reference
REST endpoints for conversations, imports, agent jobs, billing, and MCP.
Read docs →Protocol Reference
Scopes, memory, jobs, limits, encryption, and machine-readable contracts.
Open reference →MCP Memory quickstart
OAuth-capable clients can discover authorization from the server URL. The owner signs in and approves the requested scopes in the browser.
{
"mcpServers": {
"mnemolog": {
"url": "https://mnemolog.com/api/mcp"
}
}
}
Core MCP tools
Example: "Search my Mnemolog vault for what we decided about pricing." The client calls conversation.search, then conversation.read for the selected source.
Encrypted memory helper
Use scripts/agent_memory/ when your agent should keep plaintext local. It mints or reuses an mna_* token, encrypts with AES-256-GCM before memory.upsert, validates structured records, and includes examples for note sync, reminders, itineraries, and local alert checks.
Scopes & the ownerless policy
Owner-scoped credentials act on a user's vault with explicit scopes. Self-serve ownerless agents may create private temporary memory, run sandbox jobs, and test capabilities — but may not read or write a user's private vault, publish public artifacts, bypass retention limits, or claim owner identity.
Machine-readable surface
These stay stable and discoverable: