action1-mcp-server
Related Servers
Alternatives to action1-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA 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.1025MIT
- AlicenseNot gradedqualityAmaintenanceMCP 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
- AlicenseAqualityAmaintenanceAn MCP server for Action1, a cloud-native RMM platform, enabling remote monitoring, patch management, and endpoint management through Action1's API.63Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server with file management, HTTP requests, system info, and environment variable tools, plus a management UI and dual transport for Claude Desktop and Claude.ai.221 npmMIT
- AlicenseBqualityDmaintenanceA complete MCP server for Fortinet FortiOS 7.6.x that exposes the entire REST API as typed MCP tools for use with MCP-compatible clients like Claude Desktop.10011MIT
- FlicenseNot gradedqualityCmaintenanceA local MCP server that connects Claude Code to your work environment through auditable tools for file operations, API calls, and command execution, with safety gates and configuration.-
TDQS
Scored across 166 tools
With 166 tools, there is significant overlap and multiple ways to perform similar actions (e.g., endpoints have get_endpoint, list_endpoints, search_endpoints, endpoints_summary). While descriptions often help, the large number makes it hard for an agent to reliably distinguish between closely related tools.
All tools follow the 'action1_verb_noun' pattern with occasional qualifiers. Minor deviations exist (e.g., 'action1_cve_remediation_plan' vs. 'action1_create_cve_remediation'), but overall consistency is high for such a large set.
166 tools is far beyond the recommended range (3-15) and indicates near-complete API exposure rather than a curated, coherent tool set. This overwhelming number undermines usability for both agents and humans.
The tool set covers CRUD for endpoints, groups, automations, scripts, packages, reports, vulnerabilities, users, roles, and more. Minor gaps exist (e.g., no delete_automation_instance, only stop), but overall the surface is very comprehensive.