What can Phabricator do?

phabricator api endpoint abstraction via mcp protocol, phabricator task and revision querying with structured filtering, task and revision creation with field mapping, task and revision status/metadata updates with transaction support, repository and commit metadata retrieval, code review (differential) workflow automation, user and team information lookup with permission checking, custom field schema introspection and validation, phabricator event/activity feed querying with filtering

Phabricator

MCP ServerFree

** - Interacting with Phabricator API

Open Source

/ 100

9 capabilities

Capabilities9 decomposed

phabricator api endpoint abstraction via mcp protocol

Medium confidence

Exposes Phabricator REST API endpoints through the Model Context Protocol (MCP) server interface, translating HTTP-based Phabricator API calls into MCP tool definitions that LLM clients can invoke. Implements request routing, authentication token management, and response serialization to bridge Phabricator's native API with MCP-compatible clients (Claude, other LLM agents). Uses MCP server framework to register tools dynamically based on Phabricator API capabilities.

Solves for

I want my LLM agent to query Phabricator repositories, tasks, and code review data without making raw HTTP callsI need to integrate Phabricator into an MCP-based workflow where Claude or other LLM clients can fetch project metadataI want to abstract away Phabricator authentication and API versioning details from my agent logic

Best for

LLM agent developers building Phabricator-aware automation workflows

Teams using Claude or other MCP-compatible LLM clients who need Phabricator integration

DevOps engineers bridging legacy Phabricator instances with modern AI tooling

Requires

Phabricator instance with API access enabled

Valid Phabricator API token (conduit token)

Node.js 16+ (MCP server runtime)

Limitations

Requires active Phabricator instance with accessible API endpoint — no offline mode

MCP protocol overhead adds ~50-150ms per request compared to direct HTTP calls

Limited to Phabricator API capabilities exposed by the server implementation — custom Phabricator extensions may not be supported

What makes it unique

