Skip to main content
Glama
MikeRiveira

Atera Triage MCP

Related Servers

Alternatives to Atera Triage 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
      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
      A
      quality
      C
      maintenance
      Enables Codex to interact with the Atera REST API, including reading customers, agents, tickets, and alerts, checking health, and listing capabilities, with optional write operations when explicitly enabled.
      10
      51 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read and act on managed security data from the Huntress API, covering accounts, organizations, protected endpoints, incident reports and their remediations, escalations, signals, users, invoices and summary reports. Read operations are safe by default, while data-changing actions such as resolving incidents, approving remediations, and managing organizations or users require explicit write and confirm flags.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with AutoTask PSA data, supporting natural language ticket queries, updates, notes, and bulk export.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query and manage a web hosting billing platform through its External API — clients, tickets, invoices, domains, orders, products, and system data. It defaults to read-only with per-domain opt-in for writes, two-step confirmation for billing and destructive actions, and automatic redaction of secrets, card data, and PII.
      1
      MIT

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation4/5

    Most tools target distinct aspects of triage (queue, ticket details, site health, alerts), but morning_brief aggregates data also available through triage_queue, site_health, and open_alerts, creating some potential for confusion about when to use the summary versus the focused tools.

    Naming Consistency4/5

    All names use snake_case and are readable, but the convention is not uniformly verb_noun: get_ticket is verb_noun, while morning_brief, triage_queue, site_health, and open_alerts are noun phrases or adjective_noun. This is a minor deviation, not a hindrance.

    Tool Count5/5

    Five tools is well-scoped for a triage server. Each tool serves a clear role—overview, queue, detail, device status, alerts—and none feels redundant or extraneous.

    Completeness4/5

    The surface covers the core read-only triage workflow: summary, prioritized tickets, ticket details, site/device health, and active alerts. Minor gaps exist, such as no dedicated alert-detail drill-down or cross-site ticket search beyond optional site filtering, but agents can work around these with existing tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues