read thedocs.

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 family of 115 atera_ MCP tools — MCP (Model Context Protocol) tools are the standardized commands an AI assistant can call through StackJack. With them, 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 (on Pro plans) — create and update tickets, customers, contacts, devices, alerts, products and expenses, and delete records

How StackJack authenticates to Atera

Atera uses a single static API key sent on every request. An Atera administrator generates it in the Atera console under Admin → API. The key grants full account access — Atera has no per-endpoint scopes — so treat it like a password: anyone holding it can read and change everything in your Atera account (customers, tickets, billing, devices).

There is no OAuth, no login redirect, and nothing to refresh. Because the key is account-wide and not tied to an individual login, all AI traffic authenticates as the account rather than as a specific technician — there is no per-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, because only an admin can view or generate the account API key under Admin → API.

Step 1 — Get your Atera API key

1. Sign in to Atera with an Administrator account.
2. Go to Admin → API.
3. Copy the API key shown on the page. If no key exists yet, generate one.
4. Keep it handy for the next step, and treat it as a highly privileged secret.

Step 2 — Add the credential in StackJack

1. In the StackJack portal, open Connectors.
2. Find the Atera card. Click How To Connect for the same steps inline, or Configure to enter the credential.
3. Paste your API Key.
4. Click Save.

What happens when you save

• The API key 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 key by making a cheap authenticated read (a single-row customers request). Validation never blocks the save: you'll either see a success confirmation or a "saved but validation failed" warning with the reason.
• The connector card shows the current connection and validity status from then on.

Plans and available tools

• Free includes the 67 read-only tools: list/get across agents (including installed and available patches), devices, alerts, the knowledge base, customers, contacts, contracts, tickets (and their comments, durations, attachments, relations, and work-hours), invoices, products, expenses, departments, your account, and custom-field values.
• Pro adds the 48 write tools: create/update/delete customers, contacts, tickets, devices, alerts, contracts, products and expenses; manage departments and ticket relations; set custom-field values; and the device-family creates. 13 of these are delete operations, flagged as destructive so a consent-aware AI client prompts before running them.

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

Safety note. The Atera key is account-wide, so the tools you enable define the entire blast radius of an AI's access. Enable only the actions you want an AI to take — use the tool selections on the MCP Setup page and the Permissions page. The delete tools (agents, devices, alerts, customers, contacts, tickets, products, expenses) permanently remove records in Atera and cannot be undone from StackJack.

How Atera paginates

List tools page through results with a page number and a page size, and Atera caps the page size at 50 (unusually small). StackJack clamps any larger value to 50, so a big inventory read simply returns more pages rather than failing — your AI walks the pages until it reaches the end.

Rate limits

Atera enforces an account-wide limit of 700 requests per minute across all endpoints. StackJack paces tool calls to stay comfortably within that limit and automatically backs off when Atera signals it's busy, so bursts of calls queue briefly instead of failing — a long multi-page read may simply take a little longer.

Rotating or replacing the credential

The API key is the only secret. If you regenerate the key in Atera (Admin → API), the previous key stops working immediately. To restore access, open Connectors → Atera → Configure in StackJack and paste the new key, then Save. Rotate the key in Atera if you suspect it has been exposed — because it grants full account access, a leaked key is a full-account risk.

Troubleshooting