---
schema_version: "1"
id: bca4fb719109f9eb6aa0a8b30711b2b72e0ee158103ee2dfa5b970913b048e0b
title: Add Servers to Runtime Manager
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/runtime-manager/servers-create.md
canonical_url: https://docs.mulesoft.com/runtime-manager/servers-create
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 00ae87de85cdc1f86be8e62f9ae2d43ecbeb611b975fcbfac21b12418ecdb4fd
description: MuleSoft Documentation Site
latest: true
---
---
product: Runtime Manager
---

# Add Servers to Runtime Manager

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

[![logo hybrid active](/mulesoft/current/en-us/_/img/icons/hybrid-cloud.svg "Hybrid")Hybrid](deployment-strategies#hybrid-deployments)[ ![logo server active](/mulesoft/current/en-us/_/img/icons/server-cloud.svg "Anypoint Platform PCE")Private Cloud Edition](deployment-strategies#anypoint-platform-private-cloud-edition)

To add a Mule server to the Runtime Manager console so that you can manage it, you must first
register it with the Runtime Manager agent. Use the `amc_setup` script to configure the Runtime
Manager agent to communicate with Runtime Manager.

## Prerequisites

- Your enterprise license is current.

- If you must download the agent, you have an Enterprise support account.

- If the server is already registered with another Runtime Manager instance, remove that
  registration first.

## Add a Server

To add a Mule server to Runtime Manager:

1.  From Anypoint Platform, select **Runtime Manager**.

2.  Click **Servers** in the left menu.

3.  Click the **Add Server** button.

4.  Enter a name for your server.

    Server names can contain up to 60 alphanumeric characters (a-z, A-Z, 0-9), periods (.), hyphens
    (-), and underscores (\_), but not spaces or other special characters. Runtime Manager supports
    Unicode characters in server names.

    The server name must be unique in the environment, but it can be the same for the same
    organization in different environments.

    Runtime Manager generates the `amc_setup` command. This command includes the server name you
    specified (`_server-name_`) and the registration token (`_token_`) required to register Mule in
    your environment. The registration token includes your organization ID and the current
    environment.

    ![amc\_setup command in the Add Server window](/mulesoft/current/en-us/runtime-manager/_images/rtm-add-server.png)

    Figure 1. The arrow shows the `amc_setup` command in the **Add Server** window.

5.  Click **Copy command** to copy the `amc_setup` command.

    This button appears only if the server name you specify is valid.

6.  In a terminal window, change to the `$MULE_HOME/bin` directory for the Mule instance that you’re
    registering.

7.  Paste the command on the command line.

8.  Include any other parameters on the `amc_setup` command line.

    For information, see
    [amc\_setup Parameters](https://docs.mulesoft.com/runtime-manager/installing-and-configuring-runtime-manager-agent#amc_setup-parameters).

9.  If your environment requires all outbound calls to go through a proxy, specify proxy settings in
    either the `$MULE_HOME/conf/mule-agent.yml` file or the `$MULE_HOME/conf/wrapper.conf` file.

    See [Connect the Agent Through a Proxy Server](https://docs.mulesoft.com/runtime-manager/rtm-agent-proxy-config). When the `amc_setup`
    command completes successfully, you see:

Mule Agent configured successfully Connecting to Access Management to extract client\_id and
client\_secret Credentials extracted correctly, updating wrapper conf file

After the script completes successfully, the name of your server appears on the **Servers** tab of
Runtime Manager with a status of `Created`.

If the server was running when you ran the `amc_setup` script, restart the server to reconnect with
Runtime Manager.

## Remove a Server from Another Runtime Manager Instance

If the server you want to add is already registered with a different instance of Runtime Manager,
you must remove it before you can register.

To remove the server from Runtime Manager:

1.  In Runtime Manager, delete the server from the **Server** tab.

    See [Shut Down, Restart, or Delete Servers](https://docs.mulesoft.com/runtime-manager/servers-actions).

2.  In the `$MULE_HOME/conf` directory, delete the `mule-agent.yaml` and `mule-agent.jks` files.

## See Also

- [Run Mule Runtime Engine On-Premises](https://docs.mulesoft.com/on-premises/latest/)

- [Install or Update the Runtime Manager Agent](https://docs.mulesoft.com/runtime-manager/installing-and-configuring-runtime-manager-agent)

- [Shut Down, Restart, or Delete Servers](https://docs.mulesoft.com/runtime-manager/servers-actions)

- [Ports, IP Addresses, and Hostnames to Allow](https://docs.mulesoft.com/runtime-manager/rtm-agent-allowlists)