Summary
Review comments that land under your name, not a bot's.
The per-user token is the part that matters. An assistant can read a differential, line the comments up against the code they refer to, and post back as you, so the review history stays legible to everyone else.
What it is
An MCP server for Phabricator covering both halves of the workflow, tasks and code review. Each user configures their own API token, so comments and approvals are attributed to them rather than to a shared service account.
What you get
- Task details with status, priority and the full comment thread
- Comments added to tasks, and people subscribed to them
- Differential revisions read in brief or with the code changes included
- Review feedback returned with the surrounding code, grouped into issues, suggestions, nits and other
- Comments added to a review, or targeted at a specific line
- Revisions accepted, or sent back with changes requested
Requirements
A personal Phabricator API token set in your MCP client. The server runs over HTTP/SSE on a default port, with stdio available for clients that need it.
Setup effort
One command plus a key — pip install -e ., then supply credentials