Skip the install. Get this working in under 2 minutes.
Start a free trial on cloud.anythingmcp.com, add the Atera in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.
Summary
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.
Try asking
Example prompts for Atera
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Atera, paste your credentials, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
Atera + ChatGPT
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.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
ATERA_API_KEY
Step 1 — Get credentials
- In Atera open Admin → Data management → API. Only Atera admins see this page.
- Click New token and choose an expiration date (at most one year), the IP addresses allowed to use the token (keep Allow all, or add the outbound address of your AnythingMCP server) and the permissions: Full access, or Custom access with Read on the domains the AI should see, plus Write on Tickets and Alerts if you want the write tools.
- Copy the token into
ATERA_API_KEYright away: Atera shows it only once. The connector sends it as a Bearer token. - Install the connector and run
atera_list_customers. It lists your client companies with the CustomerID most other tools need.
Use a token, not a legacy key: older accounts may still hold a static API key (a short key that does not start with eyJ). Atera is replacing those with tokens and this connector only sends the Bearer form, so create a new token.
Token expiry: a token lasts at most one year. Atera notifies admins 7 days and 1 day before it expires; then create a new token and paste it into ATERA_API_KEY.
Who sees what: with Full access the token has the rights of the whole Atera account, so anyone using this connector can read every customer, device and ticket. Custom access limits the AI to the domains you grant.
What it reads: customers and their contacts, monitored agents with their full hardware inventory and installed or missing patches, agentless devices (ping, SNMP, HTTP, TCP), alerts, tickets with comments, work hours and billable time, contracts and the knowledge base. Good starting points are atera_list_tickets, atera_list_customer_agents and atera_list_alerts with the status Open.
Confirm first: the AI can create and update tickets (atera_create_ticket, atera_update_ticket), add comments (atera_add_technician_comment, atera_add_enduser_comment) and resolve alerts (atera_resolve_alert). A technician comment that is not internal is emailed to the end user, so the AI shows you the text before it posts. Ticket status names are free text in Atera, so it reads them from existing tickets.
Limits: Atera allows about 700 requests per minute per account. Lists come in pages of at most 50 items, so on large accounts the AI filters by customer or status and uses atera_list_modified_tickets for recent changes instead of paging through every ticket.
Deleting customers, contacts, agents or tickets is not offered, and patches are only listed, not installed.
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in ChatGPT
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
ChatGPT adds MCP servers as plugins on its Plugins page, on the web and on paid plans. Developer mode is no longer needed. In a Business workspace only admins and owners can add one; in Enterprise and Edu an admin can grant the Create plugins with MCPs permission.
- Go to chatgpt.com/plugins, click +, then Add custom MCP server.
- Enter a name, e.g. Name:
Atera. - Under Connection, enter the Server URL
https://cloud.anythingmcp.com/mcp/YOUR_SERVER_IDand keep Authentication on OAuth. - Select I understand and want to continue, then Create as a plugin. When ChatGPT asks, sign in to AnythingMCP and allow access.
- Install the new plugin from your personal plugins, then type @ in a chat and pick it.
Available tools
| Tool | What it does |
|---|---|
atera_list_customers | List the customers (client companies) in Atera with id, name, domain, address and phone |
atera_get_customer | Get one customer by CustomerID: name, business number, domain, address, phone, notes and links |
atera_list_contacts | List end-user contacts with EndUserID, customer, name, email, phone, job title and department |
atera_get_contact | Get one contact by EndUserID: customer, name, email, phones, job title, department and whether it is the customer's main contact person |
atera_list_agents | List all monitored devices (agents) across customers: machine name, customer, online state, last seen, OS, IP and MAC addresses, hardware… |
atera_list_customer_agents | List the agents (monitored devices) of one customer with online state, OS, hardware and last-seen time |
atera_get_agent | Get one agent by AgentID with full hardware and OS inventory: processor, memory, disks, BIOS, serial number, Office version, last reboot… |
atera_find_agents_by_machine | Find agents by machine (computer) name, for example DESKTOP-4F2K |
atera_list_installed_patches | List the patches (Windows updates) installed on one agent, identified by its DeviceGuid |
atera_list_available_patches | List the patches available but not yet installed on one agent, identified by its DeviceGuid |
atera_list_devices | List agentless monitored devices of one type (generic ping, SNMP, HTTP or TCP) with name, DeviceID, customer and monitoring agent |
atera_get_device | Get one agentless monitored device (generic, SNMP, HTTP or TCP) by DeviceID with its monitoring settings, customer and monitoring agent |
atera_list_alerts | List monitoring alerts with title, severity (Information, Warning, Critical), device, customer, creation time and linked ticket |
atera_get_alert | Get one alert by AlertID: title, message, severity, category, thresholds, device, customer, snooze end date and linked ticket |
atera_resolve_alert | Mark one open alert as resolved |
atera_list_tickets | List help desk tickets with number, title, status, priority, type, customer, end user, technician, SLA dates and durations |
atera_get_ticket | Get one ticket by TicketID with status, priority, impact, type, customer, end user, technician, first and last comments, SLA due dates and… |
atera_list_modified_tickets | List tickets modified since a date (UTC), optionally with their last comments |
atera_list_closed_tickets | List tickets whose status changed to resolved or closed, with their comments by default |
atera_list_ticket_comments | List the comments of one ticket in order: text, date, author (end user or technician, with email and name) and whether the comment is… |
atera_list_ticket_work_hours | List the work-hour records logged on one ticket: technician, start and end time, duration, billable flag and on-site or remote |
atera_get_ticket_billable_duration | Get the billable time totals of one ticket (on-site and off-site) as Atera computes them for invoicing |
atera_list_contracts | List customer contracts with type (retainer, hourly, block hours, block money, remote monitoring, project), active and default flags and… |
atera_list_customer_contracts | List the contracts of one customer with type, rates, active flag and dates |
atera_get_contract | Get one contract by ContractID with its type-specific details (hourly rates, block hours, retainer fee, monitored device rates) and dates |
atera_list_knowledge_base | List the knowledge base articles in Atera with title, content, keywords and visibility |
atera_create_ticket | Create a help desk ticket |
atera_update_ticket | Update a ticket's title, status, type, priority, impact or assigned technician |
atera_add_technician_comment | Add a technician comment to a ticket |
atera_add_enduser_comment | Add a comment to a ticket on behalf of the end-user contact, for example to log a reply that arrived by phone |
Example prompts
- "Which critical alerts are still open right now, and on which customers' machines?"
- "Show me the open tickets of the customer Northwind with their technician and SLA due date."
- "How many billable hours did we log on tickets closed last month, per customer?"
- "Draft a reply to the end user on ticket 1234 and show it to me before you post it."
FAQ
Does the free ChatGPT plan work with custom MCP servers? OpenAI documents custom MCP servers for paid plans only; the Free plan is not on its list.
Next steps
Was this guide helpful?
