Skip to main content
Glama
jshsakura

a360-mcp

by jshsakura
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to a360-mcp

No user-submitted related servers found.

    Related Servers

    • SoftAuto

      guangfubill-crypto
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to perform deterministic Windows desktop and browser automation through MCP, using pre-validated UI Automation and DOM locators for fast, stable execution of ERP and business workflows.
      2
      MIT

    • QA Copilot AI

      Sham-coder16
      F
      license
      B
      quality
      B
      maintenance
      MCP server for AI-powered QA analysis. It enables analyzing test failures, identifying root causes, suggesting fixes, classifying defects, detecting flaky tests, and generating test cases and bug reports.
      10
      -

    • OEE Enterprise Agent

      gigimento
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP-based production monitoring agent for manufacturing OEE, providing real-time monitoring, downtime root-cause analysis, and automated alerts through integration with SQL Server, MES APIs, and incident management systems.
      -

    • BridgeCommander

      copperlang2007
      F
      license
      Not graded
      quality
      B
      maintenance
      A hardened MCP desktop control server for secure process execution with strict session, buffer, and path limits. It enables reliable desktop automation via any MCP client and emits outcome events for integration with automation flywheels.
      -
    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

    B3.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: get_bot_actions retrieves bot action definitions, get_execution fetches a single execution's details, and list_executions searches execution history. There is no ambiguity or overlap between these operations.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern, using get_ for singular resources and list_ for collections. The naming is predictable and adheres to standard conventions.

    Tool Count4/5

    With only 3 tools, the server is at the lower end of the typical range, but each tool covers a distinct aspect of the domain (bot actions and executions). It feels slightly thin but is still reasonable for a focused utility.

    Completeness2/5

    The server lacks essential operations such as listing bots (making it impossible to discover bot IDs for get_bot_actions) and does not support execution lifecycle actions like starting or canceling executions. This creates significant gaps for agents trying to perform broader workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources