Skip to main content
Glama

Related Servers

Alternatives to Raidcom MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      B
      maintenance
      Enables deploying and managing infrastructure via natural language, including project/domain management, compute nodes, image deployment, and CI/CD integration.
      70
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible clients to plan, validate, generate, and deploy complete network topologies from natural-language instructions, including live deployment to a running network simulator and export to configuration or script files.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables building and configuring NiCE CXone tenant resources—skills, outbound dialer config, agents, teams, campaigns, DNC groups, calling lists, and Studio IVRs—from plain English via MCP, with diagramming and server-side validation. Read-only operations and safe writes are supported, while destructive actions and dialing ignition are deliberately blocked.
      5
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables managing OpenI platform resources (login, query nodes, submit jobs, view logs) via natural language in Claude or Codex, following a kubectl/docker-style CLI.
      153
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to provision and manage cloud infrastructure and AI/ML workloads—such as GPUs, nodes, storage, networking, databases, Kubernetes, and training/inference resources—through natural language. It also provides a universal REST tool for authenticated access to the underlying cloud API.
      46
      14 npm
      Apache 2.0

    TDQS

    A4.1/5.0

    Scored across 8 tools

    Disambiguation4/5

    The three "build" tools (build_command, build_script, build_recipe) share a surface but are clearly delineated by scope: one command, many commands, or a prebuilt workflow, and the descriptions explicitly cross-reference each other. Discovery (list_commands), documentation (describe_command), and validation (check_command) each have distinct roles, leaving only mild build_script-vs-build_recipe overlap.

    Naming Consistency4/5

    All eight tools use a uniform raidcom_ prefix, snake_case, and verb-first style (build_, list_, describe_, check_). The only deviation is raidcom_model_limits, which is noun-based rather than verb_noun, but it remains readable and unambiguous.

    Tool Count5/5

    Eight tools is a well-scoped set for an offline raidcom command builder, and each tool earns its place: discovery, docs, single build, multi-step build, recipe listing, recipe build, validation, and model limits. No obvious padding or redundancy.

    Completeness4/5

    The lifecycle is well covered from discovery through description, validation, single-command build, multi-step scripts, and recipes, with no execution by design. Minor gaps remain, such as a tool to interpret raidcom error codes or the asynchronous command_status output the generated scripts rely on.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues