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

# Claude Code

> Connect GetWhys to Claude Code from your terminal with individual or organization-level OAuth.

Connect Claude Code to GetWhys from your terminal.

Claude Code has its own MCP configuration. It does not inherit the connector from [Claude.ai or Claude Desktop](/integrations/mcp-claude).

## Connect your individual account

Run:

```text theme={null}
claude mcp add --transport http getwhys https://api.getwhys.io/mcp/org
```

Start Claude Code and run `/mcp`. Sign in to GetWhys when prompted. The connection uses your GetWhys user and permissions.

## Connect with organization-level access

For a shared connection that isn't tied to one user, use an OAuth MCP Connector.

1. [Generate an OAuth MCP Connector](/integrations/mcp-setup#organization-oauth-recommended) in GetWhys with a label such as `claude-code`.
2. On the connector, click **Edit URIs** and add `http://localhost:8080/callback`.
3. Run the following command. Replace `<oauth-client-id>` with the connector's **OAuth Client ID**.

```text theme={null}
claude mcp add --transport http \
  --client-id <oauth-client-id> \
  --client-secret \
  --callback-port 8080 \
  getwhys https://api.getwhys.io/mcp/org
```

4. Enter the connector's **OAuth Client Secret** at the masked prompt.
5. Start Claude Code, run `/mcp`, and complete the connection flow.

Claude Code stores the client secret outside the MCP configuration. If port `8080` is in use, choose another port and use it in both the redirect URI and `--callback-port`.

## Verify

Ask Claude Code: "Who am I in GetWhys?"

Individual OAuth returns your user and organization. An OAuth MCP Connector returns organization-level context.