Harness MCP
Related Servers
Alternatives to Harness MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that gives your agent a persistent project brain: vision, architecture decisions, conventions, roadmaps, and automatic session handoff.11 npm7MIT
- 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.16 npmMIT
- AlicenseNot gradedqualityBmaintenanceLocal 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.2,352 npm1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that bundles curated development rules and tools to teach AI agents universal coding standards, testing, planning, and requirements engineering.34 npmMIT
TDQS
Scored across 10 tools
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.
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.
10 tools is well-scoped for a harness management domain—enough to cover essential operations without being bloated or too few.
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.