> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kanaeru.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Kanaeru in Codex, Claude, and ChatGPT

> Talk to your Kana sessions, answer their questions, and open blueprints from inside Codex, Claude, or ChatGPT.

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.

<Note>
  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.
</Note>

<Note>
  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.
</Note>

## Add Kanaeru to your app

<Tabs>
  <Tab title="Codex">
    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:

    ```bash theme={null}
    codex mcp add kanaeru-client --url https://api.kanaeru.ai/mcp/client
    codex mcp login kanaeru-client
    ```
  </Tab>

  <Tab title="Claude Desktop">
    Add a custom connector with the URL `https://api.kanaeru.ai/mcp/client`, then sign in when Claude prompts you. Kanaeru's views open right inside the conversation.
  </Tab>

  <Tab title="ChatGPT">
    <Note>Coming soon. The Kanaeru app for ChatGPT isn't published yet.</Note>

    Once it's available, your sessions, question cards, and blueprints will open inside the ChatGPT chat, and you'll be able to export a blueprint as a file.
  </Tab>

  <Tab title="Claude Code">
    ```bash theme={null}
    claude mcp add --transport http kanaeru https://api.kanaeru.ai/mcp/client
    ```

    Then run `/mcp` in Claude Code, choose **kanaeru**, and authenticate. Your browser opens the **Connect to Kanaeru** page. Claude Code gets the tools without the interactive views.
  </Tab>
</Tabs>

## 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](/cli/overview) 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.

| Your agent runs... | Use |
| - | - |
| Inside an app such as Codex, Claude, or ChatGPT | The Kanaeru app, at `/mcp/client` |
| In a terminal or a script | The [Kana CLI](/cli/overview) |

## 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.

<Warning>
  Authorizing gives the client access to your Kanaeru account. If you didn't just start a connection, choose **Reject**.
</Warning>

## Discovery endpoints

For client developers, these are the OAuth metadata endpoints:

| Endpoint | Purpose |
| - | - |
| `https://api.kanaeru.ai/.well-known/oauth-protected-resource/mcp` | Protected resource metadata (RFC 9728) |
| `https://api.kanaeru.ai/.well-known/oauth-authorization-server` | Authorization server metadata |
| `https://api.kanaeru.ai/.well-known/openid-configuration` | OpenID-style configuration |

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

<CardGroup cols={2}>
  <Card title="Tool reference" icon="wrench" href="/mcp/tools">
    What the Kanaeru app can do.
  </Card>

  <Card title="Kana CLI" icon="terminal" href="/cli/overview">
    The same account, from your terminal.
  </Card>
</CardGroup>


## Related topics

- [Kanaeru overview](/index.md)
- [Runtimes](/machines/runtimes.md)
- [Connect a machine](/machines/connect-a-machine.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.