Give your operators access to manage the MCP server without giving them general store-settings access.
Operators work in the dashboard's MCP Server section or through the Admin GraphQL API.
The MCP dashboard and Admin API run under a dedicated McpServer permission pair. Grant it to the operators
who manage the AI integration.
| Task | Permission |
|---|---|
| View the tool registry and active grants | ReadMcpServer |
| View call logs and stats | ReadMcpServer |
| Turn a tool on or off | UpdateMcpServer |
| Revoke a grant | UpdateMcpServer |
| Prune expired call logs | UpdateMcpServer |
| Approve an admin consent request | UpdateMcpServer |
ReadMcpServer does not expose captured request or response bodies. Reading a call log's input, output, or
clientIp also requires ReadCustomer.
Approving an admin consent request binds the client to the channel the dashboard was on at the time. The agent then works on that channel only, and its grant and call logs show up on that channel. An operator looking at a different channel cannot see the grant, revoke it, or prune its log rows.
So switch to the channel you want the agent to work on before you approve. A superadmin who wants the agent to cover the whole store approves while on the default channel.
The tool-registry query returns the full registry. It is not filtered per caller, so any holder of
ReadMcpServer sees every tool.
Architecture reviews, custom plugin work, migrations, ongoing support. Get a hand from the team that builds Vendure.