Skip to main content
Glama

Related Servers

Alternatives to action1-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      A comprehensive Model Context Protocol (MCP) server that enables Claude and other LLM applications to execute PowerShell commands, scripts, and perform system operations on Windows systems.
      10
      27
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for the Atera RMM API. Implements a decision tree architecture for efficient tool discovery, enabling Claude to manage devices, alerts, tickets, and customers in Atera.
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server for Action1, a cloud-native RMM platform, enabling remote monitoring, patch management, and endpoint management through Action1's API.
      6
      3
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Read-only MCP server for the Action1 RMM REST API, enabling access to endpoints, missing updates, vulnerabilities, installed software, policies, automations, and reports.
      21
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Autonomous network monitoring and auto-remediation MCP server for Claude Desktop, enabling observation, planning, human-approved execution, verification, and session summarization.
      1
      -
    • A
      license
      A
      quality
      A
      maintenance
      Enables Claude Desktop, Cursor, and other MCP-aware clients to conversationally manage endpoints, query and triage alerts, inspect events, manage policies and intel feeds, mint enrollment tokens, and preview or commit fleet changes.
      23
      548 npm
      Apache 2.0

    TDQS

    C2.7/5.0

    Scored across 167 tools

    Disambiguation2/5

    The set contains many overlapping tools: list_missing_updates vs list_endpoint_missing_updates, list_vulnerabilities vs list_org_vulnerabilities, list_endpoints vs search_endpoints, and multiple automation instance/output/summary tools. Curated aliases and generic tools like raw_request further blur boundaries, making misselection likely despite helpful descriptions.

    Naming Consistency3/5

    Most tools use a consistent action1_ prefix and snake_case, but the naming pattern is mixed: many are verb_noun, while others are noun-style or summary/resolve/export helpers. The inconsistency is readable but not predictable enough for a large toolset.

    Tool Count1/5

    With 167 tools, this far exceeds a practical surface for an agent, even for a broad RMM platform. The count creates selection burden and increases the chance of using near-duplicate or wrong-domain tools.

    Completeness4/5

    Coverage is very broad across endpoints, organizations, users, roles, scripts, reports, software repository, automations, vulnerabilities, audit, and subscriptions. Some lifecycle gaps remain, such as unsupported software upload tools and partial automation action/version management, but most core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues