Skip to main content
Glama

Related Servers

Alternatives to MCP_HCL

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      B
      maintenance
      Enables users to plan and stage H3C Cloud Lab topologies offline, inspect a running lab read-only through its telnet bridge, and change device configuration only via gated, receipt-backed operations that are disabled by default. Ships a DeepSeek Harness plugin bundle and also works with any stdio MCP client.
      55
      30 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables external agents to inspect and interact with a local single-project workbench via MCP, providing read-only tools for state, audit, resume, readiness, comparison, impact preview, and repair candidates, while proposals are saved for manual confirmation in the workbench.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to flatten and audit Bambu Studio presets, slice models with GUI-matching results, check STL/3MF/OBJ printability and part clearance, and compose non-destructive project edits without controlling printers.
      16
      353 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to load and edit saved 3MF projects, adjust slicer settings, and regenerate G-code using an explicitly bound installed native slicer engine.
      AGPL 3.0
    • 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

    TDQS

    B3.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: capabilities (meta), list_projects (enumerate), inspect_project (read), stage_add_device (add device), and stage_link (add link). The optional linking in stage_add_device could be confused with stage_link, but the descriptions clarify the primary actions and when to use each.

    Naming Consistency4/5

    All tools use the hcl_ prefix and snake_case, with operational tools following a verb_noun pattern (list_projects, inspect_project, stage_add_device, stage_link). hcl_capabilities is a noun phrase and breaks the verb-based convention, but only as a minor deviation.

    Tool Count5/5

    Five tools is well-scoped for a server focused on HCL project inspection and staged modifications. Each tool has a clear role, and there is no redundant or excessive tooling.

    Completeness3/5

    The surface covers listing, inspection, and additive staging (add device, add link), but lacks update, removal, or project creation/deletion operations. For a tool that manipulates HCL projects, these are notable gaps in lifecycle coverage.