Kinjot in Codex.

Set up your account

Install Node.js 22.13 or newer (Node 23 requires 23.4 or newer), and your coding client. Run these commands on the machine where the client starts its MCP servers.

1. Create a free Kinjot account and follow the confirmation email, or sign in to your existing account.
2. Open Settings → Agent connections and create a key. The default level, Read and create, lets agents save and search notes; choose Full access if they should also edit or append to notes, as session autosave does.
3. Install the CLI and enter the key at its prompt:

npm install --global kinjot
kinjot key

The prompt validates your key online and saves it to ~/.kinjot/config.json. Your client can then start Kinjot without a key in its command or MCP configuration. Without a global install, use npx -y kinjot key.

Keep the key private. Do not paste it into a conversation, a note, or a shared config. Revoke an exposed key in Settings → Agent connections and run kinjot key with a new one.

Add the MCP server

codex mcp add kinjot -- npx -y kinjot
codex mcp list

Restart your Codex session. In the CLI, /mcp shows active servers. The CLI, IDE extension, and desktop client share MCP configuration on the same host.

To configure it manually instead, add this table to ~/.codex/config.toml:

[mcp_servers.kinjot]
command = "npx"
args = ["-y", "kinjot"]

If native Windows cannot launch npx directly, configure the command wrapper:

[mcp_servers.kinjot]
command = "cmd"
args = ["/c", "npx", "-y", "kinjot"]

Choose one configuration for this server. In WSL, use the Linux configuration and store the key from WSL. See the official Codex MCP documentation for project configuration, timeouts, and tool controls.

Save a fix. Find it later.

After an answer you want to keep, ask your agent:

Jot that down in Kinjot as “Worker environment fix”, with the explanation and commands.

The agent calls jot and reports the saved title, ID, and tags. Kinjot is an explicit notebook: it does not automatically capture your conversation. Say what should be saved; ask for the complete answer verbatim if that is what you want.

In a later session, ask:

Find my Kinjot notes about worker environment.
Read the Worker environment fix jot in full.

find_jots returns compact matches. Choose a note when several match; get_jot brings its body into context. You can also ask “List my recent jots.” On Pro, ask “Find my Kinjot notes by meaning about deployments using stale configuration.”

If something does not connect

• Check node --version and npx --version in the same environment as your client. Restart the client after changing PATH or its MCP configuration.
• Run kinjot where to see the chosen library. If an account key and a desktop library both exist, choose kinjot use account or kinjot use local. Kinjot refuses an ambiguous destination.
• If the key is rejected, replace it with kinjot key. An existing KINJOT_API_KEY environment variable overrides the stored key.
• Account commands need network access and have no offline queue. Check connectivity before retrying. After an uncertain save, search your jots before saving a second copy.
• A write-rate error means wait a minute before retrying (60 writes per minute per key). Recall allows 60 calls a minute per account, and keyword search and open-task reads share 30 a minute per account, across all its keys; the error gives the wait. A Pro error on recall_jots does not prevent free keyword search.
• An error saying the key is read-only, or cannot change existing notes, comes from the key’s level, which is fixed when the key is created. Create a key with more access in Settings → Agent connections, run kinjot key with it, then restart your agent session so it picks up the tools the new key allows.

Windows and WSL have separate home directories and client environments. Store your key where the MCP process runs. A desktop local library must be accessible from that same environment; browser local-mode notes are not accessible through MCP.