Get started · 02
Your first Suit
Sign in, connect a server, tailor a Suit and add it to your client, and your agent can make its first call through Tuxedo. The Suits page counts these steps off for you as “Your first fitting”. This page follows the same steps and links each one to the page that covers it in depth.
Sign in
Signing in for the first time creates your account. There's no separate sign-up, and Tuxedo has no passwords. The sign-in page offers:
- Continue with GitHub
- Continue with Google
- Email me a sign-in code, which emails you a 6-digit code to enter
Every way of signing in that uses the same email address opens the same account. Once you're in, Tuxedo opens your Suits, or the page you were on your way to.
Your first fitting
Above your Suits, a checklist called “Your first fitting” lists the steps in order and counts how many are done, such as “1 of 4 done”. Each step ticks off by itself, from what is in your account, never from a click:
- Connect a server ticks once you have a Connection.
- Tailor a Suit ticks once you have a Suit.
- Dress a client ticks once one of your Suits has a token or a connected app, or its access mode is Signed URL.
- First call received ticks once one of your Suits has heard from a client.
The next step is highlighted and links to where you take it: “Add connection →”, “Create Suit →” or “Open setup →”. A step that's done shows what did it, such as the names of your Connections or of your Suit. A signed URL works by itself, so a Suit you create with the Signed URL access mode ticks “Dress a client” straight away.
Dismiss the checklist with the × in its corner and it's gone for good, on every device. It also closes once every step is done, and stays closed even if you undo a step later.
Connect a server
A Connection is one of your accounts on a remote MCP server. You connect it once and wear it in any Suit.
“Add connection →” opens the Connections page at “Connect a server”. Choose Connect on a server from the catalog, such as GitHub, Notion or Linear, or Connect by URL on Custom server for another server that uses HTTPS and is on the public internet.
Give the Connection a name and a handle. Agents see each of its tools as handle__tool, and the handle can't change later. Then connect it: depending on the server, you sign in on its own page, give Tuxedo a token, or neither, and Tuxedo loads its tools. Connect a server and Custom servers go through it in full.
Tailor a Suit
A Suit is one MCP endpoint, tailored to an agent's role: only the Connections and tools it needs. “Create Suit →” in the checklist, or Create Suit on the Suits page, opens “Tailor a Suit”:
- Name. Agents see it, so name the Suit after who wears it, such as “Code reviewer”.
- Description, optional. Agents read it, so say what the Suit is for.
- Access mode. How clients authenticate to the Suit. It starts on OAuth, and you can change it later on the Suit's Access page.
- Connections. The Suit includes the tools of the Connections you choose. You can create it with none and add them later.
The Connections you choose start with all their tools on. You can switch any tool on or off on the Suit's Tools page.
Create Suit takes you to the new Suit's overview. Tailor a Suit, Tools and Access cover what you can change there.
Dress a client
On the Suit's overview, the “Dress a client” card shows how to add the Suit to the client your agent runs in: Claude, Codex, Cursor and Grok. Pick the client and you'll see only its steps, and Tuxedo remembers your pick in this browser.
An example Suit
The steps depend on the Suit's access mode. For Code reviewer in Claude, they are:
- OAuth: “Add Code reviewer to Claude”, “Sign in and approve it” then “Check it fits”.
- Bearer token: “Put a token in your shell”, “Add Code reviewer to Claude” then “Check it fits”.
- Signed URL: “Add Code reviewer to Claude” then “Check it fits”.
A new Suit starts on OAuth. For Code reviewer in Claude, its steps are these:
-
1
Add Code reviewer to Claude
terminalclaude mcp add --transport http --scope user tuxedo-code-reviewer 'https://tuxedo.bot/mcp/example0000000000000'
-
2
Sign in and approve it
Then sign in from a terminal, or run /mcp in Claude Code, choose tuxedo-code-reviewer and Authenticate. Approve it in Tuxedo when your browser opens.
terminalclaude mcp login tuxedo-code-reviewer
-
3
Check it fits
Restart Claude and ask it to list its tools. This turns green as soon as Code reviewer hears from it.
Once you approve the client on Tuxedo's consent screen, it's one of the Suit's connected apps, which ticks “Dress a client”.
Clients know the example Suit as tuxedo-code-reviewer, from the name it was created with. Renaming a Suit keeps that name.
Copy setup as prompt copies the same steps as instructions to paste to an agent, so it can do the setup for you.
Each client has its own page: Claude, Codex, Cursor and Grok.
Check it fits
The last step, “Check it fits”, listens for your client and tells you what to do, as the last step above does. With Signed URL, it asks for more: “Restart Claude and ask it to use one of Code reviewer's tools. This turns green as soon as Code reviewer hears from it.” A signed URL doesn't say which client uses it, so listing the tools isn't enough.
While it listens, it says “Waiting for a call from Claude…”. Once the Suit hears from a client after you opened the page, the step turns green and links to the Suit's calls with “See Activity →”. It knows clients only by the names of their tokens and apps, so anything not named for another client counts.
On a Suit nothing had reached before, the green holds for a moment and then the steps fold away: the Connections move up, and the Clients card opens beside them, with Dress a client to set up another. The card lists the clients the Suit can tell by name. A call that doesn't say which client made it, such as one over a signed URL or with a token named Laptop, still folds the steps away. If no client can be told by name, the card says “No client named yet”.
It listens for 10 minutes. After that it says “No call from Claude yet”, and Listen again listens for another 10 minutes. Picking another client starts listening afresh. Troubleshoot shows tips for the Suit's access mode.
First call received
Once any of your Suits hears from a client, “First call received” ticks. With a token or a connected app, any request counts, even listing the tools. With Signed URL, the client has to use the Suit, such as by calling one of its tools. The Suit's tool calls show in Activity, and with every step done, “Your first fitting” closes.
Where to go next
- Tools: decide what the agent may do, tool by tool.
- Access: tokens, signed URLs and connected apps, and how to cut one off.
- Activity: the tool calls your agents make through your Suits.
- How Tuxedo works: what happens between your agent, a Suit and your servers.