Kijito
Get started
Start

Quickstart

Sign up, connect the agent you already use with one command, then watch it remember something in one session and recall it in the next. About five minutes.

1. Create an account

Sign up with an email and a password. Kijito is a free public beta: no card, and billing is off. Your memories are encrypted at rest under a key derived from that password, so save the recovery codes you are shown next. Until you verify your email the account holds up to 100 memories; the link we email you lifts that.

2. Connect your agent

Every client connects to the same address, https://api.kijito.ai/mcp, and there are two ways to authenticate:

  • Sign in with your account - for you, at the keyboard. The client opens a browser, you sign in to Kijito, and the client keeps the session.
  • An API key - for an agent that runs unattended, or in several processes at once. On your account page, under API keys, choose Create API key and name it. Four scopes are offered: memory.read (ticked for you), memory.write, memory.curate - correct and fade memories - and memory.dream - run consolidation. An agent that saves as well as reads needs memory.read and memory.write. Then Create key. The kjt_ key is shown once, so copy it then, and treat it like a password.

Claude Code

Sign in with your account:

terminal
claude mcp add --transport http kijito https://api.kijito.ai/mcp

Then start Claude Code, run /mcp, choose kijito, and authenticate in the browser window that opens. Or connect with an API key instead:

terminal
claude mcp add --transport http kijito https://api.kijito.ai/mcp \
  --header "Authorization: Bearer kjt_your_key"

Check it with claude mcp list, which reports ✔ Connected once the server is reachable and authenticated. The server is added for the current project; add --scope user to use it in every project.

Claude.ai

  1. Open Settings → Connectors and choose Add custom connector.
  2. Name it Kijito, paste https://api.kijito.ai/mcp, and connect.
  3. Sign in with your Kijito account when prompted.

Allow the write tools. Claude.ai asks you to approve each call to a connector tool that changes something, and a call nobody approves comes back to Claude as "No approval received". Set Kijito's tools to always allow in the connector's settings, or approve them the first time Claude asks.

Claude.ai loads connector tools on demand. If Claude says it cannot find a Kijito tool, ask it to search its tools for "kijito recall".

Codex CLI

Sign in with your account (Codex opens the browser for you):

terminal
codex mcp add kijito --url https://api.kijito.ai/mcp

If that sign-in lapses later, run codex mcp login kijito. Or connect with an API key: put it in an environment variable that Codex starts with, and point the server at that variable.

terminal
export KIJITO_API_KEY=kjt_your_key
codex mcp add kijito --url https://api.kijito.ai/mcp --bearer-token-env-var KIJITO_API_KEY

codex mcp list shows the server as enabled, and names how it authenticates under Auth.

OpenCode

Sign in with your account:

terminal
opencode mcp add kijito --url https://api.kijito.ai/mcp
opencode mcp auth kijito

Or connect with an API key: add the server to ~/.config/opencode/opencode.jsonc and keep the key in your environment as KIJITO_API_KEY.

opencode.jsonc
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kijito": {
      "type": "remote",
      "url": "https://api.kijito.ai/mcp",
      "oauth": false,
      "headers": { "Authorization": "Bearer {env:KIJITO_API_KEY}" }
    }
  }
}

opencode mcp list shows ✓ kijito connected when it works.

Keys and desktop apps. An app you launch from the Dock or the Start menu does not see variables exported in your shell profile. If a client connects from a terminal but not from its desktop app, put the key in that app's own MCP configuration instead of an environment variable.

3. Remember something

Start a new session so the client loads the Kijito tools. Ask your agent to begin with kijito_startup: in one call it loads who the agent is, what it did recently, and any active goals. Then give it something worth keeping:

prompt
Call kijito_startup. Then remember: we chose teal as the accent color for the Harbor project.

The agent calls kijito_remember and tells you the id of the new memory. One idea per memory recalls best.

4. Recall it in a fresh session

Close that session, open a new one, and ask:

prompt
What accent color did we pick for Harbor? Check Kijito.

The agent calls kijito_recall, which finds memories by meaning rather than by exact words, and answers from the memory it saved last time. That is the whole loop. Open Memories to see what it stored.

Keep going

  • Concepts - how memories, edges, corrections, and dreaming fit together.
  • Connect another client - ChatGPT, Cursor, other MCP clients, and the REST API.
  • FAQ & troubleshooting - when a client will not connect.
  • Something broken or confusing? Send beta feedback - it goes straight to the people building Kijito.
  • Long-running Claude Code sessions: npx kijito-claude installs optional tools into ~/.claude - context-usage tracking, a session catch-up hook, and the kijito-start and kijito-qa-memory skills - and registers the hook and a context statusline in ~/.claude/settings.json.
Next: Concepts →Connect another client →