Connections are the MCP servers your organization uses, such as GitHub, Linear or Atlassian. An org admin picks which servers are on the list. Each member then signs in to each server with their own account. When an agent runs a Command Center task for you, it calls those servers through Catalio with your sign-in, not anyone else’s.
This page covers servers Catalio connects out to. To connect your own AI client (Claude Code, Claude Desktop, Cursor) to Catalio, see MCP Authentication.
Where to find it
Open Settings → Connections. The page has two tabs.
- Yours lists the servers your organization has added. Catalio’s own connector is always first and is always connected.
- Discover lists servers you can add, with their URLs filled in for you.
Every member can open the page. Only org admins can add, edit or remove servers.
Add a server (org admins)
- Open Settings → Connections → Discover.
- Find the server and click Add. The form opens with the server’s URL already filled in.
- Save it. The server now appears on everyone’s Yours tab.
A server that isn’t in the catalog can be added from the same form with its MCP URL.
Adding a server doesn’t sign anyone in. Each member still connects with their own account.
Sign in to a server (every member)
On the Yours tab, each server shows your own state.
| State | What it means | What to do |
|---|---|---|
| Connected | Catalio holds a valid sign-in for you | Nothing |
| Not connected | You haven’t signed in yet | Click Connect |
| Sign-in expired | The server stopped accepting your sign-in | Click Reconnect |
| Coming soon | Catalio can’t sign in to this server yet | Nothing yet |
Connect sends you to the server’s own sign-in page. Approve access there and you land back on Connections with the server marked Connected.
Disconnect removes only your sign-in. Other members stay connected, and the server stays on the organization’s list.
Your sign-in is also removed when an admin removes the server or changes its URL, or when you leave the organization.
GitHub
Command Center agents use the GitHub connection to read your repositories and open pull requests as you.
- Install the Catalio GitHub App on the repositories you want agents to work in, if you haven’t already. See GitHub Integration.
- An org admin adds GitHub from the Discover tab. Its URL is
https://api.githubcopilot.com/mcp/. - Each member who starts Command Center tasks clicks Connect on the GitHub row.
- GitHub asks you to authorize Catalio App, the same app your organization installed. Approve it.
There’s nothing else to create on GitHub.
How it relates to the GitHub integration
Both use the Catalio GitHub App, in two different ways.
| GitHub integration | GitHub connection | |
|---|---|---|
| Set up in | Settings → Integrations → GitHub | Settings → Connections |
| Signs in as | Your organization, once, by installing the App | Each member, with their own GitHub account |
| Used for | Cloning repositories into your sandbox, issue sync, PR review | Agents reading code and opening pull requests as you |
Your GitHub connection only reaches repositories where the Catalio App is installed, and only those you can access yourself on GitHub. If you’re connected but an agent can’t see a repository, add that repository to the App’s installation.
How agents use your connections
When you start a Command Center task, the agent in your sandbox gets one connection to Catalio. Through it, the agent sees the tools of every server you’re signed in to, named <server>__<tool>. Each call goes through Catalio, which adds your sign-in and checks that the agent is allowed to make it. Your tokens never go into the sandbox.
Catalio records every time it uses your sign-in for an agent, along with which task and agent used it.
Servers you haven’t signed in to don’t appear to the agent. If a task needs GitHub and you’re not connected, connect first, then start the task again.
Troubleshooting
“Sign-in was cancelled.” You declined on the provider’s page. Click Connect again.
“That sign-in didn’t match or has expired. Try again.” The sign-in took too long, or it was started in another tab or as another user. Start it again from Connections.
“This server doesn’t support sign-in from Catalio yet. Ask an org admin.” The server needs an OAuth app that Catalio doesn’t have yet. These servers also show Coming soon.
“Couldn’t find how to sign in to this server. Ask an org admin to check its URL.” Catalio couldn’t find the server’s sign-in details at that URL. An admin should check the URL in the server’s settings.
“This server’s URL changed while you were signing in. Try again.” An admin edited the server during your sign-in. Connect again.
A server shows Sign-in expired. The server rejected your token and Catalio couldn’t refresh it. Click Reconnect.
