Suits · 01
Tailor a Suit
Each Suit is one MCP endpoint, tailored to an agent's role: only the Connections and tools it needs. This page covers creating a Suit, choosing the Connections it wears, and looking after it from its overview.
The Suits page
The Suits page lists your Suits as cards, in order of name. Each card shows:
- its name, which opens the Suit, and its description, or “Add a description” when it has none
- its Connections, as up to five logos and how many more, or “No Connections yet”. Hover over, focus or tap a logo for its Connection's name, or the count for the rest.
- how many of its tools are on, such as “4 of 12 tools on”
- its access mode: OAuth, Token or Signed URL
- how long ago its latest call in Activity came, or “Waiting for its first call…” when Activity has none
Add a description opens a dialog to write one right there: “Agents read the description, so say what this Suit is for and when to use it.” Save it and the card shows it. You can change it later on the Suit's overview.
When one of a Suit's Connections needs attention, the card says so in place of its last call, with Reconnect or Open to fix it. When a Connection needs you explains why that happens.
A card's ⋯ menu has Copy endpoint URL and View activity, which opens Activity for that Suit. With no Suits yet, the page says An empty wardrobe and offers Create Suit.
In Signed URL mode, Copy endpoint URL copies the secret
Create a Suit
-
1
Choose Create Suit
On the Suits page, choose Create Suit. A dialog, Tailor a Suit, opens with: “Every tool of the Connections you choose starts on. Switch off what the agent doesn't need on its Tools page, any time.”
Tools explains the switches. On Free, once you have 2 Suits, the button offers Pro instead: Free's Suit limit.
-
2
Name it
Name, up to 100 characters: “Agents see the name, so say who wears it, e.g. after the agent's role.” Two of your Suits can have the same name.
Description is optional, up to 500 characters: “Agents read the description, so say what this Suit is for and when to use it.”
-
3
Choose its access mode
“How clients authenticate to the Suit. You can change it later on its Access page.” OAuth is chosen unless you pick another.
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.
Access explains each mode, and what changing it does to your clients.
-
4
Choose its Connections
Tick the Connections this agent needs: “The Suit includes the tools of the Connections you choose.” With none yet, the dialog says No Connections yet: you can create the Suit now and add Connections to it later.
-
5
Create it
Choose Create Suit. Tuxedo says “Created Code reviewer.” and opens the Suit's overview.
The Suit's slug
When you create a Suit, Tuxedo makes a slug from its name: lowercase letters, digits and dashes, cut to 40 characters. If another of your Suits has that slug already, Tuxedo adds a number: code-reviewer-2, then code-reviewer-3. When nothing is left, as with a name of only punctuation, the slug is suit.
The setup on its overview names the Suit by its slug. For a Suit named Code reviewer, the server name is tuxedo-code-reviewer, and in Bearer token mode the token is read from TUXEDO_CODE_REVIEWER_TOKEN, as the setup on its overview shows:
export TUXEDO_CODE_REVIEWER_TOKEN=txd_…
The slug never changes. Rename the Suit to Reviewer, and its server name and token variable still say code-reviewer, so the clients you've set up keep working. Its endpoint URL stays the same too: it uses an id of its own, not the name.
The overview
Opening a Suit shows its overview. Four figures sit at the top:
- Calls · 24h: the tool calls Activity recorded for the Suit in the last 24 hours.
- Errors · 24h: how many of those didn't end OK, and what share of them that is. Every status but OK counts, not only a server's errors: in Activity's words, Error, Refused, Timed out, Needs sign-in and Weekly limit.
- Last call: how long ago its latest call in Activity came, or “No calls yet” when Activity has none.
- Tools on: how many of its tools are on, of how many.
Both last-call labels come from Activity, so once it no longer keeps any of a Suit's calls, the Suit shows “No calls yet” here and “Waiting for its first call…” on its card. Activity says how long it keeps them.
A request Tuxedo turns away before it reaches the Suit, for a wrong credential or too many in a minute, isn't in Activity, so these figures don't count it.
Below them, until anything has reached the Suit, Dress a client gives the steps to add the Suit to the client your agent runs in. Your first Suit walks through them. After that, the Connections lead the page, and the Clients card beside them lists the clients that have reached the Suit by name, with how long ago each last did. Its Dress a client opens the same steps, to set up another.
Choose its Connections
The Connections card lists all your Connections: “Code reviewer wears the tools of the ones you tick.” Each row shows a Connection's name and account, its status beside them when it needs you (such as Needs sign-in), its handle, and how many of its tools are on in the Suit, such as “11 of 12”. For a Connection the Suit includes, that count opens its tools on the Tools tab. The count follows the ticks: a Connection you untick counts none, and one you tick to add counts all its tools, as saving would leave them.
To find one, filter the list by name, handle or account, or show only the Connections the Suit includes, Included, or the ones it doesn't, Not included. Those two go by the Suit as saved, so a row you tick or untick stays in view until you save.
A Connection you add starts with all its tools on, whatever the Suit's new-tool policy.
Ticking or unticking a Connection doesn't save it. Its row says Not saved, and the change waits in the bar at the bottom of the page until you save.
A server you haven't connected yet
Above the list, choose Add a connection. It opens the Connections page, which says “Adding to Code reviewer. You'll go back to Code reviewer when it's connected.” Its connect dialog adds “All its tools start on in Code reviewer.”
Once the Connection is connected and its tools have loaded, Tuxedo adds it to the Suit at once, without waiting for the bar, and takes you back: “GitHub added to Code reviewer.” If its tools don't load, it stays out of the Suit and you stay on the Connections page, with the reason. Cancel goes back to the Suit without adding anything. Connect a server covers connecting.
On Free, once you have 10 Connections, Add a connection offers Pro instead. With no Connections at all, the card says “No Connections yet” and offers Add a connection.
Details
The Details card holds the Suit's Name, up to 100 characters, and Description, up to 500: “Agents read the description, so say what this Suit is for and when to use it.”
Saving a new name keeps the slug as it was.
Save your changes
Changes to the Connections and the details wait in one bar at the bottom of the page. It says Unsaved changes and offers Discard and Save changes. It also says what saving will do, such as:
- “Adding DeepWiki turns on all 3 of its tools”: the tools a Connection you add starts with
- “Removing Linear turns off its 4 tools”: how many of its tools are on in the Suit
- “Renaming the Suit keeps its URL”
- “Agents see the new description”, or “Agents no longer see a description” when you clear it
One Save changes applies them all: the Connections and the details save together, or not at all. If a field is wrong, nothing is saved, and the bar says “Fix the fields marked in red to save.” and takes you to the first one. A Suit needs a name.
Saving says “Saved.”, or “Saved. The Suit includes 3 Connections.” when the Connections changed. Discard puts everything back as it was last saved.
Leaving without saving
Leaving the overview discards changes you haven't saved, so Tuxedo usually asks first: Leave without saving? “Your changes to this Suit's Connections and details aren't saved. Leaving the page discards them.” Stay keeps your changes; Leave without saving discards them.
Removing a Connection
Untick a Connection and save to take it out of the Suit. The Connection itself stays, on the Connections page and in your other Suits.
Taking a Connection out forgets its switches
Delete a Suit
Delete Suit is in the Delete this Suit card, under Details. Tuxedo asks first: Delete Code reviewer? “Clients using its endpoint stop working, its connected apps are revoked and its switches are removed. Your Connections stay. This can't be undone.”
What stops:
- its endpoint: clients calling it are turned away
- its tokens, which are deleted with it
- its connected apps, with every sign-in Tuxedo gave them, so they can't renew it
- its tool switches
What stays:
- your Connections, and their place in your other Suits
- its calls in Activity, under Deleted Suit
Tuxedo then says “Deleted Code reviewer.” and takes you back to your Suits.
Free's Suit limit
Free includes 2 Suits. Pro has no limit.
On Free, the top of the Suits page counts yours, such as “1 / 2 Suits”, and the count turns amber at the limit. Pro shows no count.
At the limit, Create Suit opens You've used both Free Suits instead of the form: “Free includes 2 Suits. Go Pro to tailor one for every agent you run, or delete a Suit you no longer wear.” It shows what Pro costs, ₱300 / month or ₱3,000 / year, with Not now and See Pro, which opens the Upgrade page.
Limits stop additions only. If you have more Suits than Free includes, say after Pro ends, every one keeps working, and you can create another once you have fewer than 2. Plans and billing explains the plans.