phab-arc-mcp
Related Servers
Alternatives to phab-arc-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server for code review of Bitbucket Cloud pull requests: list PRs, read diffs, file contents and comments, and post review comments.611 npmISC
- AlicenseAqualityDmaintenanceMCP server for Bitbucket Cloud, focused on pull-request review workflows114,764 npmMIT
- FlicenseNot gradedqualityCmaintenanceA local MCP server that reads GitHub pull request diffs and coding standards, then posts inline review comments and full reviews to PRs via any MCP client.-
- AlicenseNot gradedqualityCmaintenanceMCP server for reviewing code changes using LLMs, supporting Copilot, Ollama, and OpenAI-compatible endpoints.MIT
- FlicenseNot gradedqualityFmaintenanceMCP server for code review using OpenRouter API. Supports local code review via MCP or web interface.12-
- AlicenseAqualityFmaintenanceA code review tool server based on Model Context Protocol (MCP) providing multi-dimensional code review and scoring.46 npmMIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one fetches review context, the other creates draft inline comments. There is no overlap in functionality, so an agent can easily select the right tool.
Tool names do not follow a consistent pattern. 'review-phab' is verb-noun, while 'inline-comments-phab' is noun-noun. The shared '-phab' suffix is a minor unifier but the lack of consistent verb usage makes naming unpredictable.
With only two tools, the server feels thin but not unreasonable for a narrowly focused review workflow. The count is at the borderline where it could benefit from additional operations, but it is not excessively sparse.
The tool surface has significant gaps. It creates draft comments but explicitly does not publish them, and there is no way to submit or finalize a review. This creates a dead end for the agent workflow, as the created comments cannot be acted upon fully.