pygithub-mcp-server
If you are the rightful owner of pygithub-mcp-server and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.
PyGithub MCP Server is a Model Context Protocol server that facilitates interaction with the GitHub API using PyGithub, enabling AI assistants to manage GitHub operations such as issues, repositories, and pull requests.
PyGithub MCP Server
A Model Context Protocol server that provides tools for interacting with the GitHub API through PyGithub. This server enables AI assistants to perform GitHub operations like managing issues, repositories, and pull requests.
Features
-
Modular Tool Architecture:
- Configurable tool groups that can be enabled/disabled
- Domain-specific organization (issues, repositories, etc.)
- Flexible configuration via file or environment variables
- Clear separation of concerns with modular design
- Easy extension with consistent patterns
-
Complete GitHub Issue Management:
- Create and update issues
- Get issue details and list repository issues
- Add, list, update, and delete comments
- Manage issue labels
- Handle assignees and milestones
-
Smart Parameter Handling:
- Dynamic kwargs building for optional parameters
- Proper type conversion for GitHub objects
- Validation for all input parameters
- Clear error messages for invalid inputs
-
Robust Implementation:
- Object-oriented GitHub API interactions via PyGithub
- Centralized GitHub client management
- Proper error handling and rate limiting
- Clean API abstraction through MCP tools
- Comprehensive pagination support
- Detailed logging for debugging
Documentation
Comprehensive guides are available in the docs/guides directory:
- error-handling.md: Error types, handling patterns, and best practices
- security.md: Authentication, access control, and content security
- tool-reference.md: Detailed tool documentation with examples
See these guides for detailed information about using the PyGithub MCP Server.
Usage Examples
Issue Operations
- Creating an Issue
{
"owner": "username",
"repo": "repository",
"title": "Issue Title",
"body": "Issue description",
"assignees": ["username1", "username2"],
"labels": ["bug", "help wanted"],
"milestone": 1
}
- Getting Issue Details
{
"owner": "username",
"repo": "repository",
"issue_number": 1
}
- Updating an Issue
{
"owner": "username",
"repo": "repository",
"issue_number": 1,
"title": "Updated Title",
"body": "Updated description",
"state": "closed",
"labels": ["bug", "wontfix"]
}
Comment Operations
- Adding a Comment
{
"owner": "username",
"repo": "repository",
"issue_number": 1,
"body": "This is a comment"
}
- Listing Comments
{
"owner": "username",
"repo": "repository",
"issue_number": 1,
"per_page": 10
}
- Updating a Comment
{
"owner": "username",
"repo": "repository",
"issue_number": 1,
"comment_id": 123456789,
"body": "Updated comment text"
}
Label Operations
- Adding Labels
{
"owner": "username",
"repo": "repository",
"issue_number": 1,
"labels": ["enhancement", "help wanted"]
}
- Removing a Label
{
"owner": "username",
"repo": "repository",
"issue_number": 1,
"label": "enhancement"
}
All operations handle optional parameters intelligently:
- Only includes provided parameters in API calls
- Converts primitive types to GitHub objects (e.g., milestone number to Milestone object)
- Provides clear error messages for invalid parameters
- Handles pagination automatically where applicable
Installation
- Create and activate a virtual environment:
uv venv
source .venv/bin/activate
- Install dependencies:
uv pip install -e .
Configuration
Basic Configuration
Add the server to your MCP settings (e.g., claude_desktop_config.json
or cline_mcp_settings.json
):
{
"mcpServers": {
"github": {
"command": "/path/to/repo/.venv/bin/python",
"args": ["-m", "pygithub_mcp_server"],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "your-token-here"
}
}
}
}
Tool Group Configuration
The server supports selectively enabling or disabling tool groups through configuration. You can configure this in two ways:
1. Configuration File
Create a JSON configuration file (e.g., pygithub_mcp_config.json
):
{
"tool_groups": {
"issues": {"enabled": true},
"repositories": {"enabled": true},
"pull_requests": {"enabled": false},
"discussions": {"enabled": false},
"search": {"enabled": true}
}
}
Then specify this file in your environment:
export PYGITHUB_MCP_CONFIG=/path/to/pygithub_mcp_config.json
2. Environment Variables
Alternatively, use environment variables to configure tool groups:
export PYGITHUB_ENABLE_ISSUES=true
export PYGITHUB_ENABLE_REPOSITORIES=true
export PYGITHUB_ENABLE_PULL_REQUESTS=false
By default, only the issues
tool group is enabled. See README.config.md
for more detailed configuration options.
Development
Testing
The project includes a comprehensive test suite:
# Run all tests
pytest
# Run tests with coverage report
pytest --cov
# Run specific test file
pytest tests/test_operations/test_issues.py
# Run tests matching a pattern
pytest -k "test_create_issue"
Note: Many tests are currently failing and under investigation. This is a known issue being actively worked on.
Testing with MCP Inspector
Test MCP tools during development using the MCP Inspector:
source .venv/bin/activate # Ensure venv is activated
npx @modelcontextprotocol/inspector -e GITHUB_PERSONAL_ACCESS_TOKEN=your-token-here uv run pygithub-mcp-server
Use the MCP Inspector's Web UI to:
- Experiment with available tools
- Test with real GitHub repositories
- Verify success and error cases
- Document working payloads
Project Structure
tests/
āāā unit/ # Fast tests without external dependencies
ā āāā config/ # Configuration tests
ā āāā tools/ # Tool registration tests
ā āāā ... # Other unit tests
āāā integration/ # Tests with real GitHub API
āāā issues/ # Issue tools tests
āāā ... # Other integration tests
src/
āāā pygithub_mcp_server/
āāā __init__.py
āāā __main__.py
āāā server.py # Server factory (create_server)
āāā version.py
āāā config/ # Configuration system
ā āāā __init__.py
ā āāā settings.py # Configuration management
āāā tools/ # Modular tool system
ā āāā __init__.py # Tool registration framework
ā āāā issues/ # Issue tools
ā āāā __init__.py
ā āāā tools.py # Issue tool implementations
āāā client/ # GitHub client functionality
ā āāā __init__.py
ā āāā client.py # Core GitHub client
ā āāā rate_limit.py # Rate limit handling
āāā converters/ # Data transformation
ā āāā __init__.py
ā āāā parameters.py # Parameter formatting
ā āāā responses.py # Response formatting
ā āāā common/ # Common converters
ā āāā issues/ # Issue-related converters
ā āāā repositories/ # Repository converters
ā āāā users/ # User-related converters
āāā errors/ # Error handling
ā āāā __init__.py
ā āāā exceptions.py # Custom exceptions
āāā operations/ # GitHub operations
ā āāā __init__.py
ā āāā issues.py
āāā schemas/ # Data models
ā āāā __init__.py
ā āāā base.py
ā āāā issues.py
ā āāā ...
āāā utils/ # General utilities
āāā __init__.py
āāā environment.py # Environment utilities
Troubleshooting
-
Server fails to start:
- Verify venv Python path in MCP settings
- Ensure all requirements are installed in venv
- Check GITHUB_PERSONAL_ACCESS_TOKEN is set and valid
-
Build errors:
- Use --no-build-isolation flag with uv build
- Ensure Python 3.10+ is being used
- Verify all dependencies are installed
-
GitHub API errors:
- Check token permissions and validity
- Review pygithub_mcp_server.log for detailed error traces
- Verify rate limits haven't been exceeded
Dependencies
- Python 3.10+
- MCP Python SDK
- Pydantic
- PyGithub
- UV package manager
License
MIT