Developers

M.N.E.M.O. is more than Dorothy.

Dorothy is one interface built on M.N.E.M.O. Underneath, M.N.E.M.O. — short for Multidimensional Neural Elastic Memory Organization — is a vector-free memory and knowledge-sharing layer — you can talk to it directly, wire it into Claude Desktop, call it from inside a Claude Code session, or query it as a RAG pipeline from your own app. Same memory, four ways in.

Build your own interface

The same memory and knowledge-sharing layer that powers Dorothy, available for anything you build.

Ingest documents, spreadsheets, or plain text; ask questions in natural language; get back exact stored values, not paraphrased guesses. Every account can create an API token and start integrating — no separate approval step required.

Store and recall memory across sessions, not just one conversation window
Ask questions in plain language — M.N.E.M.O. figures out what you mean and returns the exact stored fact
Organize memory automatically into subjects, so related information stays together without manual folder management
Role-based access built in, so sensitive data can be scoped to the right people as your team grows

Available on Pro and Enterprise

See plans

Give Claude Desktop a memory

A small process that lets Claude Desktop talk to your M.N.E.M.O. memory directly.

M.N.E.M.O. ships as an MCP server. Once connected, you can ask Claude to remember something in a conversation, and recall it weeks later in a completely different session. Claude decides when to save or retrieve automatically; you don't have to invoke anything manually.

Ask Claude to remember decisions, notes, or context from any conversation
Recall that information in a later session — memory persists, Claude doesn't start over each time
Runs as a lightweight local process; no separate account dashboard to manage day to day

Available on Pro and Enterprise

See plans

Bring memory into your coding workflow

Nothing extra to install or keep running — Claude Code talks to your M.N.E.M.O. account directly.

For Claude Code, M.N.E.M.O. is available as a Skill instead of a running server — Claude Code reads a set of instructions and calls it directly. Useful for carrying project decisions, specs, or context across coding sessions instead of re-explaining them every time.

No server process to install or manage — Claude Code uses its own built-in tools
Ask Claude Code to remember a decision, spec, or piece of context from your current session
Pull that memory back up in a future session, on a different day, without re-pasting anything

Available on Pro and Enterprise

See plans

A third retrieval paradigm

MnemoRAG: VectorRAG, GraphRAG, MnemoRAG — plug M.N.E.M.O. into your own RAG pipeline.

Most RAG pipelines retrieve from a vector database or walk a knowledge graph. MnemoRAG is a third option: one stateless POST call to a named, fixed subset of your own M.N.E.M.O. subjects. The eNN reasons over your data, OAT retrieves it exactly, and one synthesized answer comes back — no chat session, no conversation history, no disambiguation step to manage.

Define a MnemoRAG endpoint from Dorothy Settings — name it, describe it, and choose exactly which subjects it can see
Call it with a single request — no session or chat state for your app to track
Evidence from every subject in scope is combined into one answer, never silently blended across mutually exclusive numbers
Pass optional context of your own to ground or validate the answer, without it ever becoming a retrieval target itself
Turn on a full-memory fallback or a general-knowledge fallback per endpoint — both off by default

Available on Pro and Enterprise

See plans

Not just chat

Same memory, four ways in.

Whichever way you connect — API, MCP, Skill, or MnemoRAG — it's the same underlying memory: vector-free, exact recall, built on OAT. Dorothy shows what that feels like in a chat app. These four are how you build your own.

Get API access See plans