Guide // Integrations
How to connect an external tool through MCP
You'll have an outside service connected over MCP, tested, and limited to the workers and tools you choose.
- For
- Workspace owners who set up AI Workers
- Time
- About 10 min
- Uses
- MCP servers · Logins & keys · Confirmation before changes
Before you start
- Workspace owner: only owners can open Tools & connections
- The service's remote MCP server address, starting with https://
- A key for the server, if it needs one
Steps
Save the key first, if needed
Open AI Workers › Logins & keys, click Add login or key, pick API token (or OAuth client (client id and secret)), list the server's site under Sites, choose The whole workspace and click Save. The secret is write-only and never reaches the workers.
In the user guideAdd the MCP server
Open AI Workers › Tools & connections and, under MCP servers, click Add MCP server. Paste the Address, which usually ends in /mcp.
In the user guideFill in the fields
Keep the Name short and lowercase, pick the Key from Logins & keys or keep None: the server needs no key, and tick the Workers who may use it (none ticked means every worker). Choose In chat and/or In computer runs.
In the user guideKeep Ask before changing things on
With Ask before changing things, tools that change data run in chat only after the person's explicit yes, and stay off in computer runs. Keep it on for any server that can change data.
In the user guideAdd and test
Click Add and test. The server gets its own row with its tools listed; click Test later to check the connection and refresh the tools.
In the user guideSet the per-tool switches
Under Tools, switch off On to hide a tool from the workers, and switch Changes things off for tools that only read, so they run without asking.
In the user guide