MCP servers
Add a custom MCP server so the assistant can use its actions, or connect Claude, ChatGPT and other AI apps to AgentWorks.
MCP (Model Context Protocol) is a standard way for AI apps to talk to other systems. AgentWorks supports it in two directions: you can add other systems' MCP servers to AgentWorks, and you can connect other AI apps to AgentWorks.
Add a custom MCP server
A custom server adds its own actions to your chats and agents, next to the actions of your connected apps.
Open the MCP servers tab
Go to Actions and open the MCP servers tab. Under Custom servers (MCP) choose Manage servers.
Pick or add a server
Choose Browse directory and pick a server (Click to add), or choose Add MCP server to add your own.
Fill in the details
Enter a Name and the Server URL (usually ending in /mcp or /sse). Under How does this server authenticate? choose No auth, OAuth, Bearer token or API key, and paste the token or key. AgentWorks works out the connection type itself. For OAuth, choose Connect after adding the server and sign in.
Add and discover actions
Choose Add. AgentWorks then looks up the server's actions on its own. Use Health check to test the connection later, and Refresh actions if the server changes.
Choose which actions to enable
Under Manage enabled actions select the actions you want. There is a cap on how many you can enable per server, and the dialog shows it. Choose Save selection.
Each enabled action is governed like any other action: actions that change something ask for approval first, and chats label them External · via the server's name.
Use a server in chat
Open Capabilities in the message box. Under MCP servers you can switch each server on or off for this chat, see its actions, and choose Manage MCP servers. Servers can also offer their own interactive screens in chat if you switch Interactive apps on for that server; they run in a locked-down sandbox and follow the same approval rules.
Each server shows its status (Connected, Pending, Error or Disconnected) and its action count. To remove it, choose Remove.
MCP servers count towards your plan's connection limit, and Free allows one custom server. See Connect apps.
Use AgentWorks from another AI app
AgentWorks has its own MCP server, so Claude, ChatGPT, Claude Code or another MCP client can work with your AgentWorks account: agents, workflows, runs, knowledge, board tasks and more.
Copy the address
Go to Settings and open AgentWorks MCP. Under Connect Claude, ChatGPT or another AI app, choose Copy URL.
Add a custom connector in the AI app
In the AI app, add a custom connector and paste the address. In Claude: Settings, Connectors, Add custom connector.
Sign in and choose permissions
You are taken to AgentWorks to sign in. The page What may this app do? lists the permissions grouped by area: Agents, Workflows, Runs, Knowledge, Board tasks, Rules, Skills, Memory, Notifications, Approvals and Account. Read permissions start on and permissions that change things start off. Switch on what the app may do and choose Allow.
The connection then appears under Your connections with its Created, Expires and Last used details. Choose Revoke to cut access at once; the app loses access immediately and you would need a new connection to restore it. There is a limit on how many connections can be active at a time, and the page shows it.
Create a token instead
If an app or script cannot sign in through the address, choose Create a token under the advanced option. Name the connection, choose permissions and an expiry, and choose Create connection. The token is shown only once, together with a snippet you can paste into the client's configuration. AgentWorks stores only a hash of the token.
Start with narrow permissions: you can always create another connection with more access later. Permissions marked Sensitive give broad access to personal data, money or actions.
On the Free plan an MCP connection can only read. Writing, running and deciding approvals need Business.
Who can choose a server's tools
A workspace admin chooses which of a server's tools are on for the whole workspace. The member who added a server can also choose its tools, but then only for their own use: those tools appear in their chats and runs, not in anyone else's. When an admin later saves the selection, the server is shared with the whole workspace again.