Implements MCP server pattern specifically for Phabricator, translating Conduit API (Phabricator's native RPC protocol) into MCP tool definitions that LLM clients can discover and invoke without custom HTTP handling. Manages Phabricator session tokens and request serialization internally.

vs alternatives

Enables direct Phabricator integration in MCP-compatible LLM workflows (Claude, etc.) without requiring custom HTTP client code or Phabricator API knowledge in agent logic, whereas direct API calls require agents to handle authentication and response parsing.

phabricator task and revision querying with structured filtering

Medium confidence

Provides MCP tools to query Phabricator tasks (Maniphest) and code revisions (Differential) using structured filters like status, assignee, project, and date ranges. Translates filter parameters into Phabricator Conduit API query constraints, executes searches, and returns paginated result sets with full task/revision metadata. Supports constraint composition for complex queries (e.g., 'open tasks assigned to user X in project Y modified in last 7 days').

Solves for

I want to fetch all open tasks assigned to a specific team member from my LLM agentI need to search for code revisions in a particular project that are awaiting reviewI want to query tasks by status, priority, and custom fields to build a dynamic dashboard or report

Best for

Developers building LLM-powered project management assistants

Teams automating task triage and code review workflows

Agents that need to understand current project state before taking actions

Requires

Phabricator instance with Maniphest (task) and/or Differential (code review) applications enabled

Valid API token with read permissions on target projects

Knowledge of Phabricator field names and constraint operators

Limitations

Query performance degrades with very large result sets (1000+ items) — pagination required

Custom Phabricator fields may not be queryable depending on server configuration

Filter syntax is Phabricator-specific — agents must understand Conduit constraint format or MCP tool must abstract it

What makes it unique

Abstracts Phabricator's Conduit constraint language into MCP tool parameters, allowing LLM agents to construct complex queries without learning Phabricator API syntax. Handles pagination and result aggregation transparently, returning normalized JSON structures.

vs alternatives

Simpler for LLM agents than raw Conduit API calls because constraints are expressed as JSON parameters rather than Phabricator's native constraint format, reducing cognitive load on agent logic.

task and revision creation with field mapping

Medium confidence

Enables MCP tools to create new Phabricator tasks (Maniphest) and code revisions (Differential) by accepting structured input (title, description, assignee, priority, custom fields) and mapping them to Phabricator's internal field schema. Handles field validation, custom field serialization, and returns the created object ID and metadata. Supports bulk creation via repeated tool calls.

Solves for

I want my LLM agent to automatically create a task when it detects a bug or feature requestI need to programmatically create code revisions from generated patches with proper metadataI want to create tasks with custom fields (e.g., 'estimated effort', 'customer impact') populated from agent reasoning

Best for

Agents automating issue/task creation from logs, alerts, or user input

CI/CD pipelines that need to create Phabricator tasks for failed builds or security findings

LLM-powered code review systems that generate revisions programmatically

Requires

Phabricator instance with write permissions for creating tasks/revisions

API token with 'create' capability on Maniphest and/or Differential

Knowledge of valid project IDs, user IDs, and custom field identifiers in target Phabricator instance

Limitations

Custom field types (select, date, etc.) require pre-configuration in Phabricator — MCP server must know field type mappings

No transaction-based creation — if creation fails mid-way, partial state may be left in Phabricator

Bulk creation is sequential (one tool call per task) — no batch API support

What makes it unique

Implements field mapping layer that translates generic task/revision input (title, description, assignee) into Phabricator's custom field schema, handling type coercion and validation. Exposes creation as MCP tools so agents can trigger task generation without understanding Phabricator's internal field structure.

vs alternatives

Abstracts Phabricator's complex custom field system from agent logic, whereas direct Conduit API calls require agents to know exact field keys and types for each Phabricator instance.

task and revision status/metadata updates with transaction support

Medium confidence

Provides MCP tools to update task and revision status, assignee, priority, and custom fields via Phabricator's transaction API. Accepts update parameters (new status, assignee, priority, custom field values) and applies them as atomic transactions, returning the updated object and transaction history. Supports conditional updates (e.g., 'only update if current status is X').

Solves for

I want my agent to automatically close a task when a related code revision is mergedI need to reassign tasks to different team members based on workload or expertiseI want to update task priority or custom fields in response to new information or agent reasoning

Best for

Agents automating task lifecycle management (triage, assignment, closure)

Workflows that synchronize Phabricator state with external systems (Slack, GitHub, Jira)

LLM-powered code review systems that update revision status based on review feedback

Requires

Phabricator instance with write permissions for updating tasks/revisions

API token with 'edit' capability on target objects

Valid target object IDs (task ID or revision ID)

Limitations

Transaction API is asynchronous — updates may not be immediately visible in subsequent queries

Conditional updates require pre-fetching current state; no atomic compare-and-swap primitive

Custom field updates may fail silently if field type validation fails on server side

What makes it unique

Leverages Phabricator's transaction system to apply updates atomically, ensuring audit trail and consistency. MCP tool interface abstracts transaction details from agents, exposing simple update parameters that map to underlying transactions.

vs alternatives

Provides transaction-based updates with audit trails, whereas simple REST PATCH calls lack Phabricator's built-in change tracking and may not guarantee consistency in concurrent scenarios.

repository and commit metadata retrieval

Medium confidence

Exposes MCP tools to fetch Phabricator repository metadata (name, VCS type, clone URLs, branches) and commit/changeset information (author, message, affected files, diff stats). Queries Phabricator's Diffusion application via Conduit API and returns structured commit data including file changes, line counts, and associated tasks/revisions. Supports filtering by branch, date range, or author.

Solves for

I want my agent to understand the structure and history of a Phabricator-hosted repositoryI need to fetch recent commits and their associated code reviews to provide context to an LLMI want to query which commits touched specific files or were authored by specific developers

Best for

Agents building code context for LLM-based code analysis or documentation generation

CI/CD systems that need to correlate commits with Phabricator tasks and revisions

Teams auditing code changes and their associated metadata

Requires

Phabricator instance with Diffusion (repository) application enabled

Repository indexed and tracked in Phabricator

API token with read permissions on target repository

Limitations

Diff content is not returned by default — only file names and line counts (full diffs require separate API call)

Large repositories may have slow commit history queries; pagination required for 1000+ commits

Branch filtering depends on Phabricator's branch tracking configuration

What makes it unique

Integrates Phabricator's Diffusion API to provide normalized commit metadata with associated task/revision links, enabling agents to understand code changes in the context of project management. Handles repository lookup by name or ID and abstracts Phabricator's internal commit representation.

vs alternatives

Provides unified access to commits and their associated Phabricator metadata (linked tasks, revisions) in a single query, whereas querying Git directly requires separate lookups to correlate with Phabricator data.

code review (differential) workflow automation

Medium confidence

Provides MCP tools to manage code review workflows in Phabricator Differential: create revisions from diffs, request reviewers, add inline comments, approve/request changes, and transition revision status (draft → review → accepted → closed). Implements reviewer assignment logic, comment threading, and status transition validation. Supports bulk reviewer assignment and automated approval based on rules (e.g., 'auto-approve if all reviewers approved').

Solves for

I want my agent to create a code review for a generated patch and assign it to specific reviewersI need to automate code review approval workflows based on reviewer feedback or automated checksI want to add inline comments to code revisions programmatically based on static analysis or LLM reasoning

Best for

LLM-powered code generation systems that need to submit generated code for review

CI/CD pipelines automating code review workflows (e.g., auto-approve if tests pass)

Agents that analyze code and provide feedback via Phabricator comments

Requires

Phabricator instance with Differential (code review) application enabled

API token with 'create' and 'edit' permissions on revisions

Valid reviewer user IDs and repository configuration

Limitations

Inline comments require line numbers and file paths — must match revision's diff structure exactly

Reviewer assignment validation is server-side; invalid reviewer IDs fail at submission time

No support for requesting changes with severity levels or blocking vs. non-blocking feedback

What makes it unique

Abstracts Phabricator's Differential workflow (revision creation, reviewer assignment, inline comments, status transitions) into discrete MCP tools, enabling agents to manage code reviews without understanding Phabricator's revision lifecycle. Handles diff parsing and line-number mapping internally.

vs alternatives

Provides high-level code review workflow tools (create revision, request review, approve) whereas raw Conduit API requires agents to manage revision state and comment threading manually.

user and team information lookup with permission checking

Medium confidence

Exposes MCP tools to query Phabricator users and teams (projects with members), retrieve user profiles (name, email, avatar, status), and check permissions (whether a user can access a specific project or object). Queries Phabricator's user and project management APIs and returns normalized user/team data. Supports filtering by username, email, or team membership.

Solves for

I want my agent to look up a user's email or contact info from their Phabricator usernameI need to verify that a user has permission to access a specific project before assigning them a taskI want to find all members of a team to distribute work or send notifications

Best for

Agents that need to validate user identities or permissions before taking actions

Workflow systems that distribute tasks to team members based on availability or expertise

Integration systems that need to map Phabricator users to external systems (Slack, email, etc.)

Requires

Phabricator instance with user management enabled

API token with read permissions on user and project data

Limitations

User status (online/offline) is not real-time — reflects last activity, not current presence

Permission checking is coarse-grained (project-level) — no fine-grained object-level permissions

Team membership is static snapshot; changes require re-querying

What makes it unique

Combines user profile lookup with permission checking in a single MCP tool interface, allowing agents to validate both identity and access rights before assigning tasks or sharing information. Abstracts Phabricator's user/project hierarchy.

vs alternatives

Provides permission-aware user lookup, whereas simple user directory queries lack access control context and may expose sensitive information to unauthorized agents.

custom field schema introspection and validation

Medium confidence

Provides MCP tools to query Phabricator's custom field definitions (for tasks, revisions, etc.), retrieve field metadata (type, required, allowed values, validation rules), and validate input values against field schemas. Enables agents to understand what custom fields are available and what values are valid before attempting to create or update objects. Returns field type information (text, select, date, etc.) and constraints.

Solves for

I want my agent to discover what custom fields are available in Phabricator before creating a taskI need to validate that a custom field value is acceptable (e.g., within allowed enum values) before submittingI want to understand field types and constraints so I can guide an LLM to generate valid input

Best for

Agents that need to adapt to different Phabricator configurations without hardcoding field names

Systems building dynamic forms or input validation based on Phabricator schema

LLM-powered task creation systems that need to understand field constraints

Requires

Phabricator instance with custom fields configured

API token with read permissions on field definitions

Limitations

Schema introspection is read-only — cannot modify field definitions via MCP

Custom field visibility may be restricted by permissions — some fields may not be queryable

Field constraints (regex, min/max) are not always exposed via API — validation may be incomplete

What makes it unique

Exposes Phabricator's custom field schema as queryable MCP tools, enabling agents to dynamically adapt to different Phabricator configurations without hardcoding field names or types. Provides field validation context that agents can use to generate valid input.

vs alternatives

Allows agents to discover and validate custom fields at runtime, whereas hardcoding field names requires manual configuration per Phabricator instance and breaks when fields change.

phabricator event/activity feed querying with filtering

Medium confidence

Provides MCP tools to query Phabricator's activity feed (recent changes to tasks, revisions, comments, etc.) with filters for object type, user, date range, and action type. Returns paginated activity events with metadata (who changed what, when, on which object). Enables agents to monitor project activity, detect changes, and react to events. Supports filtering by project, user, or specific object types.

Solves for

I want my agent to monitor recent changes to tasks and revisions in a projectI need to detect when a specific task was updated and by whomI want to build a notification system that reacts to Phabricator activity (e.g., 'notify team when task is closed')

Best for

Agents building activity monitoring or notification systems

Workflow systems that react to Phabricator state changes

Audit and compliance systems tracking project activity

Requires

Phabricator instance with activity feed enabled

API token with read permissions on activity data

Limitations

Activity feed is not real-time — events may be delayed by seconds to minutes

Feed retention is limited by Phabricator configuration — old events may be purged

Filtering is coarse-grained (project, user, type) — no fine-grained event filtering

What makes it unique

Exposes Phabricator's activity feed as queryable MCP tools with filtering, enabling agents to monitor and react to project changes without polling individual objects. Abstracts feed pagination and event serialization.

vs alternatives

Provides centralized activity monitoring via feed queries, whereas querying individual objects requires agents to track state changes manually or implement polling logic.

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with Phabricator, ranked by overlap. Discovered automatically through the match graph.

MCP Server24

Todoist

** - Full implementation of Todoist Rest API for MCP server

task-creation-via-mcp-protocoltask-update-and-modificationtask-retrieval-and-filtering

3 shared capabilities

MCP Server25

Taskeract

** - Official Taskeract MCP Server for integrating your [Taskeract](https://www.taskeract.com/) project tasks and load the context of your tasks into your MCP enabled app.

mcp-protocol-task-resource-exposuretaskeract-project-task-enumeration

2 shared capabilities

MCP Server26

Buildable

** - Official MCP server for Buildable AI-powered development platform. Enables AI assistants to manage tasks, track progress, get project context, and collaborate with humans on software projects.

task-management-via-mcp-protocol

1 shared capability

MCP Server26

targetprocess-mcp-server

MCP server for Tartget Process

targetprocess-resource-crud-operations

1 shared capability

MCP Server23

Routine

** - MCP server to interact with [Routine](https://routine.co/): calendars, tasks, notes, etc.

task-management-via-mcp

1 shared capability

MCP Server43

@taazkareem/clickup-mcp-server

ClickUp MCP Server - Powering AI Agents with full ClickUp task, document, and chat management capabilities.

task-creation-and-management-via-mcp

1 shared capability

Best For

✓LLM agent developers building Phabricator-aware automation workflows
✓Teams using Claude or other MCP-compatible LLM clients who need Phabricator integration
✓DevOps engineers bridging legacy Phabricator instances with modern AI tooling
✓Developers building LLM-powered project management assistants
✓Teams automating task triage and code review workflows
✓Agents that need to understand current project state before taking actions
✓Agents automating issue/task creation from logs, alerts, or user input
✓CI/CD pipelines that need to create Phabricator tasks for failed builds or security findings

Known Limitations

⚠Requires active Phabricator instance with accessible API endpoint — no offline mode
⚠MCP protocol overhead adds ~50-150ms per request compared to direct HTTP calls
⚠Limited to Phabricator API capabilities exposed by the server implementation — custom Phabricator extensions may not be supported
⚠No built-in caching or rate-limiting — relies on client-side throttling or Phabricator's own rate limits
⚠Authentication token must be provisioned externally and passed to MCP server at startup
⚠Query performance degrades with very large result sets (1000+ items) — pagination required

Requirements

Phabricator instance with API access enabledValid Phabricator API token (conduit token)Node.js 16+ (MCP server runtime)Network connectivity to Phabricator API endpointPhabricator instance with Maniphest (task) and/or Differential (code review) applications enabledValid API token with read permissions on target projectsKnowledge of Phabricator field names and constraint operatorsPhabricator instance with write permissions for creating tasks/revisions

Input / Output

Accepts: MCP tool call with JSON parameters (repository names, task IDs, revision identifiers, query filters), JSON filter object with keys like 'status', 'assignee', 'project', 'createdAfter', 'createdBefore', 'priority', JSON object with keys: 'title', 'description', 'assignee' (user ID), 'project' (project ID), 'priority' (int), 'customFields' (object), JSON object with keys: 'objectId', 'status' (string), 'assignee' (user ID), 'priority' (int), 'customFields' (object), 'comments' (string), JSON object with keys: 'repositoryId' or 'repositoryName', 'branch' (optional), 'limit' (int), 'offset' (int), 'authorFilter' (optional), JSON object with keys: 'diff' (unified diff string), 'title', 'summary', 'reviewers' (array of user IDs), 'inlineComments' (array of {file, line, comment}), 'status' (draft/review/accepted/closed), JSON object with keys: 'username' or 'userId' or 'email' (for user lookup), 'projectId' (for permission check), 'teamId' (for membership query), JSON object with keys: 'objectType' (e.g., 'task', 'revision'), 'fieldKey' (optional, for single field lookup), JSON object with keys: 'projectId' (optional), 'userId' (optional), 'objectType' (optional), 'dateAfter' (optional), 'limit' (int), 'offset' (int)

Produces: JSON-serialized Phabricator API responses (task objects, commit metadata, repository info, user data), JSON array of task/revision objects with fields: id, title, status, assignee, priority, dateCreated, dateModified, custom fields, JSON object with 'id' (task/revision ID), 'phid' (Phabricator ID), 'uri' (web URL), and created object metadata, JSON object with updated object metadata, transaction ID, and transaction history (who changed what, when), JSON array of commit objects with fields: id, hash, author, message, dateCreated, files (array of {name, additions, deletions}), associatedRevisions, JSON object with revision ID, PHID, URI, status, reviewer list, and comment thread data, JSON object with user fields: id, username, realName, email, avatar, status, or team fields: id, name, members (array of user IDs), JSON array of field objects with keys: key, label, type (text/select/date/etc.), required (bool), description, options (for select fields), JSON array of activity events with fields: id, actor (user ID), action (created/updated/commented), objectType, objectId, timestamp, details

UnfragileRank

Adoption15%(25% weight)

Quality19%(25% weight)

Ecosystem30%(15% weight)

Match Graph25%(30% weight)

Freshness75%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

9 capabilities

Visit Phabricator→

About

** - Interacting with Phabricator API

Alternatives to Phabricator

IntelliCode46Extension

AI-assisted development

Compare →

GitHub Copilot Chat49Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot48Extension

Your AI pair programmer

Compare →

Claude Code for VS Code48Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

Are you the builder of Phabricator?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

github awesome

Looking for something else?

Search →

Capabilities9 decomposed

phabricator api endpoint abstraction via mcp protocol

Medium confidence

Solves for

Best for

LLM agent developers building Phabricator-aware automation workflows

Teams using Claude or other MCP-compatible LLM clients who need Phabricator integration

DevOps engineers bridging legacy Phabricator instances with modern AI tooling

Requires

Phabricator instance with API access enabled

Valid Phabricator API token (conduit token)

Node.js 16+ (MCP server runtime)

Limitations

Requires active Phabricator instance with accessible API endpoint — no offline mode

MCP protocol overhead adds ~50-150ms per request compared to direct HTTP calls

Limited to Phabricator API capabilities exposed by the server implementation — custom Phabricator extensions may not be supported

What makes it unique

vs alternatives

phabricator task and revision querying with structured filtering

Medium confidence

Solves for

Best for

Developers building LLM-powered project management assistants

Teams automating task triage and code review workflows

Agents that need to understand current project state before taking actions

Requires

Phabricator instance with Maniphest (task) and/or Differential (code review) applications enabled

Valid API token with read permissions on target projects

Knowledge of Phabricator field names and constraint operators

Limitations

Query performance degrades with very large result sets (1000+ items) — pagination required

Custom Phabricator fields may not be queryable depending on server configuration

Filter syntax is Phabricator-specific — agents must understand Conduit constraint format or MCP tool must abstract it

What makes it unique

vs alternatives

Simpler for LLM agents than raw Conduit API calls because constraints are expressed as JSON parameters rather than Phabricator's native constraint format, reducing cognitive load on agent logic.

task and revision creation with field mapping

Medium confidence

Solves for

Best for

Agents automating issue/task creation from logs, alerts, or user input

CI/CD pipelines that need to create Phabricator tasks for failed builds or security findings

LLM-powered code review systems that generate revisions programmatically

Requires

Phabricator instance with write permissions for creating tasks/revisions

API token with 'create' capability on Maniphest and/or Differential

Knowledge of valid project IDs, user IDs, and custom field identifiers in target Phabricator instance

Limitations

Custom field types (select, date, etc.) require pre-configuration in Phabricator — MCP server must know field type mappings

No transaction-based creation — if creation fails mid-way, partial state may be left in Phabricator

Bulk creation is sequential (one tool call per task) — no batch API support

What makes it unique

vs alternatives

Abstracts Phabricator's complex custom field system from agent logic, whereas direct Conduit API calls require agents to know exact field keys and types for each Phabricator instance.

task and revision status/metadata updates with transaction support

Medium confidence

Solves for

Best for

Agents automating task lifecycle management (triage, assignment, closure)

Workflows that synchronize Phabricator state with external systems (Slack, GitHub, Jira)

LLM-powered code review systems that update revision status based on review feedback

Requires

Phabricator instance with write permissions for updating tasks/revisions

API token with 'edit' capability on target objects

Valid target object IDs (task ID or revision ID)

Limitations

Transaction API is asynchronous — updates may not be immediately visible in subsequent queries

Conditional updates require pre-fetching current state; no atomic compare-and-swap primitive

Custom field updates may fail silently if field type validation fails on server side

What makes it unique

vs alternatives

Provides transaction-based updates with audit trails, whereas simple REST PATCH calls lack Phabricator's built-in change tracking and may not guarantee consistency in concurrent scenarios.

repository and commit metadata retrieval

Medium confidence

Solves for

Best for

Agents building code context for LLM-based code analysis or documentation generation

CI/CD systems that need to correlate commits with Phabricator tasks and revisions

Teams auditing code changes and their associated metadata

Requires

Phabricator instance with Diffusion (repository) application enabled

Repository indexed and tracked in Phabricator

API token with read permissions on target repository

Limitations

Diff content is not returned by default — only file names and line counts (full diffs require separate API call)

Large repositories may have slow commit history queries; pagination required for 1000+ commits

Branch filtering depends on Phabricator's branch tracking configuration

What makes it unique

vs alternatives

code review (differential) workflow automation

Medium confidence

Solves for

Best for

LLM-powered code generation systems that need to submit generated code for review

CI/CD pipelines automating code review workflows (e.g., auto-approve if tests pass)

Agents that analyze code and provide feedback via Phabricator comments

Requires

Phabricator instance with Differential (code review) application enabled

API token with 'create' and 'edit' permissions on revisions

Valid reviewer user IDs and repository configuration

Limitations

Inline comments require line numbers and file paths — must match revision's diff structure exactly

Reviewer assignment validation is server-side; invalid reviewer IDs fail at submission time

No support for requesting changes with severity levels or blocking vs. non-blocking feedback

What makes it unique

vs alternatives

Provides high-level code review workflow tools (create revision, request review, approve) whereas raw Conduit API requires agents to manage revision state and comment threading manually.

user and team information lookup with permission checking

Medium confidence

Solves for

Best for

Agents that need to validate user identities or permissions before taking actions

Workflow systems that distribute tasks to team members based on availability or expertise

Integration systems that need to map Phabricator users to external systems (Slack, email, etc.)

Requires

Phabricator instance with user management enabled

API token with read permissions on user and project data

Limitations

User status (online/offline) is not real-time — reflects last activity, not current presence

Permission checking is coarse-grained (project-level) — no fine-grained object-level permissions

Team membership is static snapshot; changes require re-querying

What makes it unique

vs alternatives

Provides permission-aware user lookup, whereas simple user directory queries lack access control context and may expose sensitive information to unauthorized agents.

custom field schema introspection and validation

Medium confidence

Solves for

Best for

Agents that need to adapt to different Phabricator configurations without hardcoding field names

Systems building dynamic forms or input validation based on Phabricator schema

LLM-powered task creation systems that need to understand field constraints

Requires

Phabricator instance with custom fields configured

API token with read permissions on field definitions

Limitations

Schema introspection is read-only — cannot modify field definitions via MCP

Custom field visibility may be restricted by permissions — some fields may not be queryable

Field constraints (regex, min/max) are not always exposed via API — validation may be incomplete

What makes it unique

vs alternatives

Allows agents to discover and validate custom fields at runtime, whereas hardcoding field names requires manual configuration per Phabricator instance and breaks when fields change.

phabricator event/activity feed querying with filtering

Medium confidence

Solves for

Best for

Agents building activity monitoring or notification systems

Workflow systems that react to Phabricator state changes

Audit and compliance systems tracking project activity

Requires

Phabricator instance with activity feed enabled

API token with read permissions on activity data

Limitations

Activity feed is not real-time — events may be delayed by seconds to minutes

Feed retention is limited by Phabricator configuration — old events may be purged

Filtering is coarse-grained (project, user, type) — no fine-grained event filtering

What makes it unique

vs alternatives

Provides centralized activity monitoring via feed queries, whereas querying individual objects requires agents to track state changes manually or implement polling logic.

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to Phabricator

IntelliCode46Extension

AI-assisted development

Compare →

GitHub Copilot Chat49Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot48Extension

Your AI pair programmer

Compare →

Claude Code for VS Code48Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

Phabricator

Capabilities9 decomposed

phabricator api endpoint abstraction via mcp protocol

phabricator task and revision querying with structured filtering

task and revision creation with field mapping

task and revision status/metadata updates with transaction support

repository and commit metadata retrieval

code review (differential) workflow automation

user and team information lookup with permission checking

custom field schema introspection and validation

phabricator event/activity feed querying with filtering

Related Artifactssharing capabilities

Todoist

Taskeract

Buildable

targetprocess-mcp-server

Routine

@taazkareem/clickup-mcp-server

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

About

Categories

Alternatives to Phabricator

Are you the builder of Phabricator?

Get the weekly brief

Data Sources

Phabricator

Capabilities9 decomposed

phabricator api endpoint abstraction via mcp protocol

phabricator task and revision querying with structured filtering

task and revision creation with field mapping

task and revision status/metadata updates with transaction support

repository and commit metadata retrieval

code review (differential) workflow automation

user and team information lookup with permission checking

custom field schema introspection and validation

phabricator event/activity feed querying with filtering

Related Artifactssharing capabilities

Todoist

Taskeract

Buildable

targetprocess-mcp-server

Routine

@taazkareem/clickup-mcp-server

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

About

Categories

Alternatives to Phabricator

Are you the builder of Phabricator?

Get the weekly brief

Data Sources