Skip to main content
Glama
Oleksandr-Kliuiev

Atera MCP

by Oleksandr-Kliuiev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Atera MCP

No user-submitted related servers found.

    Related Servers

    • Feishu Codex MCP

      cimorn
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables Codex to access Feishu knowledge bases and authorized shared cloud drives, allowing listing, searching, and reading wikis, documents, spreadsheets, bitable, and files, with scoped and approval-gated create and edit capabilities.
      -

    • mcp-server-action1

      borgels
      A
      license
      A
      quality
      C
      maintenance
      Enables management of endpoint inventory, patching, and vulnerabilities through the Action1 REST API, with read-only access by default and optional write support for update approvals.
      15
      1
      Apache 2.0

    • poweroffice-mcp

      Oleksandr-Kliuiev
      F
      license
      A
      quality
      C
      maintenance
      Enables Codex to securely access PowerOffice Go API v2 with read-only tools and write operations that require explicit confirmation for customers and general ledger accounts.
      10
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivityMaintained
    ResponsivenessNo issues

    Resources