Kinjot in Claude Code.

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 → API keys and create a key.
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 → API keys and run kinjot key with a new one.

Add the MCP server

In your terminal, register Kinjot for your user so it is available across projects:

claude mcp add --transport stdio --scope user kinjot -- npx -y kinjot
claude mcp get kinjot

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

claude mcp add --transport stdio --scope user kinjot -- cmd /c npx -y kinjot

Restart Claude Code, then use /mcp to check the connection. Follow your client’s tool approval prompts. For scopes and configuration options, see the official Claude Code MCP documentation.

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). A Pro error on recall_jots does not prevent free keyword search.

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.