Generating API keys: Autotask, Datto RMM, and IT Glue

Before Claude can connect to your Kaseya product, give it permission to do so. Each product uses a unique set of secret credentials called API keys to verify that the connection is coming from an authorized source. You generate those keys in each product by following the steps in this guide, then paste them into your Claude configuration file to complete the connection.

• You must be an administrator in each product. Generating API keys requires admin-level access in Autotask, IT Glue, and Datto RMM. If you do not have that access, ask whoever manages your Kaseya account to complete these steps and share the values with you securely.

• Secret values are shown only once. The secret or password portion of each key pair is displayed only when you generate it. After you leave the page, you cannot retrieve it. Keep a secure place ready to store your values before you begin, such as a password manager or your IT Glue vault.

Requirement: Administrator role in Autotask.

1. In Autotask, select Admin in the left menu.

   

2. Under Admin in the left menu, click Resources (Users).

3. On the Resources page, select New API User from the + New dropdown menu.

   

4. On the Add API User page, complete the required information for the new API user. Make sure the Security Level field is set to API User (system).

5. Click Generate Key and Generate Secret. Copy both values immediately and store them securely.

   

6. In the API Tracking Identifier section, keep Integration Vendor selected, then search for and select Autotask - MCP.

   

7. Unless your business strictly separates work by line of business, leave the Line of Business field blank. Assigning one here can restrict what the API user can view.

8. Click Save and Close.

In addition to your Autotask API credentials, you are prompted for your Autotask MCP endpoint value when you connect. Use the table below to identify the MCP hostname to enter for this field.

After you save your Autotask key and secret, and your MCP hostname, continue to the next product below to generate its API credentials.

For additional information about creating API users in Autotask, see Adding or editing an API user.

Requirement: Administrator role in Datto RMM.

1. In Datto RMM, select Setup > Global Settings in the left menu.

2. On the Global Settings page, turn on the Enable API Access toggle in the Access Control section.

   

1. In the left menu, select Setup > Users.

2. On the Users page, select the username for which you want to generate keys.

   

3. On the username page that displays, scroll down to the API section, then click Generate API Keys.

   

4. The API Key and API Secret Key display. Copy both values immediately and store them securely.

You are prompted to choose the platform for your Datto RMM account by number. Use the key below to determine which number to enter.

For additional information about creating API keys in Datto RMM, see Datto RMM API.

Requirement: Administrator role in IT Glue.

1. In IT Glue, select Admin in the top menu, then Settings in the left menu.

   

2. On the Settings page, select the API Keys tab.

3. In the Custom API Keys section, click + Create API Key.

4. In the Enter Name field below, enter a name for the key, such as Claude MCP, then click Generate Secret Key. Copy the key value immediately and store it securely.

   

5. Optionally, select the Password Access checkbox if you want the API key to retrieve password records from IT Glue. Leave it unselected if you do not need it.

For additional information about creating API keys in IT Glue, see Getting started with the IT Glue API.

• Create a dedicated API user for Claude in each product. Rather than using a personal admin account, create a purpose-built API user specifically for this integration and give it a clear name such as Claude MCP. This helps you identify Claude connections, control access, and revoke credentials cleanly without affecting anyone else.

• Generate one set of keys per person setting up the integration. If multiple team members are configuring Claude separately, each person should generate their own keys rather than share one set. This makes it easier to track changes and rotate credentials individually if someone leaves.

• Use a dedicated service account, not a personal one. If a user account is deactivated or deleted in any of the products, the API keys stop working immediately. Building the integration under a shared service account prevents disruption if a team member leaves.

• Revoking or regenerating a key immediately breaks existing connections. If you need to rotate a key, generate a new one in the relevant product, update the value in your Claude configuration file, and restart Claude Desktop. The old key stops working as soon as a new key is generated.

After you have sets of credentials for all products, return to the README and follow Step 2: Connect to MCP servers and install skills in Claude Desktop.