get-taskLABSCO 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
Build from source — git clone https://github.com/YushengAuggie/phabricator-mcp-server.git
USE CASES
01
Working through review feedback on your own diff
Pull the comments back with the code they point at, already grouped into issues, suggestions and nits.
02
Reviewing someone's change without leaving the editor
Read the revision with its code changes, then approve it or ask for changes.
03
Leaving a note on one specific line
Add an inline comment at the line rather than a general one at the bottom.
04
Catching up on a task before a standup
Read the task with its metadata and full comment thread in one call.
05
Looping the right person in
Subscribe a colleague to the task or the revision you are looking at.
06
Answering a question on a task
Post the reply as a task comment under your own account.
11 tools
Listed in project docs. Your client may show a different list.
add-task-commentsubscribe-to-taskget-differentialget-differential-detailedget-review-feedbackadd-differential-commentadd-inline-commentaccept-differentialrequest-changes-differentialsubscribe-to-differentialBEFORE YOU INSTALL
What to know first
Tools you get
11 tools named in the project's documentation.
Requires
- python on PATH
- Python 3.8+
- PHABRICATOR_TOKEN in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
TERMINAL
git clone https://github.com/YushengAuggie/phabricator-mcp-server.git
cd phabricator-mcp-server
pip install -e .
echo "PHABRICATOR_TOKEN=<YOUR_PHABRICATOR_TOKEN>" > .env
echo "PHABRICATOR_URL=<YOUR_PHABRICATOR_URL>/api/" >> .env
python3 start.py --mode httpMCP Clients
Claude Code
CLAUDE CODE · JSON
{
"mcpServers": {
"phabricator": {
"type": "sse",
"url": "http://localhost:8932/sse"
}
}
}Start the server first with python3 start.py --mode http (the last step above). It reads PHABRICATOR_TOKEN and PHABRICATOR_URL from the .env file created there, so this entry carries no token.
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"phabricator": {
"command": "python",
"args": [
"<YOUR_PATH_TO_PHABRICATOR_MCP_SERVER>/start.py",
"--mode",
"stdio"
],
"cwd": "<YOUR_PATH_TO_PHABRICATOR_MCP_SERVER>",
"env": {
"PHABRICATOR_TOKEN": "<YOUR_PHABRICATOR_TOKEN>",
"PHABRICATOR_URL": "<YOUR_SERVER_URL>/api/"
}
}
}
}<YOUR_PATH_TO_PHABRICATOR_MCP_SERVER> (in args and in cwd) is the full path of the folder the git clone above created, <YOUR_PHABRICATOR_TOKEN> your Phabricator API token (Settings → API Tokens), and <YOUR_SERVER_URL>/api/ your instance's API URL, which ends in /api/.
