Get started · 01
Introduction
Tuxedo dresses your agents right. You connect your MCP servers to it once, then tailor a Suit for each agent: one MCP endpoint with only the tools its role needs.
What Tuxedo is
Give an agent an MCP server and it gets every tool that server offers, including the ones that change or delete things; give it five servers and it gets five servers' worth. Tuxedo puts a fitting in between. You connect each server to Tuxedo once, as a Connection, and then tailor a Suit for each role an agent plays, such as reviewing code or keeping a project board. The Suit includes only the Connections that role needs, and each of their tools has its own switch in it.
Each Suit is one MCP endpoint, which you add to your client as a remote MCP server; the Suit's overview gives you the steps for your client. From then on, what an agent may do is decided in Tuxedo, not in each client's config file: switch a tool off, and Tuxedo refuses it at once, in every client that wears the Suit.
The words in these docs
- Account. You sign in with GitHub, or with Google or a code sent to your email when this Tuxedo offers them, and every way in that vouches for the same verified address opens the same account. There are no passwords.
- Suit. One MCP endpoint, tailored to an agent's role: the Connections it includes, and which of their tools are on. Its address is
https://tuxedo.bot/mcp/…, ending in an id of its own that stays the same when you rename the Suit. - Connection. One of your accounts on a remote MCP server, such as your GitHub account on GitHub's server. You connect it once, and any of your Suits can include it. To use two accounts of one service, connect each as its own Connection.
- Tool. Something a server lets an agent do, such as searching issues or creating a page. A client lists the tools that are on in a Suit, and its agent calls them; as far as the agent can tell, a tool that is off doesn't exist.
- Handle. The short name you give a Connection, such as
github: lowercase letters, digits and dashes, starting with a letter, at most 24 characters. It never changes once the Connection is made. handle__tool. How a Suit names each tool to clients: the Connection's handle,__and the tool's name on its server, sogithub__search_issuesis the search_issues tool of the Connection with the handle github. That keeps apart two servers' tools of the same name, and two accounts of one service.- Client. The app your agent runs in. A Suit's overview has the setup for Claude, Codex, Cursor and Grok, each in every access mode. A client adds the Suit as an MCP server, lists its tools and calls them.
- Access mode. How clients prove they may use a Suit: OAuth, Bearer token or Signed URL. Each Suit has one, and accepts only that. A new Suit starts in OAuth, unless you choose another when you create it, and you can switch it on the Suit's Access page. Access compares them.
How a tool call travels
An agent decides to call a tool, say github__search_issues. Its client sends the call to the Suit's endpoint, with the credential the Suit's access mode asks for. Tuxedo checks the credential, then checks that the tool is on in that Suit; if it isn't, the call is refused as if the tool didn't exist. Otherwise Tuxedo sends the call on to the server of the Connection with that handle, signed in as you with the Connection's credentials (or without signing in, for a public server), with the arguments exactly as the client sent them. The server's result goes back to the client as the server sent it, with only the protocol details Tuxedo's own server puts on every result: the result type, any caching hints, and Tuxedo's own server details in place of the server's. If the call can't get through, or the server asks for more input before it answers, which Tuxedo doesn't support yet, the agent gets Tuxedo's own message saying why instead.
Activity records the call: the tool and its Connection, the Suit, how the call ended and how long it took, and as much about the caller as its credential says. A call with a token carries the name you gave the token, and a call from an app you approved carries the name the app gave itself; a call with a signed URL carries no name, so Activity can't tell the clients that share it apart.
On Free, each call Tuxedo sends on counts toward 2,000 tool calls a week. Plans and billing explains what counts.
Tuxedo never stores a call's arguments or results
Where to go next
- Your first Suit: connect one server, tailor a Suit and add it to your client.
- How Tuxedo works: what happens along the way, in more detail.
- Connect a server and Tailor a Suit: the two things every Suit starts from.
- The page for your client: Claude, Codex, Cursor or Grok.