-
securityF
license-
qualityA Model Context Protocol (MCP) server implementation for interacting with Phabricator API. This server allows LLMs to interact with Phabricator through a standardized interface.
Provides seamless integration with Phabricator APIs, enabling task management, automation, and developer interaction through both synchronous and asynchronous clients with token-based authentication.
Conduit - The MCP Server for Phabricator and Phorge
Conduit is a Model Context Protocol (MCP) server that provides seamless integration with Phabricator and Phorge APIs, enabling advanced automation and interaction capabilities for developers and tools.
Conduit
Modern HTTP Client: Built with httpx for HTTP/2 support and better performance
MCP Integration: Ready-to-use MCP tools for task management
Type Safety: Full type hints for better development experience
Secure: Token-based authentication with environment variable configuration
Usage
Via uvx
You need to install uv first. If it is not installed, run the following command:
curl -LsSf https://astral.sh/uv/install.sh | sh
After installation, restart your shell or terminal to apply the environment variable changes.
Then run:
uvx --from git+https://github.com/mcpnow-io/conduit conduit-mcp
From Source
To install from source for development or contribution:
# Clone the repository
git clone https://github.com/mcpnow-io/conduit.git
cd conduit
# Install in development mode with all dependencies
pip install -e .[dev]
This will install the package in editable mode with all development dependencies.
Docker
We are still working on Docker support. We estimate it will be available soon.
As HTTP/SSE Server
Conduit can run as an HTTP/SSE server for multi-user scenarios. This mode allows multiple clients to connect simultaneously, each using their own authentication tokens.
conduit-mcp --host 127.0.0.1 --port 8000
When running as an HTTP server, authentication tokens are provided via HTTP headers instead of environment variables.
X-PHABRICATOR-TOKEN: your-32-character-token-here
Configuration
Before running the server, you need to set up the following environment variables:
Environment Variables
export PHABRICATOR_TOKEN=your-api-token-here
export PHABRICATOR_URL="https://your-phabricator-instance.com/api/"
export PHABRICATOR_PROXY="socks5://127.0.0.1:1080" # Optional, if your network is behind a firewall
export PHABRICATOR_DISABLE_CERT_VERIFY=1 # Optional, if your network is under HTTPS filter (WARNING: Disabling certificate verification can expose you to security risks. Only set this if you trust your network environment.)
Do note that in HTTPS/SSE mode, PHABRICATOR_TOKEN is NOT needed.
Getting Your API Token
Log into your Phabricator instance
Go to Settings > API Tokens
Generate a new token
Copy the 32-character token and use it as
PHABRICATOR_TOKEN
Contributing
There are many ways in which you can participate in this project, for example:
Submit bugs and feature requests, and help us verify as they are checked in
Review source code changes
Review the wiki and make pull requests for anything from typos to additional and new content
If you are interested in fixing issues and contributing directly to the code base, please see the document How to Contribute：
First-Time Setup - Now uses modern
pyproject.tomlfor dependency management
Development Setup
This project uses modern Python packaging with pyproject.toml for dependency management and build configuration. To set up for development:
Install the package in editable mode with development dependencies:
pip install -e .[dev]Run pre-commit hooks to ensure code quality:
pre-commit run -aRun tests with coverage:
coverage run -m pytest -s
License
Copyright (c) 2025 mpcnow.io. All rights reserved.
Licensed under the MIT license.
This server cannot be installed
remote-capable server
The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.
A Model Context Protocol server that integrates with Phabricator and Phorge APIs, enabling developers to automate and interact with task management systems through both synchronous and asynchronous clients.
Related MCP Servers
- -securityAlicense-qualityThis server implements the Model Context Protocol (MCP) to handle asynchronous tasks with real-time status tracking, robust error handling, and automatic resource management.
- -securityAlicense-qualityA Model Context Protocol server providing comprehensive task management capabilities with support for project organization, task tracking, and automatic PRD parsing into actionable items.Last updated -26MIT License
- AsecurityFlicenseAqualityA Model Context Protocol server that provides structured workflow tools for managing software development projects through different complexity levels, offering specialized modes for project planning, design, implementation, and documentation.Last updated -5331