Docs Access

Suits · 03

Access

Every Suit has one access mode. It decides how clients prove they may wear the Suit, and the Suit accepts nothing else.

Access modes

You choose a Suit's access mode when you tailor it, under Access mode, and you can change it any time on the Suit's Access tab. A new Suit uses OAuth unless you pick another. The mode shows beside the Suit's name, and on its card in Suits.

  • 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.
  • Bearer token. Clients send a token you create for each of them in a header. You can revoke each token on its own.
  • 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.

The Suit's overview sets up Claude, Codex, Cursor and Grok in every mode, under Dress a client.

Switching modes

A Suit accepts only its current mode, so switching stops clients using the old one. A Suit that now uses a signed URL refuses its old tokens, and a Suit back on tokens refuses its old signed URL.

To switch, choose the new mode under Access mode on the Access tab, then Switch to {mode}. Tuxedo asks first, and tells you what you lose. Switching retires the credentials of the mode you leave, for good:

  • Leaving OAuth revokes every app for good: even if you switch back, none of them can sign in to the Suit again.
  • Leaving Bearer token deletes every token. Clients using them stop reaching the Suit at once.
  • Leaving Signed URL kills the URL. If you switch back later, the Suit gets a new one, so you set your clients up again.

Switching can't be undone

Even if you switch straight back, the old tokens, URL or apps stay dead.

OAuth

In OAuth mode there is no secret to copy. You add the Suit's URL to a client, the client signs in to Tuxedo by itself, and you approve it.

  1. Add the Suit's URL to the client

    In OAuth mode it's the plain address of the Suit. The overview's Dress a client has the setup for each client.

  2. Sign in from the client

    Each client has its own way to start, and the overview shows the step for yours. For Claude and a Suit called Code reviewer, it's this command:

    terminal
    claude mcp login tuxedo-code-reviewer

    Tuxedo opens in your browser. If you aren't signed in, you sign in first and come back to the request.

  3. Approve it

    Tuxedo asks “Allow {client} to wear {Suit}?” Choose Approve, or Deny to send the client away with nothing.

Under the question, Tuxedo says who you're signed in as. Not you? Switch account signs you out so you can sign in as someone else, then brings you back to the same request. Below that, the card “What {client} can do” asks you to approve only if you just added this Suit to the client yourself, and lists:

  • The tools switched on in this Suit, and only those: switch one off and the client can't call it any more.
  • As you: its calls use your Connections and show in your Activity.
  • Until you revoke it: you can revoke it any time on the Suit's Access page.

Under the card, Authorizing will redirect to names where approving sends you back.

Only the Suit's owner can approve. Signed in as anyone else, the screen says “{client} isn't asking for one of your Suits” and offers only Deny. An app you approve reaches only the Suit you approved it for, never your other Suits.

The apps you approved are listed under Connected apps on the Access tab, each by the name it gave itself, with where it returns to and when it last reached the Suit. A client you didn't approve isn't listed.

To revoke an app, open its ⋯ menu, choose Revoke, then Revoke app. It stops reaching the Suit at once, and for good: that app can't sign in to the Suit again.

A client's sign-in lasts 1 hour. It can renew it with a refresh token, which lasts 30 days and is replaced at each renewal; a client that goes 30 days without renewing has to sign in again, and you approve it again. The old refresh token stops working once the client uses the new one, so a client that quits halfway through a renewal can renew again instead of signing in again.

Tokens

In Bearer token mode, clients send one of the Suit's tokens in a header: Authorization: Bearer txd_…. Give each client its own token, so you can revoke one without the others. A Suit can have up to 10 tokens.

  1. Create a token

    On the Access tab, choose Create token and name the token after the client that uses it, such as “Claude Code on my laptop”. The name is how you tell your tokens apart, and Activity shows it as the client of each call the token makes.

  2. Put the token in your shell

    Tuxedo shows the new token once, as a line for your shell profile, ~/.zshrc. For a Suit called Code reviewer, it reads:

    ~/.zshrc
    export TUXEDO_CODE_REVIEWER_TOKEN=txd_…
    This is the only time Tuxedo shows this token. If you lose it, create another and revoke this one.
  3. Set up the client

    Next: set up a client takes you to the Suit's overview, where Dress a client has the client's setup. Every snippet reads the token from the variable, so it never sits in a client's config file.

The Access tab names the variable for its Suit: for a Suit called Code reviewer, it's TUXEDO_CODE_REVIEWER_TOKEN. It comes from the name you first gave the Suit, and renaming the Suit doesn't change it. A client reads the token when it starts: after you edit ~/.zshrc, open a new terminal and restart the client from there.

A token is txd_ followed by 40 random letters and digits. Tuxedo keeps only a hash of it, and its first few characters to show you which one it is, so it can never show you the token again.

The Access tab lists each token by its name and its first few characters, with when a client last used it.

To revoke a token, open its ⋯ menu, choose Revoke, then Revoke token. Revoking deletes the token at once: clients using it stop reaching the Suit, and it can't be undone.

Once the Suit has 10 tokens, Create token is off and the page says Token limit reached: “This Suit has 10 tokens, the most a Suit can have. Revoke one to create another.”

Signed URL

In Signed URL mode, the Suit has one secret URL that works by itself: a client needs nothing else to reach the Suit.

Anyone who has this URL can use the Suit, so treat it like a password.

It's the Suit's address with a version and a signature added, https://tuxedo.bot/mcp/…?v=…&signature=…, and you'll find it in more than one place:

  • on the Access tab, under Signed URL
  • at the top of every page of the Suit, where Copy copies it
  • in the Suit's ⋯ menu in Suits, where Copy endpoint URL copies the signed URL in this mode, not the bare address
  • in the setup snippets on the Suit's overview, so keep them out of shared or committed files

If it leaks, rotate it. Rotate URL asks first, then gives the Suit a new URL and stops the old one at once. Give your clients the new URL from the Access tab.

A signed URL doesn't say which client uses it, so Activity can't tell you which client made a call.

When a client is refused

A request without a credential the Suit accepts gets HTTP 401, with a JSON-RPC error saying how to get in for the Suit's mode:

  • OAuth: Unauthorized: sign in to Tuxedo to use this Suit. MCP clients start signing in from this response, and the Suit's owner approves the client in Tuxedo.
  • Bearer token: Unauthorized: send one of this Suit's tokens as "Authorization: Bearer txd_…". Its owner creates them on the Suit's Access page in Tuxedo.
  • Signed URL: Unauthorized: connect with this Suit's signed URL. Its owner copies it from the Suit's Access page in Tuxedo.

An address that matches no Suit gets the Bearer token message. The response's WWW-Authenticate header reads Bearer realm="tuxedo". It adds error="invalid_token" when the request sent a token that didn't let it in, and in OAuth mode it names where the client starts signing in.

Each token, connected app and signed URL can make 120 requests a minute; past that, requests get HTTP 429.

Requests refused this way, with a 401 or a 429, don't show in Activity. It records the tool calls that get past these checks.