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 дней бесплатно · без карты · EU-хостинг
Спроси Atera что угодно
Попробуй реальный промпт против Atera via AnythingMCP — Claude вызывает tools, возвращает ответ. Нажми Enter на своём сообщении, чтобы установить в Cloud.
Установить Atera в CloudClaude — это AI, он может ошибаться. Проверяйте ответы.
Настройка за 2 минуты
- 1Запусти free trial на cloud.anythingmcp.com.
- 2Нажми Atera в коннектор-сторе. Вставь учётные данные.
- 3Выпусти MCP API ключ и направьте AI-клиент на MCP URL.
Гиды по Atera
Пошаговая настройка для основных AI-клиентов.
Настройка Atera
Прямо из определения коннектора: где взять учётные данные, какие права им нужны и с каким API работает этот адаптер. Предоставлено автором коннектора на английском языке.
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_customersgives theCustomerIDused by most other tools.atera_list_tickets(filter bycustomer_idorticket_status) andatera_get_ticketfor the help desk;atera_list_ticket_commentsfor the conversation.atera_list_customer_agentsoratera_find_agents_by_machinefor devices;atera_get_agentfor the full hardware inventory.atera_list_alertswithalert_statusOpen 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.
Твой AI в двух кликах от Atera.
Установи коннектор, вставь учётные данные, спроси AI. 7 дней бесплатно, без карты.