Notes
Memories
Suggestions
Universal Memory LayerOne memory service. Multiple ways to connect.
Itsuki gives supported tools and your own apps a private, structured memory API that you can inspect, edit, and export.
Free early access · Open source · You own your memory · Works with API, SDK, dashboard, and MCP-linked clients.
Your memory, as a living graph — real product footage.
How it works
Four steps. Simple enough to explain to anyone.
1
You talk
Tell your AI: "save this to itsuki — I finished Unit 3." Or let your app send it automatically.
2
Itsuki organizes it
AI proposes durable facts. Backend gates verify evidence and either write structured memory or report why a proposal was skipped.
3
You can see it
Open the dashboard to inspect the graph, timelines, organized pages, receipts, and asynchronous job status.
4
Connect supported tools
MCP clients and your own agents can address the same account-scoped service. Each host still decides when to call its tools.
Supported connections
Choose an interface and follow its setup.
Sign up, create your private memory link in the Connect tab, then paste it into any MCP-capable client — or call the API from your own app.
Set up on a computer, not your phone. Neither Claude nor ChatGPT lets you add a connector from their mobile apps — do it once in a computer browser and it syncs to your phone automatically.
itsuki · connect
1Sign up free → open Connect → Create MCP link
2On a computer, open Claude → Customize → Connectors → + → Add custom connector
3Name it itsuki, paste your private link, click Add:
4In a chat, tap the + (bottom-left) → Connectors → switch on itsuki
Remote custom connectors are currently in beta on all Claude plans; Free is limited to one, and organization plans require an owner to add it. Then explicitly ask Claude to use the Itsuki tool.
1On ChatGPT web, a Business or Enterprise/Edu workspace admin enables Developer mode under Apps and starts a custom MCP app.
2Name the app itsuki, review its write tools and permissions, and use this URL:
3Publish or approve it for the workspace, then enable it in a new web chat. ChatGPT may ask for confirmation before a save.
Full MCP write actions currently require Business or Enterprise/Edu on the web. Pro custom apps are read/fetch only.
1Create your MCP link in the Connect tab, then run:
Claude Code gets three tools: save_memory, save_conversation, recall_memory.
1Add Itsuki to your MCP config (.cursor/mcp.json):
Uses a standard Streamable HTTP MCP configuration; tool discovery and invocation still depend on the host.
1One call: recall relevant memory and auto-save the turn:
Plus /v1/save, /v1/recall, /v1/graph, /v1/rules, and /v1/export under the selected account and scope.
Honest MCP note
When Itsuki is connected through an MCP-capable AI client, Itsuki provides memory tools. The client or host model decides when to call them. If you need guaranteed per-turn API invocation, call Itsuki from your own app or agent runtime and inspect the resulting receipt and packet status.
Why a graph
Structured memory, not transcript replay.
Itsuki turns context submitted through its supported save, conversation, ingest, and MCP interfaces into structured memory objects — entities, facts, events, relationships, pages, and receipts.
Chat history is not memory.
Messages are source material. Itsuki keeps the durable meaning that should survive beyond a single exchange.
Memory is structured meaning.
Itsuki stores verified entities, facts, events, relationships, rollups, and receipts so systems can reason over them later.
Backend is the authority, not the LLM.
The LLM proposes; Itsuki verifies; Itsuki writes. Recall and extraction stay separate.
What makes it different
A graph that can update, not just append.
New evidence can create, update, promote, invalidate, or supersede memory. Itsuki is not an append-only chat log.
A memory you can see
Your facts live in a visual graph with clusters you can open, search, drag, and edit — not a hidden blob.
Supersession with history
When new evidence is classified as an update to the same fact, the prior value can be superseded and retained as timeline history.
Receipts for every save
Write responses include a receipt describing what was saved, updated, or refused; asynchronous work also exposes packet and job status.
Your rules
Decide what gets collected and what must never be saved — plain-language rules the backend actually enforces.
One graph, supported inputs
Chat is one input. Not the whole product.
Applications can submit chat, document, tool-result, event, and workflow-state context through Itsuki's supported APIs and connectors.
Chat turnsManual savesDocumentsTool outputsApp events
Support ticketsMeeting notesProject rulesWorkflow stateAPI events
Private by default
Your memory stays under your control.
No ads. No trackers. No selling data. No training on your memory. Export everything as JSON or delete it all — any time, one click.
Privacy Policy
Itsuki does not sell user data or use user memory for unrelated purposes. User memory belongs to the account that created it. Connected tools are third-party services and access Itsuki only through private links or tokens you create.
Terms of Service
Itsuki is an early product and may change. Use it responsibly. You are responsible for tokens and private links, and you can revoke them from Connect. Avoid sensitive or regulated data unless Itsuki is appropriate for that use.
Build structured memory into the tools where work continues.
Free early access — founding users keep the Pro tier free when paid plans launch.
Support
Need help connecting Itsuki or shaping an integration?
Contact support
Open source
Itsuki's engine is open source under Apache 2.0 — read the code, open issues, or star the repo on GitHub.