Two ways in: an MCP connector for any MCP client, or a REST API for everything else. Both reach one memory graph. New here? The Quickstart walks the whole path in five minutes. Setting someone up as their agent? Follow the setup map for agents: the person creates an account, you connect for every project and they sign in, then after the first kijito_startup you run kijito_onboard(action="start").
MCP is an open standard, so any client that supports remote MCP servers can connect. We have verified Claude Code, Claude.ai (web and desktop) and the REST API end to end; Codex is in testing; other MCP clients should connect the same way, but we have not tested them; and the ChatGPT connector is planned. Each tab below says how far we have tested that client.
remember, recall, dream and the rest of the tools in every conversation.https://api.kijito.ai/mcpKijito is long-term memory for AI agents: a graph your assistant writes to and recalls from, so it continues across conversations instead of starting cold each time. Here is the whole loop, start to finish.
Sign up with an email and password. Your memory content is encrypted under a key derived from that password, so keep it (and your recovery codes) safe - see Security & trust. New accounts start with a small memory allowance; verify your email to lift it to the full free-tier cap.
Add Kijito to your assistant using the connector above. In an MCP client you paste one Streamable HTTP URL and sign in (Claude Code and Claude.ai are verified; the tabs say how far each other client is tested). Using Claude.ai or the Claude desktop app? Follow the step-by-step guide with screenshots. Your agent then has kijito_remember, kijito_recall, kijito_dream and the rest of the tools in every conversation. Prefer to build directly? Use the REST tab for a token-and-curl setup. Once connected, have your agent run kijito_onboard(action="start") after its first kijito_startup: it asks you one setup question at a time, including a name to file its work under.
Just talk. When something matters - a decision, a fact, a preference, where you left off - your agent calls kijito_remember to store it. You can also nudge it: "remember that we chose aqua as the primary accent." One atomic idea per memory works best; the graph links related memories for you.
In a new conversation, ask about it - "what did we decide about color?" Your agent calls kijito_recall, which searches by meaning (not keywords), pulls in the memories connected to the best matches, and returns just the few that are relevant. That is the payoff: continuity without re-reading the whole history.
Open Explore to see what your memory holds, which agent wrote what, the themes that emerge and, on the map, how memories connect. Over time a scheduled "dreaming" pass connects related ideas, ranks low-importance memories lower, and keeps recall sharp - you do not manage any of it.
You don't manage any of this. Your AI does it as you talk:
Kijito exposes a full toolset over MCP, but day to day an agent reaches for a small core - and recall returns only what matters, not a wall of definitions.
kijito_startupSession bootstrap: identity, recent memories, and active goals in one call.kijito_rememberStore a memory. One call, kept until you fade or delete it, recalled by meaning.kijito_recallFind the few memories that relate, by meaning, and the ones connected to them.kijito_correctSupersede a memory without losing the history. The old version is kept.kijito_dreamRun a dreaming pass: strengthen, cluster, link.kijito_hive_send / kijito_hive_inboxMessage other agents on the same graph. Coordinate a hive.Keep going: read Concepts to understand how memory, edges, themes, and dreaming fit together, or jump to the API reference. Questions in the meantime: [email protected].