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

# Setup

> Connect Claude, Codex, or any OAuth-capable MCP client to Kontext.

Both Claude and Codex have a first-class **custom connector** flow for remote MCP servers — no config files to edit by hand, no credentials to paste. You hand the client the server URL, it drives the OAuth handshake, and you sign in to Kontext, pick the organization to connect, and approve the scopes.

## Claude (Desktop, web, mobile)

1. Go to **Customize → Connectors** (or click **+** in the chat and choose **Manage connectors**).
2. Click **+ Add custom connector**.
3. Paste the server URL: `https://mcp.getkontext.io`.
4. Click **Add**. Claude opens a browser window for Kontext sign-in and org selection — approve the scopes and you're done.

<Note>
  Custom connectors are available on Pro, Max, Team, and Enterprise plans. On Team and Enterprise, Owners add the connector at the organization level and members then connect individually.
</Note>

## Codex CLI

1. Add Kontext to `~/.codex/config.toml`:

   ```toml theme={null}
   [mcp_servers.kontext]
   url = "https://mcp.getkontext.io"
   ```

2. Trigger the OAuth flow:

   ```bash theme={null}
   codex mcp login kontext
   ```

   Codex opens a browser for sign-in, caches the token, and the server is ready to use in your next Codex session.

## Other clients

Any MCP-compliant client with OAuth support (Cursor, Continue, Zed, custom agents) works the same way — point it at `https://mcp.getkontext.io` and complete the OAuth flow.

## After authorizing

The authorized client appears in **Organization Settings → Connected Apps** in the Kontext web app, with the granted scopes and a revoke button. If you need non-interactive access (CI, servers, cron), issue an [API key](/docs/api-reference/authentication) instead.