A
licenseNot graded
qualityD
maintenanceExposes CodeRabbit IDE review comments as MCP tools and resources, allowing scanning, listing, and managing comments from clients like Cursor.
5 npm
1
MIT
Reado
Related Servers
Alternatives to Reado
- AlicenseAqualityDmaintenanceMCP server that exposes code review tasks from the Fix My Comments VS Code extension to AI agents, enabling them to list, retrieve, reply to, and update task statuses.411 npmMIT
- FlicenseAqualityCmaintenanceMCP server for exploring GitHub public data. It provides tools to fetch user profiles, list top repositories, and calculate language usage statistics, which AI agents can invoke dynamically.3-
Related Servers
- FlicenseNot gradedqualityBmaintenanceMCP server for AI DevTool workflow, exposing tools and resources for code review, repository chat, and repository operations.1-
- AlicenseNot gradedqualityBmaintenanceEnables continuing a local coding task from your own web ChatGPT account by exposing project-scoped read and apply tools over MCP, with no inference API dependency.MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to read a project's component tree and design tokens, edit React/TSX canvas frames, set props, apply auto layout and variants, add shader backgrounds, and capture screenshots, so agents can make design changes that are written back as reviewable code diffs and pull requests.MIT
Nolane Habitatofficial
FlicenseNot gradedqualityBmaintenanceProvides coding agents with a durable, revision-aware project workspace for semantic context, governed source changes, verification, task checkpoints, and observability through an MCP interface.1-- AlicenseNot gradedqualityCmaintenanceEnables external agents to inspect and interact with a local single-project workbench via MCP, providing read-only tools for state, audit, resume, readiness, comparison, impact preview, and repair candidates, while proposals are saved for manual confirmation in the workbench.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to inspect Runable projects over MCP, providing read-only access to project information and configuration via Runable's inspector.6 npmMIT
TDQS
A4.1/5.0
Scored across 27 tools
Disambiguation4/5
Most tools target a distinct resource+action, and the descriptions explicitly disambiguate the tricky pairs (browser_errors as a subset of browser_console, review_propose_comment vs review_propose, comment_add vs comment_reply vs review_propose_comment). The only real overlaps are browser_console/browser_errors and the read-only session_show vs review_context, both of which the descriptions diff explicitly. No tool pair appears interchangeable.
Naming Consistency4/5
Consistent snake_case verb_noun throughout, with clear domain prefixes (browser_*, task_*, comment_*, review_*, session_*). Minor deviations exist: comment_add/comment_reply use different verbs than the task_* lifecycle, and the summarize action is split across review_summarize_file and session_summarize rather than following one prefix scheme. Still highly predictable overall.
Tool Count3/5
27 tools is on the heavy side and just past the threshold where a set starts to feel bloated. However, the surface spans three genuinely distinct sub-domains (browser automation/inspection, guided-code-review lifecycle, task/comment/notification handling), so most tools earn their place rather than being redundant variants.
Completeness4/5
Browser control, task state transitions, comment creation, review routing, proposal and summarization are all covered with no obvious dead ends for the stated review-oriented purpose. The main gap is read/enumeration: there is no way to list or fetch tasks or existing comments (only add/reply/transition), so an agent depends on work arriving via the prompt.
Maintenance
ActivityActive
ResponsivenessUnresponsive