Skip to main content
Glama

Related Servers

Alternatives to Atera MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      A
      maintenance
      Enables interaction with the Atera RMM/PSA API v3 for managing tickets, customers, contacts, agents, alerts, contracts, knowledge base, billing, custom fields, network devices, departments, and rates. It exposes 47 tools with read-only defaults and optional write or delete access.
      32
      51 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables 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.
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Codex to safely interact with Bitwarden vault status, metadata, generated logins, folders, and approved automation profiles while preventing direct secret access.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read computers, clients, locations, alerts, and script catalog and history data from the ConnectWise Automate RMM REST API, and on explicit request reboot machines, run scripts or catalog commands, and create or update clients. Credentials are supplied per request via HTTP headers and never stored, supporting stateless multi-tenant use.
      Apache 2.0

    TDQS

    A3.8/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct Atera resource or meta-information task. The health check, account context, and capabilities tools are descriptive enough that an agent can reliably distinguish them from the operational list/get tools.

    Naming Consistency4/5

    Tool names consistently use the atera_ prefix and mostly follow an atera_<resource>_<action> pattern with list/get pairs. atera_health_check and atera_capabilities are minor exceptions because they do not follow the same resource/action structure.

    Tool Count5/5

    Ten tools is well-scoped for an Atera connector: three meta/info tools plus list/get operations for customers, agents, and tickets, plus alerts listing. Each tool serves a clear purpose without unnecessary bloat.

    Completeness4/5

    The read-side surface covers the core Atera entities (customers, agents, tickets, alerts) with list and detail access for most resources. It lacks write/update/delete operations and an alerts-get detail tool, but this appears to be a deliberate read-only connector rather than a severe gap.

    Maintenance

    ActivityStale
    ResponsivenessNo issues