Atera

Atera

Atera RMM and help desk: customers, contacts, monitored agents with hardware and patches, agentless devices, alerts, tickets with comments and work hours, contracts and knowledge base. Atera REST API v3 with an API token.

7-day free trial · No credit card · EU-hosted

Ask Atera anything

Try a real prompt against Atera via AnythingMCP — Claude calls the tools, returns the answer. Press Enter on your own message to install on Cloud.

Install Atera on Cloud
Atera · live via MCP
Share
Opus 4.7

Claude is AI and can make mistakes. Please double-check responses.

Setup in 2 minutes

  1. 1Start a free trial on cloud.anythingmcp.com.
  2. 2Click Atera in the connector store. Paste credentials when prompted.
  3. 3Mint an MCP API key and point your AI client at the generated MCP URL.
Install Atera now

Guides for Atera

Step-by-step setup for the most popular AI clients.

Setting up Atera

From the connector definition itself: where to find the credentials, what they need to be allowed to do, and which API this adapter talks to.

Atera

This connector uses the Atera REST API v3 (https://app.atera.com/api/v3). Atera is a remote monitoring and management (RMM) and help desk (PSA) platform for IT departments and managed service providers.

Setup

In Atera open Admin > Data management > API (only Atera admins see it), click New token and copy the token into ATERA_API_KEY; Atera shows it only once. The token is sent as Authorization: Bearer <token>. When you create it you choose:

  • an expiration date (at most one year; Atera notifies admins 7 days and 1 day before it expires, then paste a new token here);
  • the IP addresses allowed to use it: keep Allow all, or add the outbound address of your AnythingMCP server;
  • the permissions: Full access, or Custom access with Read on the domains you want the agent to see (plus Write on Tickets and Alerts for the write tools).

Older accounts may still hold a legacy static API key (a short key, not starting with eyJ). Atera is replacing those with tokens; create a new token instead, because this connector sends the Bearer form.

With Full access the token has the rights of the whole Atera account: anyone with this connector can read every customer, device and ticket.

Start here

  • atera_list_customers gives the CustomerID used by most other tools.
  • atera_list_tickets (filter by customer_id or ticket_status) and atera_get_ticket for the help desk; atera_list_ticket_comments for the conversation.
  • atera_list_customer_agents or atera_find_agents_by_machine for devices; atera_get_agent for the full hardware inventory.
  • atera_list_alerts with alert_status Open for what needs attention now.

Ids

CustomerID, EndUserID (contacts), AgentID, TicketID, AlertID and ContractID are integers. Patch tools take the agent's DeviceGuid (a GUID), not the AgentID. Agentless devices (ping, SNMP, HTTP, TCP) are separate from agents and use their own DeviceID with atera_list_devices. A technician is identified by TechnicianContactID (shown on tickets) or by email.

Pagination

List answers have items, totalItemCount, page, itemsInPage, totalPages and nextLink. Pass page (from 1) and items_in_page (default 20, at most 50) and stop when page equals totalPages. For changes since a date use atera_list_modified_tickets rather than paging all tickets.

Rate limit

Atera allows about 700 requests per minute per account. Large accounts can have thousands of agents; page with a filter instead of listing everything.

Writes

atera_create_ticket, atera_update_ticket, the two comment tools and atera_resolve_alert change data. A technician comment with is_internal false is emailed to the end user, so confirm the text first. Ticket status names are free text in Atera (Open, Pending, Resolved, Closed and any custom ones); read them from existing tickets. Deleting customers, contacts, agents or tickets is not offered.

Your AI is two clicks away from Atera.

Install the connector, paste your credentials, ask your AI a question. 7-day free trial, no credit card.