Use to set up user and automation access for the MCP (Model Context Protocol) server in the Automation Anywhere Control Room.

  1. Create a new role with permissions, user, and licenses:
    1. From the Control Room, navigate to Administration →Roles.
    2. Click Create Role and enter a name (for example, MCP_Server).
    3. Give the role these permissions:
      To make it easier and more organized to control access for Agent Interoperability, repository (role based access control) RBAC is used. This helps to discover and use Automation Anywhere automations, processes, and API Tasks.
      Permissions Settings
      AI
      • View Agent Connections: Allows users to view inbound and outbound tools and connections
      • Manage Agent Connections: Allows users to configure and manage inbound and outbound tools and connections
      API Generate API-Key. See Generate API key for details.
      BOTS
      • View my bots
      • Run my bots
      Note: You must select which bots you want to include in the Custom role.
      DEVICES Register device
    4. Save the role.
    5. Navigate to Administration →Users and create a new user.
    6. Assign the (new) MCP_Server role to the user:
    7. Make sure the Attended Bot Runner license is assigned.
    8. Save the user.
  2. To run a process from the MCP client, check that your process configuration is correct and the process can run from the Control Room. For process configuration details, see Create a business process.
    1. Log in to Automation Co-Pilot with the AAE_Robotic Interface Admin user.
    2. Navigate to Manage →Processes and the Process Setup page.
    3. Review the Scheduler user to make sure it is correct.
  3. Configure teams.
    1. Navigate to Manage →Teams and create a new team.
    2. Map each process to the team you just created.
  4. To run an API Task from the MCP Client, make sure the API Task details are configured (see Example: API Task).
    • To execute API Tasks, the user must have the Register device permission. 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.
    • You can also add the AAE_API Task Runner role to any custom user who needs to execute API Tasks.
  5. Check that your API Task Runner configuration is correct and can run the API Tasks.

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>"
            }
        }