# Connect Cursor

Add Tyton to Cursor and sign in to set up one website.



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

Open your website’s code in Cursor. 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 [Cursor’s MCP guide](https://cursor.com/docs/context/mcp).

1. Add a `tyton` entry to `.cursor/mcp.json` in your project. Merge it with any existing entries:

```json
{
  "mcpServers": {
    "tyton": {
      "url": "https://mcp.usetyton.com/mcp"
    }
  }
}
```

2. Turn Tyton on from **Customize** in Cursor’s sidebar, then ask Cursor to audit your website. The free audit works without signing in.
3. When you start paid setup, Cursor should ask you to sign in to Tyton and open the sign-in page in your browser.
4. Sign in, pick your website under **Website it can use** (or **Add a website**), then select **Allow access**.
5. Go back to Cursor and ask it to continue setup.

You can also add the entry to `~/.cursor/mcp.json` to use Tyton in every project. Each sign-in covers one website, so check it’s the website for the project you have open.

## Success check [#success-check]

Cursor can read setup progress for the website you picked and tells you its name or address. Seeing Tyton’s tools in Cursor shows only that the URL works.

## 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 Cursor can’t complete sign-in, 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 Cursor to call `connect` with it and `client: "cursor"`, and have it store the returned key privately. Then add the key from an environment variable:

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

Provide the variable to the Cursor process securely. A project `.env` file alone doesn’t reach Cursor’s MCP connection.

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

* **No sign-in prompt appears:** open Tyton under **Customize** and check whether it needs sign-in. Connection and sign-in errors show in the Output panel under **MCP Logs**.
* **The sign-in page says the request has ended:** the request timed out or was already used. Start sign-in again from Cursor.
* **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 Cursor.
* **Cursor connected to the wrong website:** select **Disconnect** for it on the **Integrations** page in Tyton, then sign in again and pick the right one.
* **Tools are blocked:** ask your administrator whether your team limits MCP servers.

For a free audit only, use `https://mcp.usetyton.com/audit`, which never asks you to sign in. Keep your Meta CAPI token out of MCP settings; it belongs in Tyton’s secure token field. Continue with [permissions](/docs/connect/permissions).