Skip to main content
Glama
x380kkm

harness-manager

by x380kkm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to harness-manager

No user-submitted related servers found.

    Related Servers

    • workspace-mcp

      MarcoCaamal
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to safely read, write, edit, search, and optionally run commands within one or more named project workspaces, while maintaining a work journal and tracking changes.
      19
      MIT

    • hugo-mcp-server

      klauri
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables managing Hugo static site content via the MCP protocol, including schema and record CRUD, markdown generation, build, and publish.
      -

    • memorybank-mcp

      maxweb4u
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to work with a Memory Bank through routing, section-aware reading, governance validation, dependency graph traversal, full-text search, change tracking, and document creation or promotion.
      59 npm
      MIT
    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

    C2.7/5.0

    Scored across 44 tools

    Disambiguation2/5

    Multiple tools have overlapping boundaries: host_inspect vs host_preview both return diffs, codex_list vs codex_groups both enumerate Codex content, and content_read/content_open/content_snapshot/content_continue cover similar read/snapshot behavior. The domain prefixes help, but with 44 tools an agent will often be unsure which variant is the right one.

    Naming Consistency4/5

    Most tools follow a consistent [resource]_[action] snake_case pattern with clear prefixes like host_preview, document_apply, and context_preview. A few names are result-oriented rather than action-oriented (catalog_graph, card_relations, host_status, agent_capabilities) and statistics_reads is an odd variant, but the overall style is predictable.

    Tool Count2/5

    44 tools is well beyond the 25+ threshold for a practical MCP surface, even though the server spans multiple subsystems. Many tools are fine-grained lifecycle variants of preview/apply/read that could be consolidated into fewer, clearer entry points.

    Completeness3/5

    The set covers host management, card relations, catalog/document reads, content snapshots, and code/x import with mostly consistent preview/apply flows. However, some lifecycles are asymmetric: usage has no direct remove/apply counterpart to context_preview_remove/context_apply, and module_apply has no explicit removal path visible, so coverage is not uniformly complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources