Connect your AI assistant with MCP

You can connect your own AI assistant, such as Claude or ChatGPT, to one of your teams through MCP, a standard way for assistants to use an application. The assistant then works only in that team, with your role and permissions there and nothing more: what you cannot do in that team, it cannot do either, and it never sees your other teams.

Switch on MCP for the team

MCP is a team add-on, and it starts switched off. Someone who manages the team's plan opens Add-ons in the team menu and clicks Activate on MCP. Clicking Deactivate stops every assistant connected to the team at once; the tokens are kept and work again when MCP is switched back on.

Create a token

Creating tokens needs the Manage Mcp Tokens or the Edit Settings permission in the team. If you do not see the Integrations tab in the team's Settings with MCP switched on, ask the team's owner for one of them.

1. Open Settings in the team menu and choose Integrations.
2. Copy the MCP server URL into your assistant's settings, where it asks for a remote MCP server.
3. Write a Token name that tells you where you use it, such as Claude Desktop, and click Create token.
4. Copy the token from the yellow box and paste it into your assistant, where it asks for a bearer token. The token is shown only once: after you click Done only its name stays. If you lose it, revoke it and create another.

Create one token per assistant or device, so you can stop one without touching the others. A token works only in the team where you created it; to use the assistant in another team, create a token there.

What the assistant can do

It can describe the team and your role in it, and, when your role allows it:

• list the members and the roles, invite a person by email, remove a member and change a member's role, with the same rules as the members screen;
• list, cancel and resend invitations, change the team's name and description, manage its roles and switch its add-ons on or off, without ever seeing a price or buying anything;
• work on the team's Files: list folders and files, create a folder, rename a file and delete one, with Manage Media. It cannot upload files;
• list, read, reply to and close the team's Tickets: your own, and other members' with View team tickets. Replies are written as you;
• list the team's data exports and imports and start an export, with Edit Settings. The file arrives as the usual notification, and importing stays in Import and export data.

Deleting a file or closing a ticket only happens when the assistant confirms it in a second call. When you are not allowed to do something, the assistant is told which permission is missing and nothing changes. The product may add more of its own.

If you also administer the product, it can list its announcements. The product's figures, such as how many users and teams there are and which teams have been active, and the activity log as the admin panel shows it, are not reached through a team's token: a superadministrator opens MCP in the admin panel's menu, copies the MCP server URL shown there into the assistant and creates a token on that screen. Those figures carry no emails, and a team counts as active when one of its members has signed in.

Whatever it changes is recorded with you as the author, and the history of that record shows a Via MCP tag with the name of the token it used.

Revoke a token

In Integrations, click Revoke next to the token and confirm. It stops working right away; the other tokens keep working. The list shows every token of the team with who created it, and anyone who reaches Integrations can revoke any of them.

When the assistant cannot connect