atera-mcp
Related Servers
Alternatives to atera-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceLets an AI agent read an MSP's customers, monitored agents, alerts, tickets and contacts through the Atera RMM/PSA v3 API, and, on explicit request, create customers and tickets, update ticket fields and add ticket comments. It runs statelessly over MCP Streamable HTTP with a per-request API key and exposes all 20 list, get and write tools from the first tools/list call.Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI assistants to triage an Atera help desk by ranking open tickets with plain reasons, summarizing site health and alerts, and producing a one-call morning brief. It redacts personal data, fences user-written text as untrusted, and stays read-only unless writes are explicitly enabled.6MIT
- AlicenseBqualityDmaintenanceComprehensive read/write access to the Datto RMM API v2, enabling management of devices, sites, alerts, audits, jobs, variables, filters, and activity logs through 46 tools.46MIT
- AlicenseNot gradedqualityBmaintenanceGives AI agents access to five MSP products' APIs — Core, Lifecycle Manager, ControlMap, Backup Radar and Quoter — through 381 tools that read clients, contacts, assets, tickets, roadmaps, compliance data, backup health and quotes, and on explicit request create, update, attach, publish or delete records using a single API key passed per request.Apache 2.0
- AlicenseCqualityCmaintenanceProvides AI assistants with direct access to Autotask PSA for MSP operations. Enables natural language interaction for ticket management, time logging, company lookups, project tracking, and billing review through 39 comprehensive tools.100123 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceProvides comprehensive access to the Kaseya VSAX (VSA 10) REST API v3 through 67 specialized tools. It enables users to manage devices, run workflows, execute scripts, and oversee organizational data using natural language and OData query support.1MIT
TDQS
Scored across 32 tools
Tools are grouped by distinct Atera resources, and descriptions proactively distinguish easily confused pairs such as list_customers/find_customers, list_devices/list_agents, and get_agent/find_agents/get_agent_by_machine. The main residual ambiguity is the multiple agent-retrieval variants, but selection guidance is strong.
All tool names use a predictable snake_case verb_noun pattern with list_, get_, and find_ prefixes. Compound names such as get_agent_by_machine and get_ticket_work_hours still follow the same convention without mixing casing or verb styles.
With 32 tools, the server exceeds the rubric's 25+ threshold for 'too many.' Although Atera is a broad platform, many tools are list/get/search variants that could be consolidated or better namespaced, making the surface heavy for an agent to navigate.
The read/query surface is comprehensive across customers, contacts, agents, devices, tickets, alerts, invoices, contracts, KB articles, and custom fields. However, there are no create, update, or delete operations, so the set cannot perform common lifecycle actions such as opening or updating tickets, adding comments, or managing records.