UMLUniversal Memory Layer Universal Memory Layer
UML is 1 backstage representation chart shared by Claude, your agents, and your apps — you tin spot it, edit it, and ain it.
Free early entree · Open root · You ain your representation · Works pinch API, SDK, dashboard, and MCP-linked clients.
Your memory, arsenic a surviving chart — existent merchandise footage.
How it works
Four steps. Simple capable to explicate to anyone.
1
You talk
Tell your AI: "save this to uml — I vanished Unit 3." Or fto your app nonstop it automatically.
2
UML organizes it
AI extracts the durable facts. The backend verifies them and writes existent building — ne'er a earthy chat dump.
3
You tin spot it
Open the dashboard: a surviving graph, timelines, organized pages — and a receipt for each azygous save.
4
Every instrumentality remembers
Claude, Cursor, your ain supplier — each link to the aforesaid backstage memory. Save once, callback everywhere.
Connect successful 2 minutes
Pick your tool. Paste 1 link. Done.
Sign up, create your backstage representation nexus successful the Connect tab, past paste it into immoderate MCP-capable customer — aliases telephone the API from your ain app.
uml · connect
1Sign up free → unfastened Connect → Create MCP link
2Claude → Settings → Connectors → Add civilization connector
3Paste your backstage nexus and commencement chatting:
Custom connectors request a paid Claude plan. Then conscionable say: "save this to uml" aliases "what do you cognize astir me?"
1Create your MCP nexus successful the Connect tab, past run:
Claude Code gets 3 tools: save_memory, save_conversation, recall_memory.
1Add UML to your MCP config (.cursor/mcp.json):
Works the aforesaid successful immoderate MCP-capable editor aliases supplier host.
1One call: callback applicable representation and auto-save the turn:
Plus /v1/save, /v1/recall, /v1/graph, /v1/rules, /v1/export — aforesaid backstage graph.
Why a graph
Structured memory, not transcript replay.
UML turns useful discourse from chats, events, documents, tools, and workflows into system representation objects — entities, facts, events, relationships, pages, and receipts.
Chat history is not memory.
Messages are root material. UML keeps the durable meaning that should past beyond a azygous exchange.
Memory is system meaning.
UML stores verified entities, facts, events, relationships, rollups, and receipts truthful systems tin logic complete them later.
Backend is the authority, not the LLM.
The LLM proposes; UML verifies; UML writes. Recall and extraction enactment separate.
What makes it different
A chart that tin update, not conscionable append.
New grounds tin create, update, promote, invalidate, aliases supersede memory. UML is not an append-only chat log.
A representation you tin see
Your facts unrecorded successful a ocular chart pinch clusters you tin open, search, drag, and edit — not a hidden blob.
Latest truth wins
Say "actually, that changed" — the aged truth is superseded and kept arsenic visible history connected a timeline, not deleted, not duplicated.
Receipts for each save
Each constitute returns proof: what was saved, updated, aliases refused — pinch root and timestamp. No silent writes, ever.
Your rules
Decide what gets collected and what must ne'er beryllium saved — plain-language rules the backend really enforces.
One graph, galore inputs
Chat is 1 input. Not the full product.
UML tin ingest useful discourse from tools, apps, agents, docs, events, workflows, and civilization schemas.
Chat turnsManual savesDocumentsTool outputsApp events Support ticketsMeeting notesProject rulesWorkflow stateCustom schemas
Private by default
Your representation belongs to you. Provably.
No ads. No trackers. No trading data. No training connected your memory. Export everything arsenic JSON aliases delete it each — immoderate time, 1 click.
Privacy Policy
UML does not waste personification information aliases usage personification representation for unrelated purposes. User representation belongs to the relationship that created it. Connected devices are third-party services and entree UML only done backstage links aliases tokens you create.
Terms of Service
UML is an early merchandise and whitethorn change. Use it responsibly. You are responsible for tokens and backstage links, and you tin revoke them from Connect. Avoid delicate aliases regulated information unless UML is due for that use.
Build representation once. Use it everyplace activity continues.
Free early entree — founding users support the Pro tier free erstwhile paid plans launch.
Support
Need thief connecting UML aliases shaping an integration?
English (US) · 
Indonesian (ID) · 
