Connections · 01
Connect a server
A Connection is one of your accounts on a remote MCP server. Connect a server once, and any of your Suits can wear it. Here is how to pick it from the catalog, choose how Tuxedo signs in to it, and give it the handle your agents will see.
The Connections page
Open Connections in Tuxedo. Your Connections come first, then the catalog of servers you can add. With none yet, Add your first connection takes you down to the catalog; once you have one, Add connection at the top does the same.
On Free, the top of the page also counts your Connections against the plan's limit, and the count turns amber once you reach it. See Free's Connection limit.
Find a server
The catalog is headed Connect a server until you have a Connection, and Add more after that. The line under the heading counts the servers it has.
Type in Search servers to narrow it down: it matches a server's name or its one-line summary as you type. If nothing matches, Clear search brings the whole catalog back, and Connect by URL opens the custom server form, to connect it by its URL instead.
Each server has a card with its logo, name and summary, and Docs ↗, which opens the service's own page about its MCP server. A card may also say:
- 2 connected: how many of your Connections are accounts of this service.
- Preview: the service's MCP server is still in preview.
- Not available yet: this Tuxedo can't connect the service yet. The service only signs in with OAuth, through an app this Tuxedo's operator registers with it, and they haven't registered one. The badge says so when you point at it, and the card's button is greyed out.
The card's button reads Connect, or Add account for a service you already use: connecting it again adds another account. The last card, Custom server, connects any remote MCP server by its URL, as Custom servers explains.
Choose how to sign in
Choosing a server opens its connect dialog. How Tuxedo signs in depends on what the server accepts: a token, OAuth, or nothing at all for a public server.
When a server takes both a token and OAuth, the dialog shows them as two cards under Sign in with, one already chosen. When it takes only one, the dialog goes straight to what that one needs. Afterwards, the Connection's page shows how it signs in, under Sign-in. The ways in, where {Service} stands for the service's name:
- Your own token: Tuxedo sends the token you paste with every request to the service's server, so calls run as whatever the token is: your own account, or a service account's.
- Sign in with {Service}: Approve Tuxedo on {Service}'s own sign-in page. There is nothing for you to set up: Tuxedo signs in as this Tuxedo's own app for the service, or registers itself with servers that allow it.
- Your own OAuth app: Register an OAuth app on {Service}, enter its client ID and secret, then approve Tuxedo on {Service}'s own sign-in page. The dialog offers this in place of Sign in with {Service} when the service only accepts OAuth apps registered with it and this Tuxedo hasn't registered one.
The dialog chooses Sign in with {Service} when the server offers it. Otherwise it chooses Your own token when the server takes a token, and otherwise Your own OAuth app, the only way left. When there are two cards, you can choose the other before you connect.
A public server needs no sign-in, so the dialog offers no choice: it says the server is public and that Tuxedo connects without signing in. Its Connection's page shows its sign-in as No auth.
Your own token
The dialog says how to create a token on the service, with a Create a token on {Service} ↗ link to the page where you make one. Paste it under Token. Tuxedo stores it encrypted, sends it with every request in the header the field's hint names, such as Authorization: Bearer …, and checks it by loading the tools. If you paste the token with its prefix, such as Bearer, Tuxedo doesn't add the prefix twice.
If the service refuses the token, Tuxedo saves nothing and keeps the dialog open with the reason. Check that you copied all of it and that it hasn't expired or been revoked.
Your own OAuth app
-
1
Register an OAuth app on the service
The dialog says how, with a Register an OAuth app on {Service} ↗ link to the page where you do it. Give the app this callback URL, which the dialog also shows under Callback URL, with a copy button:
Callback URLhttps://tuxedo.bot/oauth/callback
-
2
Enter its client ID and secret
Fill in Client ID and Client secret. Here in the catalog, both are required. Tuxedo stores the secret encrypted.
-
3
Approve Tuxedo
Continue to {Service} ↗ takes you to the service's own sign-in page. Approve Tuxedo there.
Name and handle
The dialog suggests a Name and a Handle for the Connection. Change either before you connect. The name is what you call the Connection in Tuxedo, and you can rename it later under Details on its page.
The handle starts the name of every tool the Connection brings, handle__tool, which is what your agents see. A handle:
- is at most 24 characters
- starts with a letter
- uses only lowercase letters, digits and dashes
- isn't one you already use for another Connection
Under the fields, a preview shows the tool names agents will see as you type, such as github__<tool>.
The handle never changes
Use this account for is optional. It tells your agents what the account is for, which helps them pick the right one when you connect a service more than once. You can change it later under Details too.
What happens when you connect
The button at the bottom of the dialog depends on how Tuxedo signs in.
- Connect and load tools, for a token or a public server. Tuxedo saves the Connection, loads its tools and opens its page, saying how many tools it loaded. If the tools don't load for a reason other than a refused token, the Connection is saved anyway, and its page says why.
- Continue to {Service} ↗, for OAuth. Tuxedo saves the Connection and sends you to the service's own sign-in page. Approve Tuxedo there, and you come back to the Connection's page once Tuxedo has loaded its tools, or with the reason it couldn't.
GitHub goes one step further: see GitHub organizations and repositories.
Until you approve Tuxedo, an OAuth Connection needs sign-in. If you don't approve it, Tuxedo says so, and the Connection waits in your list with Reconnect to sign in again; When a Connection needs you explains what that means for your Suits. Cancel closes the dialog and saves nothing.
GitHub organizations and repositories
When you connect GitHub with Sign in with GitHub, Tuxedo signs in through this Tuxedo's own GitHub App. Its tools then reach the repositories where the app is installed and your GitHub account has access. Public repositories can be read anyway.
So once a new GitHub Connection is connected and its tools have loaded, Tuxedo takes you on to GitHub's own page for installing the app. Choose your account or an organization (one that has the app already says Configure), then all of its repositories or only some, and save. GitHub brings you back to the Connection, or to the Suit you were adding it to. Leaving GitHub without saving loses nothing: the Connection works already. Reconnecting never takes you there.
The Connection's page shows the same under Organizations and repositories: each account or organization the app is installed on that your account can see, whether the installation covers all its repositories or selected ones, and how many your account can reach through it. Show repositories lists them, a hundred at a time; Manage on GitHub opens the installation's settings on GitHub; Choose organizations and repositories opens GitHub's page again; and Check again reads it afresh.
An installation belongs to the account or organization
More than one account
You can connect a service more than once, such as a work account and a personal one. Choose its card again: it now says Add account.
The suggested name and handle count up, so they don't clash with the ones you have. Your first GitHub Connection is suggested as GitHub, with the handle github; the next as GitHub 2, with github-2; then GitHub 3 and github-3. Tuxedo skips any name or handle you already use.
When you sign in with OAuth, GitHub, Google Calendar and Google Drive can show an account chooser, and Tuxedo asks them to, so you can choose which account to connect.
Give each account a Use this account for note, such as "work repositories". It's what tells your agents which account a task is for.
The account label
Tuxedo tells your accounts of a service apart by each Connection's account label: its name, the account it signed in as, and your note. Agents read it like this:
GitHub · octocat — use for: work
Tuxedo learns which account it signed in as when the service says:
- when you sign in with OAuth, if the service names you, your workspace or both
- each time the tools refresh, for services with a tool that says who you are: Cloudflare, GitHub and Typesense Cloud
It's only a label: Tuxedo never decides what a Connection may do from it. Until Tuxedo knows the account, the label leaves it out and the Connection's page has no Account row.
The account and your note show under each Connection's name in your Connections list, on the Connection's own pages and when you choose a new Suit's Connections. A Suit's overview and Tools page show the account.
When a Suit includes two accounts of one service, the descriptions of their tools start with "From" and the account label, such as From GitHub · octocat — use for: work, and the Suit tells agents to use the account the task is for.
Adding a Connection from a Suit
On a Suit's overview, Add a connection opens the same catalog, set to add the new Connection to that Suit. A banner at the top of the Connections page says which Suit you're adding to and that you'll go back to it once it's connected. Its Cancel takes you back to the Suit without adding anything, and so does the dialog's.
Connect as usual. Once its tools load, Tuxedo adds the Connection to the Suit and takes you back there. All its tools start on in the Suit. For a Suit called Work, the dialog says "All its tools start on in Work."
Signing in with OAuth doesn't lose your place: Tuxedo remembers the Suit while you're on the service's sign-in page.
If connecting doesn't work out, because the service refused your token, you didn't approve Tuxedo or the tools didn't load, nothing is added to the Suit. You stay on the Connections page, still adding to the Suit, with the reason. A Connection that was saved stays in your list, and you can add it to the Suit once it works, as Tailor a Suit explains.
Free's Connection limit
Free includes 10 Connections. Pro has no limit. Once you have as many as Free includes, everything that would add another Connection opens a prompt instead, such as Add connection, a card's Connect or Add account, Connect by URL and a Suit's Add a connection.
The prompt says "You've used all 10 Free Connections" and offers See Pro, which opens the upgrade page, or Not now. If you reach the limit in another tab, connecting tells you so instead of saving. What each plan includes is in Plans and billing.
Limits only stop you adding