Skip to main content
Kanaeru ships an MCP app that brings your Kana work into Codex, Claude Desktop, Claude Code, and ChatGPT. From the app you can open your conversations, message any Kana session, answer her question rounds, and view blueprints. The work still runs on each session’s own agent machine and runtime: the host app only shows it and lets you steer it. In apps that support MCP app interfaces, such as Claude Desktop, Kanaeru shows its own interactive views: your session, question cards, and the blueprint viewer. In apps that don’t, such as Claude Code, you get the same tools as plain text. The app connects to the Kanaeru client server, https://api.kanaeru.ai/mcp/client, over Streamable HTTP. You sign in with OAuth, so you never paste a token.
The Kanaeru client server is the only Kanaeru MCP server meant for you to connect. Kana’s own agents use a separate server for their tools inside Kana sessions. Don’t connect your agents to it.
You need an active Kanaeru account. Accept your invite and finish onboarding in the web app first. Until onboarding is complete, MCP requests from your account are refused.

​
Add Kanaeru to your app

Install the Kanaeru for Codex plugin. It connects to the client server and teaches Codex to show your outcomes, sessions, blueprints, and reviews in its own conversation, browser, and file views.To connect the server without the plugin:

​
Let your coding agent drive Kana

Any coding agent that can run commands, such as Claude Code or Codex, can also use the Kana CLI directly: create conversations, send messages, answer questions, and approve work. On a computer connected through the Agent Manager, kana already works without a separate sign-in, because it falls back to the machine’s credential. Elsewhere, run kana login once.

​
Signing in

When your client connects, your browser opens Connect to Kanaeru. Sign in with the same account you use for the web app. Tokens last 30 days and refresh automatically.

​
Signing in from another device

Clients running somewhere without a browser, such as over SSH or in a container, can use the device flow instead. The client shows a URL and a code. Open the URL on any device, check that the Authorize an MCP client page shows the same code, and choose Authorize. Codes expire after 10 minutes.
Authorizing gives the client access to your Kanaeru account. If you didn’t just start a connection, choose Reject.

​
Discovery endpoints

For client developers, these are the OAuth metadata endpoints: Supported grants are authorization code with PKCE (S256 only), refresh token, and the device authorization grant. Scopes are mcp:tools, openid, and email. Access tokens are opaque, and no ID tokens are issued. The server is stateless: it serves POST only and never opens a server-sent event stream.

​
Next steps

Tool reference

What the Kanaeru app can do.

Kana CLI

The same account, from your terminal.