# Connect Claude Code

Add Tyton to Claude Code and sign in to set up one website.



## What you need [#what-you-need]

Open your website’s code in Claude Code. For paid setup you also need a Tyton account and plan. If you don’t have them yet, Tyton walks you through both when you sign in.

## Connect [#connect]

These steps follow [Claude Code’s MCP guide](https://code.claude.com/docs/en/mcp).

1. Add Tyton in your terminal:

```sh
claude mcp add --transport http tyton https://mcp.usetyton.com/mcp
```

2. Start Claude Code and ask it to audit your website. The free audit works without signing in.
3. When you’re ready for paid setup, run `/mcp`, choose Tyton and follow the steps to sign in. Claude Code opens Tyton in your browser. If the browser doesn’t open, copy the link Claude Code shows.
4. Sign in to Tyton, pick your website under **Website it can use** (or **Add a website**), then select **Allow access**.
5. Go back to Claude Code and ask it to continue setup.

## Success check [#success-check]

Claude can read setup progress for the website you picked and tells you its name or address. A connected server in `/mcp` shows Tyton is reachable. Setup progress shows it has access to your website.

## Use a connection key instead (for CI or apps without sign-in) [#use-a-connection-key-instead-for-ci-or-apps-without-sign-in]

If Claude Code runs where it can’t open a browser, connect with a Tyton server key. On the **Integrations** page in Tyton, use **Can’t sign in from your app? Use a pairing code** to get a code for your site, ask Claude to call `connect` with it and `client: "claude_code"`, and have it store the returned key privately.

Then use the key from an environment variable in a project `.mcp.json`:

```json
{
  "mcpServers": {
    "tyton": {
      "type": "http",
      "url": "https://mcp.usetyton.com/mcp",
      "headers": {
        "Authorization": "Bearer ${TYTON_SECRET_KEY}"
      }
    }
  }
}
```

Merge it with existing entries. Supply the variable privately and keep keys out of shell history and shared files. Claude Code expands `${VAR}` in `url` and `headers`, as described in [its MCP guide](https://code.claude.com/docs/en/mcp). A key in the header takes the place of sign-in, so Claude Code won’t ask you to sign in for that entry.

## If you get stuck [#if-you-get-stuck]

* **The sign-in page says the request has ended:** the request timed out or was already used. Run `/mcp` and sign in to Tyton again.
* **Your site slots are all in use:** review your plan in Tyton, or remove a website you no longer need, then sign in again from `/mcp`.
* **Claude connected to the wrong website:** in `/mcp`, choose Tyton and select **Clear authentication**, then sign in again and pick the right one. You can also select **Disconnect** for it on the **Integrations** page in Tyton.
* **The entry runs as a local program:** an HTTP entry in `.mcp.json` needs `"type": "http"`.
* **A key stopped working:** generate a new pairing code if the old one expired, or switch the entry to sign-in.

Connecting and approving tracking are separate. Read [what your agent can do](/docs/connect/permissions).