Connect Atera

Atera is an all-in-one RMM (remote monitoring and management) and PSA (professional services automation) platform for MSPs and internal IT teams. It brings device monitoring, ticketing, customers and contacts, contracts, billing and rates, and custom fields together in one cloud console.

Connecting Atera to StackJack gives your AI assistant a broad family of atera_ MCP tools — MCP (Model Context Protocol) tools are the standardized commands an AI assistant can call through StackJack. Depending on the tools you enable, your AI can:

• Inventory RMM agents and the four monitored-device families (generic, HTTP, SNMP, TCP)
• Triage alerts and search the knowledge base
• Manage the PSA side — customers, end-user contacts, contracts, and tickets (with their comments and work-hours)
• Review billing invoices and the rates catalog (products and expenses)
• Read and set the account's custom-field values across agents, tickets, customers, contacts, contracts, SLAs, and devices
• Act — create and update operational records, with destructive actions separately identified for consent-aware clients

How StackJack authenticates to Atera

Atera uses a named API token sent in the X-API-KEY header on every request. An Atera Administrator creates it under Admin → Data management → API. Atera lets you create multiple tokens, set an expiration up to one year away, restrict source IPs, and choose either Full access or Custom access by API domain and action (Read, Write, and Delete). Treat the token like a password even when it is narrowly scoped.

There is no OAuth, login redirect, or refresh flow. StackJack calls authenticate as the configured token rather than as the currently signed-in technician, so Atera does not provide per-call interactive-user attribution.

Atera is a single global cloud (https://app.atera.com), so there is no region to choose — the connector form asks only for the API key.

Before you begin

• In StackJack: you need a role that can manage connectors (tenant Owner, a co-owner, or an Administrator).
• In Atera: you need an Administrator account to manage tokens under Admin → Data management → API.
• Decide which StackJack tools you plan to enable. That determines which Atera API domains and Read, Write, or Delete actions the token needs.
• Review Atera's current Using the Atera API instructions before creating the token.

Step 1 — Create a least-privilege Atera token

1. Sign in to Atera with an Administrator account.
2. Go to Admin → Data management → API, then select New token.
3. Give the token a recognizable name and choose an expiration date no more than one year away.
4. Allow all source IPs, or configure the IP allowlist your environment requires. StackJack does not publish its outbound addresses: open a support ticket to get the current addresses for your region before you enable the restriction, and ask again after a region move, because they change.
5. Prefer Custom access. Grant the API domains that match your selected StackJack tools and only the required Read, Write, and Delete actions. Choose Full access only when you intentionally need the entire connector surface.
6. Create the token and copy it immediately. Atera shows the token value only once.

Step 2 — Add the credential in StackJack

1. In the StackJack portal, open Connectors.
2. Select the Atera tile to open its details. Choose How To Connect to review the inline setup guide, or Configure to reveal the credential form in the drawer.
3. Paste the Atera token into API Key.
4. Click Save.

What happens when you save

• The token is stored encrypted in Azure Key Vault — never in the StackJack database, and never shown back to you.
• If this is the first time you configure Atera, a Free-tier subscription for the connector is created automatically so its Free tools work right away.
• StackJack immediately live-validates the token with a one-row customers request. Validation never blocks the save.
• After saving, the form collapses and the connector drawer stays open. It shows Connected / Valid on success, or Needs Attention with Re-test and recovery guidance if validation failed.

Plans and available tools

See the generated Atera tool reference for the current inventory, plan assignment, input schemas, and destructive-action labels.

Current pricing and quotas are shown in the portal's Billing page and at checkout.

Safety note. Least privilege has two layers: the Atera token's API-domain/action permissions and the tools you enable in StackJack on the MCP Setup and Permissions pages. A tool labeled destructive can permanently change or remove upstream data; review its current schema and destructive label in the generated reference before enabling it.

How Atera paginates

List tools use a one-based page number and page size. Most Atera list endpoints in the checked-in API contract allow up to 500 items per page. Ticket-family endpoints allow 50. StackJack also uses a 50-item safety cap for the few list endpoints whose contract does not publish a maximum. A large read therefore may require several calls, and callers must continue paging until the response indicates the end.

Rate limits

Atera's current public setup guide and API FAQ do not state a numeric upstream request ceiling. StackJack conservatively paces Atera calls at 600 requests per minute per tenant and reacts to HTTP 429 responses. Other callers using the same token and Atera-side policy are outside that local budget, so a rate-limit response can still occur; honor the retry delay rather than immediately repeating a large batch.

Rotating or replacing the credential

Atera supports multiple named tokens, so you can rotate without intentionally creating a gap: create a replacement under Admin → Data management → API, copy it once, update Connectors → Atera → Configure in StackJack, save, and confirm Valid. Only then revoke the old Atera token. Repeat this before its configured expiration, and rotate immediately if it may have been exposed.

Disconnecting Atera

Using Disconnect in the Atera connector drawer removes StackJack's stored credential and stops future connector calls. It does not revoke the token in Atera. Revoke or delete that token separately under Admin → Data management → API when it is no longer used anywhere else. Disconnecting credentials and changing a paid connector subscription are separate actions; review the drawer's subscription choice before confirming.

Troubleshooting

Atera tools

atera_ · 115 tools · Free 67 · Pro 48

Agents

Devices

Alerts

Knowledge Base

Account

Departments

Customers

Contacts

Contracts

Tickets

Billing

Rates

Custom Values