grasp
Related Servers
Alternatives to grasp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables humans to review AI-generated code changes through a GUI: agents freeze git diffs and add findings/diagrams, while reviewers annotate and save decisions returned as an exact correction prompt.17302 npmISC
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to publish their work mid-task and hand it to a real human reviewer, who pins comments to the exact elements that are off and returns an approval verdict. The agent then iterates on that human feedback until the work is signed off.38 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to file work for review by a real human, who opens the published artifact and returns comments pinned to the exact elements that are off along with a verdict. The agent then revises and refiles, iterating through human checks until the work is approved.38 npmMIT
- AlicenseNot gradedqualityAmaintenanceLets AI coding agents hand off in-progress work to real human reviewers, who pin comments to the exact elements that are wrong and send back a verdict. The agent then revises and re-files until a person approves, so only human-signed-off output reaches the user.38 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to request real human reviews mid-task, receiving pinned feedback and approval verdicts so they can iterate until approved.38 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to publish their in-progress work and have a real human reviewer open it, pin comments to the exact elements that are off, and return a verdict. The agent then revises based on that pinned human feedback and refiles until a person approves.38 npmMIT
TDQS
Scored across 3 tools
Each tool occupies a distinct phase of the review loop: record_decision writes, show_behavior demonstrates evidence, get_review_feedback reads reviewer verdicts. No two tools could plausibly be selected for the same intent.
All three names follow a strict verb_noun snake_case pattern (get_review_feedback, record_decision, show_behavior). The verbs accurately signal direction (read/write/demonstrate).
Three tools is minimal but each maps to a necessary step in the submit-review-revise workflow, so nothing feels padded. It sits at the low end of the comfortable range, leaving little room for auxiliary operations.
The core loop (record decision, demonstrate behavior, collect feedback) is fully covered. Minor gaps exist around inspecting previously recorded decisions or withdrawing/amending one, but the workflow can proceed without those.