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

Important: This feature is not generally available and is restricted to specific customers. Contact your Automation Anywhere account team for more information.
  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, CustomerRole).
    3. Give the role these permissions:
      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
      Bots
      • View my bots
      • Run my bots
      • Select the required folders/bots to run automations
      Administration
      • View Settings
      • Manage Settings
      API Generate API-Key
      Automation Co-Pilot Setup
      • View and manage MY teams
      • View and manage ALL teams
      • View and manage ALL bots
    4. Save the role.
    5. Navigate to Administration →Users and create a new user.
    6. Assign the new role, CustomerRole, to the user, and add these roles too:
      • AAE_Basic
      • AAE_Robotic Interface User
    7. Navigate to Administration →Licenses.
      License type Accessible features
      Base license
      • Ability to invoke Automation Anywhere bots, processes, API Tasks and AI Agents (if available in Customer Control Room), as individual MCP inbound tools
      • RBAC is available for MCP Inbound connections.
      • No limit to number automations (bots and processes that you can run.
      • Streamable HTTP with API Key is supported.
      Enterprise license In addition to what is available in the Base license, the following is accessible:
      • PRE/Automation Discovery Service is available

      Based on what features you want to access, assign a license for the platform and Control Room devices.

    8. Save the user.
  2. Log in and configure teams and bots in Automation Co-Pilot:
    1. Log in to Automation Co-Pilot using the user you just created.
    2. Navigate to Manage →Teams and create a new team.
    3. Add the task bot automations that you want to deploy via the MCP (Model Context Protocol) server.
    4. Map each bot to the team you just created.
  3. Configure API Tasks in the Control Room Settings:
    1. Return to the Control Room home page.
    2. Navigate to the Administration →Settings→Cloud Device Management section.
    3. Add the API Tasks (which you plan to deploy via the MCP server) under the API Tasks in Forms section.
  4. Connect the Bot Agent (BA) device and configure the API Task Runner:
    1. From your local machine, connect the Bot Agent device to deploy the task bot automations.
    2. Make sure the Attended Bot Runner license is assigned (as done in Step 1).
    3. 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>"
            }
        }
Note: MCP server configuration is not available in the Control Room right now. Once you set up the Automation Anywhere MCP server endpoint and user credentials in your MCP client, you can use these MCP tools:
  • Discover automations: This MCP tool looks at what the user wants and finds the right automations from the Automation Anywhere public repository. It only gets automations that the user is allowed to use.
  • Run automations: This MCP tool runs Automation Anywhere bots and API Tasks from third-party AI Agents.
  • Get automation results: This MCP tool gets the status or result of the automation that was started by the Run automations tool.