Show HN: Itsuki – open-source memory engine for AI agents (API and MCP)

Itsuki, an open-source memory engine for AI agents, has been launched with an API and MCP support, allowing users to connect 26 tools and extract structured memories from conversations, documents, and events. The engine, published under Apache 2.0, is free during early access with about 100 saves per day, and aims to provide durable user context across sessions and channels.

An example memory “We’re on Postgres. No ORM — raw SQL only.” you typed this once, in whichever tool was open. イツキ 01 For the AI tools you already use Connect once with one key. Itsuki extracts structured memories from any of 26 connected tools and serves them back across all the rest. Open source · One key, two minutes · Free during early access 1 2 3 4 5 6 7 { "mcpServers": { "itsuki": { "url": "PASTE THE PRIVATE URL CREATED IN ITSUKI" } } } → recalled in Cursor — “raw SQL only, no ORM”, saved from Claude Code on Monday npm install itsuki pip install itsuki One key · 26 tools — assistants, coding agents, workflows One store sits under all twenty-six. Type the fact once, in whichever tool happens to be open, and the next tool to ask gets it back — no export, no re-paste, no second store to keep in sync. Typed once, in Claude Code An example memory “We’re on Postgres. No ORM — raw SQL only.” you typed this once, in whichever tool was open. Everyone else replays the transcript and hopes the model finds the point. Itsuki keeps the point, the exact words it came from, and the shape of what it connects to. “hey are we still on for the review” “let me check the calendar one sec” “ok so september is completely packed” “we're moving the pricing review to october” “who's calling it?” “the growth lead owns it now” “cool, i'll tell the team” “thanks ” + 10 more turns of the same, replayed on every request. Discarded on purpose: greetings, scheduling chatter, and questions with no durable answer. Your rules decide what never becomes memory. “Who moved the pricing review, and when?” A worked example. Every memory stays linked to the words it came from — your agent receives four typed objects and a source it can cite, not eighteen turns to re-read and guess at. Four moves. One living memory. Conversations, documents, and events enter through one consistent memory API. “The pricing review moved from September to October.” Conversation · Document · EventInput accepted · ready to structure Scope attachedBuild personalization, support, and adaptive experiences from durable user context. Carry preferences, decisions, and important history across sessions and channels. Recall the right facts and relationships without flooding the prompt with history. Share structured memory across queues, jobs, n8n workflows, and backend services. Move fast without turning memory into a black box. The Itsuki principleRead the extraction engine. Read the admission rules that decide what becomes memory. Read the delete path. The engine, the SDKs and the schema history are published under Apache 2.0 — memory infrastructure you cannot inspect is just another black box. Publication runs behind deployment: the hosted service is built from a development line, so the newest modules and migrations reach the repository later. Connect a tool, save one conversation, and recall it in the next one. Free during early access — about 100 saves a day.