Overview
Coworker lets you connect any remote MCP (Model Context Protocol) server directly from your workspace settings — no manual setup through your admin or ops team required. Once connected, the MCP server's tools are available to you in chats and agents, called live when needed.
Note: Custom MCP connections are tool-level integrations only. Data from MCP servers is not ingested into Coworker's organizational memory (OM2).
Before you start
Workspace admins can add MCP servers for everyone in the workspace, or personal servers for themselves.
Members can add personal MCP servers only if a workspace admin has enabled this in Source Settings. If you don't see the option to add a server, contact your admin.
How to connect a custom MCP server
Go to Settings → Data Sources and click the Custom MCP tab.
Click Add.
Paste your MCP server URL. Coworker will automatically detect the server and pre-fill the recommended authentication method and server name.
If the URL points to a retired endpoint (e.g.
/sse), Coworker will suggest the correct working URL.
Choose who can access this server:
Everyone in the workspace — available to all members (admins only)
Only me — personal server, visible only to you
Select your authentication method. Coworker defaults to OAuth with auto-registration (DCR), which works for most servers — you just paste the URL and connect. Other options:
OAuth with your own client — enter your client ID and secret (used for providers like GitHub, Box, or HubSpot)
API token — paste your token directly
None — for servers that require no authentication
Click Add. If the server uses OAuth, you'll be prompted to Connect your account — follow the sign-in flow to authorize Coworker.
Testing your connection
After adding a server, click Test from the Custom MCP tab to verify the connection.
The test result shows:
Whether the connection succeeded
A plain-language description of any error and how to fix it
The tools available from the server (including any that were repaired or skipped)
Suggested fixes like switching to a correct URL or switching to OAuth, with one-click actions
If the server requires you to sign in first, the test result will include a Connect button to complete authorization.
Using custom MCP tools in chats and agents
Once connected, tools from your MCP server are automatically available in Coworker chats. In the Agent Builder, you can explicitly include custom MCP servers as data sources for agents you create.
Personal MCP servers are labeled "Only works when you run it" in the agent builder — if you share an agent that uses your personal MCP server, other users will see a note that the tool isn't available for them.
Managing existing connections
From the Custom MCP tab in Settings → Data Sources, you can:
Edit a server's name, URL, or authentication settings
Test an existing connection
Remove a server you no longer need
Workspace admins can also enable or disable the ability for members to add their own personal MCP servers via the "Allow members to add their own MCP servers" toggle in Source Settings. Disabling this setting pauses any existing personal MCP servers — their tools will no longer appear in chats or agents.
Troubleshooting
"I don't see the option to add a server" — Your workspace admin may not have enabled personal MCP connections. Reach out to your admin to request access.
Connection test failed — Review the error message in the test result for a specific fix. Common issues include incorrect URLs, expired credentials, or servers that require OAuth instead of API keys.
Tools aren't appearing in a chat — Ensure the connection test passes and the server is still active. If the server requires OAuth, you may need to reconnect your account.
Shared agent says a tool isn't available — The agent likely uses a personal MCP server belonging to another user. Personal MCP tools only work for the person who connected them.