Permissions

MCP Client defines two levels of permission. Both are flagged as security sensitive in the permissions UI, so grant them only to trusted roles.

Permission	Grants
Administer MCP Client (administer mcp_client)	Create, edit and delete MCP server configurations, and execute every tool of every server.
Use the tools of the Server MCP server (use mcp_client server <id> tools)	Execute the enabled tools of one server. One permission exists per configured server.

Granting access to a single server

1. Configure the server as described in Configuration.
2. Navigate to Administration » People » Permissions (/admin/people/permissions).
3. In the MCP Client section, check Use the tools of the Server MCP server for the role that runs AI agents against that server.
4. Save the permissions.

The permission disappears when the server is deleted, and the role configuration is cleaned up with it.

Which permission to use

• Site builders and developers who configure servers need Administer MCP Client.
• Roles that only run AI agents need the per-server permission for the servers they use. Keep the admin permission away from these roles: it also grants execution of every tool and the ability to point the site to a different server.

Upgrading from earlier releases

Earlier releases used a single administer mcp_server permission and tool execution was effectively limited to the super user. The update hook moves every role that held administer mcp_server to administer mcp_client.

Per-server permissions are never granted automatically. After running drush updb, grant them to the roles that need tool access.