phab-arc-mcp
Provides tools for reviewing Phabricator revisions and creating draft inline comments, with context from linked Maniphest tasks.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@phab-arc-mcp Review revision D35297"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
phab-arc-mcp
phab-arc-mcp is a small MCP stdio server for reviewing Phabricator revisions.
What This Server Exposes
The public MCP surface is intentionally small:
review-phabinline-comments-phab
Related MCP server: AI Code Review MCP Server
What review-phab Does
review-phab is the tool you call when you want an AI reviewer to review a Differential properly.
You give it a revision ID like D35297. It fetches the revision title, summary, changed files, raw diff, and the linked Maniphest task context, then packages all of that together with the review prompt the model should use.
From a user point of view, this means you do not have to manually open the revision, copy the diff, inspect related tasks, and explain the background before asking for a review. The tool gives the model the code changes and the surrounding context in one shot.
That makes reviews more useful because the model can judge the change against the actual task being solved, not just the raw code diff. It can use the overall repository context to reason about likely bugs, regressions, and edge cases, and it can also check whether the revision actually does what the linked task says it should do. In practice.
After that, inline-comments-phab can take the review findings and create draft inline comments directly on the Differential.
Important details:
comments are created as draft inlines, not published comments
Installation
Requirements
Node.js 18 or newer
npmaccess to a Phabricator instance with the Conduit API enabled
a Conduit API token for an account that can read the revisions and tasks you want to review
1. Clone the repository
git clone https://github.com/wxomi/node-chat.git
cd mcp-phab2. Install dependencies
npm install3. Build the server
npm run buildThis produces the MCP server entrypoint at dist/server.js.
4. Configure environment variables
Set these before starting the server or before wiring it into your MCP client:
PHAB_API_TOKENrequired
primary token variable used by the server
CONDUIT_TOKENoptional alias for
PHAB_API_TOKEN
PHAB_CONDUIT_TOKENoptional alias for
PHAB_API_TOKEN
PHAB_CONDUIT_URIoptional
default:
https://phab.instahyre.com/should point to the base URL of your Phabricator instance
PHAB_ARC_TIMEOUT_MSoptional
default:
30000request timeout in milliseconds
Example:
export PHAB_CONDUIT_URI="https://phabricator.example.com/"
export PHAB_API_TOKEN="api-xxxxxxxxxxxxxxxx"
export PHAB_ARC_TIMEOUT_MS="30000"If you do not set PHAB_CONDUIT_URI, the server will try https://phab.instahyre.com/.
5. Start the server manually (optional)
You usually do not need this step when using the server through an MCP client. In the normal setup, the MCP client launches the stdio server process for you using its mcpServers configuration.
Run the built server manually only if you want to verify that the binary starts correctly:
npm startFor local development without building on every change:
npm run devThe server uses stdio transport, so manual npm start is optional and is not a required installation step.
Setup In An MCP Client
Codex / MCP config using the built server
{
"mcpServers": {
"phab-arc-mcp": {
"command": "node",
"args": ["/absolute/path/to/phab-arc-mcp/dist/server.js"],
"env": {
"PHAB_CONDUIT_URI": "https://phab.instahyre.com/",
"PHAB_API_TOKEN": "api-xxxxxxxxxxxxxxxx"
}
}
}
}Setup Checklist
Use this to verify the installation quickly:
npm installcompletes successfullynpm run buildcreatesdist/server.jsyour MCP client is configured with
PHAB_API_TOKENPHAB_CONDUIT_URIpoints to the correct Phabricator base URLthe MCP client can see the
review-phabandinline-comments-phabtools
Example Usage
Step 1: get review context
Call review-phab with:
{
"revision_id": "D35297"
}Notes
This server talks to Phabricator over the Conduit HTTP API.
A valid API token is required for every tool call.
Comments created by
inline-comments-phabare draft inlines and are not published automatically.
Available Tools
2 toolsinline-comments-phabA
Creates draft inline comments on a Differential revision from review findings JSON (does not publish).
Inputs: revision_id (required), findings, is_new_file, review_json, +2 more. Returns: diffId, results, isNewFile, revisionId, +3 more
review-phabA
Fetches the exact review prompt and revision context needed to review a Differential without MCP sampling.
Inputs: revision_id (required). Returns: next_action, revision_id, review_prompt, review_summary, +1 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Related MCP Connectors
MCP server for Riveter's enrichment, scraping, and monitoring API
MCP server for siGit (sigit.si): browse repos, search code, manage PRs/issues, web search.
A MCP server built for developers enabling Git based project management with project and personal…
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for code review using OpenRouter API. Supports local code review via MCP or web interface.12ISC
- AlicenseAqualityFmaintenanceA code review tool server based on Model Context Protocol (MCP) providing multi-dimensional code review and scoring.47 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for reviewing code changes using LLMs, supporting Copilot, Ollama, and OpenAI-compatible endpoints.MIT
- AlicenseAqualityDmaintenanceMCP server for Bitbucket Cloud, focused on pull-request review workflows116,532 npmMIT