Set up user and automation access for the MCP server
- Updated: 2026/02/25
Use to set up user and automation access for the MCP (Model Context Protocol) server in the Automation Anywhere Control Room.
- License requirement: Assign an Attended Bot Runner license to the user.
- Device connection
- The Attended Bot Runner user must be connected to a registered local device in the Automation Anywhere Control Room. Check that your bot configuration is correct and the bot can run from the Control Room. See Create your first bot.
- Device registration must be completed and active.
- Required permissions
- AI permissions:
- View Agent Connections: View inbound and outbound tools and connections
- Manage Agent Connections: Configure and manage inbound and outbound tools and connections
- API permissions: Generate API Key. See Generate API key.
- Bot permissions:
- View my bots
- Run my bots
- Ensure the required bots are assigned to the user's role (RBAC)
- AI permissions:
Before using MCP, validate the following directly in the Automation Anywhere Control Room:
- API Tasks:
- Device registration permission is enabled. The system-created role named AAE_API Task Runner includes this device permission, and this role is automatically assigned to the system-created user: apitaskrunner. See Run-as-user for API Task (apitaskrunner).
- Required AAE_Basic permissions are enabled.
- To run a process from the MCP client: Check that your process configuration is correct and the process can run from the Control Room. See the following:
- To run an API Task from the MCP client: Check that your API Task configuration is correct and the API Task can run from the Control Room. See
The following provides a sample configuration for the mcp.json for IDEs such as VS Code.
"my-aa-mcp-server": {
"url": "https://<your-control-room-url>/mcp",
"headers": {
"X-AUTH": "API_KEY=<api-key-for-user>;USER_NAME=<username>"
}
}