A
licenseNot graded
qualityC
maintenanceAn MCP server that gives your agent a persistent project brain: vision, architecture decisions, conventions, roadmaps, and automatic session handoff.
17 npm
7
MIT
Harness MCP
Related Servers
Alternatives to Harness MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI coding agents structured access to a project's architecture, rules, modules, and technical decisions.MIT
- AlicenseAqualityCmaintenanceA single, queryable source of engineering constraints that coding agents consult at code-generation time, exposed over an MCP server.3Apache 2.0
- AlicenseNot gradedqualityCmaintenanceLocal-first MCP server that provides project context, verification gates, and structured tools for coding agents to discover knowledge, run diagnostics, and execute allowlisted commands within a repository.10 npmMIT
- AlicenseNot gradedqualityAmaintenanceLocal MCP server that gives AI agents a project constitution (LAWS.md), a code graph (Compass), and a spec-driven workflow — all 100% local with no LLM or cloud.124 npm3MIT
- AlicenseNot gradedqualityAmaintenanceProvides a provider-agnostic MCP server that owns task claims, action logs, role handoffs, and health-gate results so AI coding agents can move work through use-case, spec, design, build, and review stages with server-enforced evidence. It also exposes read-only skills for drafting use cases and specs, triaging bugs, answering code questions, and auditing itself.29 npmMIT
TDQS
A3.5/5.0
Scored across 10 tools
Disambiguation5/5
Each tool has a distinct purpose: status for overview, get_spec for reading the spec, list_pending for pending changes, verify for code comparison, reverse for inferring from code, propose_structure/change for generating proposals, sync_design_system for design integration, configure for settings, checkpoint for rollbacks. No overlap.
Naming Consistency5/5
All tools follow the 'harness_verb_noun' pattern with consistent snake_case. Single-word verbs like 'status', 'verify', 'reverse', 'configure', 'checkpoint' are acceptable and uniform.
Tool Count5/5
10 tools is well-scoped for a harness management domain—enough to cover essential operations without being bloated or too few.
Completeness4/5
Covers viewing, reading, proposing, verifying, reversing, syncing, configuring, and checkpointing. Missing explicit tools for approving/rejecting pending changes, which is a minor gap but most workflows are supported.
Maintenance
ActivityInactive
ResponsivenessNo issues