MCP
Connect external MCP servers to extend Agent Mode with custom tools and capabilities
The MCP connector lets Agent Mode use tools from external Model Context Protocol (MCP) servers. Admins register MCP servers at the organization level, and individual users connect with their own tokens to access the tools those servers expose.
MCP servers must be added by a workspace admin before users can connect. See Connectors for the two-tier model.
Admin Setup
Adding an MCP Server
Go to Settings → Preferences → Connectors → MCP
Click Add MCP
Fill in the server details:
Connector Name: A unique name to identify this server
URL: The MCP server endpoint (e.g.,
https://mcp.example.com/mcp)Headers: Optional key-value pairs sent with every request to the server
Click Save
The server is now available for users to connect to.
Users can view the server's name, URL, and headers from their manage page, but cannot modify any details set by the admin.
Managing Tool Restrictions
To view and manage tools, you first need to provide an admin token:
Click Manage on an existing MCP server
In the Tool Restrictions section, enter your admin token
Once connected, the full list of available tools appears
The admin token is stored securely and can be updated at any time from the Manage dialog.
Each tool can be set to one of three permission levels:
Automatically
Tool executes without user approval
Needs Approval
User must approve each execution (default)
Deny
Tool is completely blocked
Default Behavior: Sets the permission for all tools that don't have a custom override, and applies automatically to new tools the server adds in the future.
Per-tool override: Click the permission selector on an individual tool to override the default. A reset button appears on customized tools to revert them back to the default.
Use the search field to filter tools by name.
Admin tool restrictions act as the ceiling for user permissions. Users can make their own permissions more restrictive, but never more permissive than what the admin allows. See How Tool Restrictions Work for details.
Disabling MCP Connectors
Admins can disable the MCP connector type at any time from Settings → Preferences → Connectors. When disabled, Agent Mode cannot use any MCP tools, even if users have already connected their tokens. User credentials and tool restriction settings are preserved, not deleted. Once the admin re-enables MCP connectors, all previously configured user connections resume working as before.
Removing an MCP Server
Click Remove on the server in the credentials list. This disconnects all users from the server.
User Setup
Connecting to an MCP Server
Go to Integrations → Connectors → MCP
Browse the list of MCP servers your admin has added
Click Connect on the server you want to use
Enter your personal API token and click Connect
You'll be taken to the server's manage page where you can view its configuration and manage your tool restrictions.
The server's name, URL, and headers are configured by your admin and displayed as read-only. Contact your admin if any details need to change.
Listing Available Tools
The Tool Restrictions section at the bottom of the manage page shows every tool the server exposes, including each tool's name and description. Use the search field to filter the list.
Managing Personal Tool Restrictions
You can set your own tool permissions using the same three levels as the admin, with one key difference, your choices are capped by the admin's restrictions.
Automatically
Tool executes without user approval
Needs Approval
User must approve each execution (default)
Deny
Tool is completely blocked
Default Behavior: Sets your personal default for all tools without a custom override.
Per-tool override: Customize individual tools. A reset button reverts a tool to your personal default.
Tools where the admin has set a more restrictive ceiling show a lock icon with a "Restricted by admin" tooltip. You cannot select a permission more permissive than what the admin allows.
Updating Your Token
Click Update Token on the manage page to replace your personal API token.
Disconnecting
Click the Disconnect button to remove your connection. You can reconnect at any time.
How Tool Restrictions Work
MCP tool restrictions use a least-permissive model with two tiers:
Admin tier: The admin sets org-wide permissions (Automatically, Needs Approval, or Deny) per MCP server. These act as the maximum allowed permission.
User tier: Each user sets personal permissions that can only be equal to or more restrictive than the admin's setting.
The effective permission for any tool is always the most restrictive of the two tiers.
Examples
Automatically
Automatically
Automatically
Automatically
Needs Approval
Needs Approval
Automatically
Deny
Deny
Needs Approval
Automatically
Needs Approval
Needs Approval
Needs Approval
Needs Approval
Needs Approval
Deny
Deny
Deny
Any
Deny, tool is blocked entirely
This means:
If the admin denies a tool, no user can use it.
If the admin sets a tool to Needs Approval, users can keep it at Needs Approval or deny it, but cannot set it to Automatically.
The admin's default permission also applies to new tools the server adds after initial setup.
Troubleshooting
MCP server not listed
Ask a workspace admin to add the server in Settings → Preferences → Connectors → MCP
"Restricted by admin" on a tool
The admin has set a more restrictive permission, contact your admin to change it
Tools not loading
Verify the admin has connected an admin token for the server; the server may also be unreachable
Connection failed
Check that your personal token is valid and the MCP server is accessible
Last updated