MCP Servers
MCP servers let you connect external tool providers to your team. Once a server is connected, its tools, prompts, and skills become available to the agents in your team. MCP servers are configured per team, from the team Configurations page.
What you can do
- Add an MCP server with a name and URL
- Enable or disable a server without removing it
- Load its catalog of tools, prompts, and skills
- Choose how the server is authenticated (service token and/or per-user credential)
- Enable specific tools from the server on each agent
Authentication
A server can require authentication in two independent ways. They serve different purposes, so it helps to set the right one.
| Setting | Purpose | Who provides it |
|---|---|---|
| Service authentication (token) | Loads the server's tool catalog and is sent as the shared team credential when agents call the server | An admin, once, in the server settings |
| Per-user credential (runtime) | Each user acts with their own identity at runtime | Each user, when prompted in chat |
Service authentication
This is the team-level service token. It is what lets us fetch the list of available tools from servers that require authentication, and it is sent as the shared team credential when agents call the server. It is not a personal credential.
Per-user credential
When "Require each user to provide their own credential (runtime)" is enabled, every user adds their own credential the first time an agent needs it. They are prompted directly in chat, and the credential is stored securely and used only for their own requests.
If the per-user credential is not required, every user's requests use the shared service token, so all users act with the same identity. Enable the per-user credential when the server returns data that is specific to each user (for example a personal workspace or mailbox).
Catalog status
Each server shows a status for its catalog:
| Status | Meaning |
|---|---|
| Not fetched | The catalog has not been loaded yet |
| OK | Tools, prompts, and skills were loaded successfully |
| Failed | The last attempt to load the catalog failed |
Use the refresh action to reload the catalog after you change the server or its token. If a server requires authentication and no service token is set, add a token first so the catalog can be loaded.
Using a server's tools on an agent
After a server's catalog is loaded, open an agent's Tools area to enable the specific tools, prompts, and skills you want that agent to use. Only the capabilities you enable are available to the agent.
Connect a server once at team level, then enable just the tools you need on each agent. Different agents can use different subsets of the same server.