Docs Cursor

Clients · 03

Cursor

Cursor reads a Suit from its config file, with the lines the Suit's overview writes for you. Here are those lines for each access mode, how to sign in with OAuth, how to check it fits, and what to try when it doesn't.

Your setup, on your Suit

Open one of your Suits and find Dress a client on its overview. Choose Cursor in the picker to see only its steps, written for that Suit: its name, its URL and, in Bearer token mode, the variable its token is read from. Your browser remembers the client you chose.

The steps depend on the Suit's access mode, which shows beside its name, so this page has a section for each access mode. Copy setup as prompt copies the same steps as instructions an agent can follow. They hold no secret the steps don't: a token stays in its variable, and only a Signed URL Suit's prompt has its signed URL.

Cursor knows a Suit as tuxedo- followed by its slug, such as tuxedo-code-reviewer for a Suit named Code reviewer. The slug is made from the Suit's name when you create it and stays the same when you rename the Suit, so a client you've set up keeps working.

An example Suit

The steps on this page are for an example Suit named Code reviewer, so its URL is in them, not yours, and its signed URL's signature shows as …. Copy your own steps from your Suit's overview.

OAuth

Clients send you to Tuxedo to sign in and approve them, so there is no secret to copy. You can revoke each app you approved on its own.

  1. Add Code reviewer to Cursor

    Add this to ~/.cursor/mcp.json, keeping anything already in it:

    ~/.cursor/mcp.json
    {
      "mcpServers": {
        "tuxedo-code-reviewer": {
          "url": "https://tuxedo.bot/mcp/example0000000000000"
        }
      }
    }
  2. Sign in and approve it

    Then sign in when Cursor's MCP settings say tuxedo-code-reviewer needs it, or with the Cursor CLI. Approve it in Tuxedo when your browser opens.

    terminal
    cursor-agent mcp login tuxedo-code-reviewer

    Sign in to Tuxedo if you aren't already. Tuxedo then asks whether to let the client, by the name it gave Tuxedo, wear the Suit, and lists what it could do. Only approve it if you just added the Suit to Cursor yourself, and do it signed in as the account that owns the Suit: another account can't. If you're signed in as someone else, choose Not you? Switch account. Once you choose Approve, Cursor is listed under Connected apps on the Suit's Access page, where you can revoke it.

  3. Check it fits

    Restart Cursor and ask it to list its tools. This turns green as soon as Code reviewer hears from it.

Bearer token

Clients send a token you create for each of them in a header. You can revoke each token on its own.

  1. Put a token in your shell

    On the Suit's overview, choose Create a token for Cursor → beside this step. It opens the Suit's Access page with a token named Cursor, ready to create. Choose Create token, and Tuxedo shows the token, only this once, as a line for your shell profile, such as ~/.zshrc:

    ~/.zshrc
    export TUXEDO_CODE_REVIEWER_TOKEN=txd_…

    Cursor reads the token from TUXEDO_CODE_REVIEWER_TOKEN when it starts, so after adding the line, open a new terminal and restart Cursor from there. Next: set up a client takes you back to these steps.

  2. Add Code reviewer to Cursor

    Add this to ~/.cursor/mcp.json, keeping anything already in it:

    ~/.cursor/mcp.json
    {
      "mcpServers": {
        "tuxedo-code-reviewer": {
          "url": "https://tuxedo.bot/mcp/example0000000000000",
          "headers": {
            "Authorization": "Bearer ${env:TUXEDO_CODE_REVIEWER_TOKEN}"
          }
        }
      }
    }
  3. Check it fits

    Restart Cursor and ask it to list its tools. This turns green as soon as Code reviewer hears from it.

Never paste a token into a config file. The snippet holds only the variable's name, and Cursor reads the token from it. Give each client its own token, so you can revoke one without the others.

When a Suit already has as many tokens as it can, its Access page says so instead of opening a new one: This Suit has 10 tokens, the most a Suit can have. Revoke one to create another.

Signed URL

One secret URL that works by itself, for clients that only take a URL. Anyone with it can use the Suit; rotate it to stop the old one working.

  1. Add Code reviewer to Cursor

    Add this to ~/.cursor/mcp.json, keeping anything already in it:

    ~/.cursor/mcp.json
    {
      "mcpServers": {
        "tuxedo-code-reviewer": {
          "url": "https://tuxedo.bot/mcp/example0000000000000?v=1&signature=…"
        }
      }
    }
  2. Check it fits

    Restart Cursor and ask it to use one of Code reviewer's tools. This turns green as soon as Code reviewer hears from it.

The URL is the secret

The snippet holds the Suit's signed URL. Keep it out of shared or committed files; if it leaks, rotate it on the Access page and set up your clients again.

Check it fits

The last step, Check it fits, starts listening when you open the Suit's overview, or, once anything has reached the Suit, when you open Dress a client. It says Waiting for a call from Cursor… with what to do, as in the last step of each section above. When it turns green, it says Cursor reached Code reviewer with how long ago, then It's set up. Its calls show in Activity. See Activity → opens Activity for the Suit.

A request that names no client, such as one made with a token named Laptop, or a call over a signed URL, can turn it green whichever client you chose.

If it doesn't turn green, it stops listening and says No call from Cursor yet, then Stopped listening after 10 minutes. Listen again once you've set it up. Choose Listen again to wait again, or Troubleshoot for tips, the ones under Troubleshooting below.

The green dot

A green dot beside Cursor in the picker means the Suit has a token that has been used, a connected app, or a call in its Activity, named for Cursor. So name each token after its client, as Create a token for Cursor → does. A signed URL carries no name, so its calls never light the dot.

Troubleshooting

Start with the Suit's access mode, which shows beside its name. A Suit accepts only its current mode, so switching stops clients using the old one, and you set each of them up again.

Until Check it fits turns green, choosing Troubleshoot shows tips for the Suit's mode:

OAuth

  • Cursor has to sign in to Tuxedo and you approve it for Code reviewer. Once you have, it is listed under connected apps on the Access page.
  • Approve it signed in as the account that owns Code reviewer. Another account can't.
  • Check that Cursor lists tuxedo-code-reviewer among its MCP servers without an error.

Bearer token

  • Cursor reads the token from TUXEDO_CODE_REVIEWER_TOKEN when it starts. After adding it to ~/.zshrc, open a new terminal and restart Cursor from there.
  • A revoked token is refused. Check the token is still listed on the Access page, or create another.
  • Check that Cursor lists tuxedo-code-reviewer among its MCP servers without an error.

Signed URL

  • A signed URL doesn't say which client uses it, so only tool calls are noted. Listing the tools isn't enough.
  • Rotating the URL on the Access page stops the old one working. Set Cursor up again with the new one.
  • Check that Cursor lists tuxedo-code-reviewer among its MCP servers without an error.

Where to go next

  • Access: each access mode in full, with tokens, the signed URL, connected apps and switching between them.
  • Your first Suit: from connecting a server to your Suit's first call.