A
licenseNot graded
qualityB
maintenanceEnables MCP clients to read articles, preview Markdown output, and manage publishing tasks across supported platforms.
MIT
harness-manager
by x380kkm
Related Servers
Alternatives to harness-manager
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents to inspect repositories, manage Golden Packs, plan golden flows, and run asynchronous validation tasks over MCP, providing a deterministic foundation for project-specific workflows.MIT
- AlicenseCqualityDmaintenanceEnables access to Hanzo APIs and Platform capabilities via MCP, along with development tools for managing and improving projects.71MIT
- FlicenseNot gradedqualityDmaintenanceEnables Adobe Experience Platform and AEM content operations through a shared tool registry, exposing health checks, fragment search, sandbox management, dataset queries, and content fragment fetching via MCP and web interfaces.-
- AlicenseAqualityBmaintenanceEnables 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.19MIT
- AlicenseNot gradedqualityDmaintenanceEnables managing Hugo static site content via the MCP protocol, including schema and record CRUD, markdown generation, build, and publish.MIT
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.