Radicle + GitHub MCP Server
Used as a runtime for the GitHub MCP server component, required as a prerequisite for running the integration.
Supports Git operations through Radicle, including repository initialization, cloning, status checking, and pushing changes to the network.
Provides tools for managing GitHub repositories, issues, pull requests, and file operations. Enables creating, forking, and cloning repositories, managing issues and PRs, reading and writing files, searching across repositories, and handling user and organization information.
Required as a runtime environment for the Radicle MCP server component, with Python 3.8+ specifically mentioned as a prerequisite.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Radicle + GitHub MCP Server sync issues between my GitHub repo and Radicle project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Radicle + GitHub MCP Server
A Model Context Protocol (MCP) server setup that provides tools for interacting with both Radicle (peer-to-peer code collaboration) and GitHub through a unified interface.
Features
This setup includes two MCP servers:
🌟 Radicle MCP Server (Python)
Repository Management: Initialize, clone, and inspect Radicle repositories
Synchronization: Sync repositories with the Radicle network
Patches & Issues: List and manage patches and issues
Node Information: Get node ID and remote information
Help System: Access Radicle command documentation
🔄 GitHub Integration: Bidirectional sync of issues and PRs between GitHub and Radicle
🐙 GitHub MCP Server (Official)
Repository Operations: Create, fork, clone GitHub repositories
Issue Management: Create, update, and manage GitHub issues
Pull Requests: Manage pull requests and reviews
File Operations: Read, write, and manage repository files
Search: Search repositories, issues, and code
User Management: Manage user and organization information
🔗 GitHub ↔ Radicle Synchronization
Bidirectional Issue Sync: Automatically sync issues between platforms
Idempotent Operations: Safe to run multiple times without duplicates
Metadata Preservation: Maintains original author, links, and timestamps
Mapping Database: Tracks relationships between GitHub and Radicle items
MCP Integration: Available as AI assistant tools
Related MCP server: GitHub MCP Server
Available Tools
Repository Operations
rad_init: Initialize a new Radicle repositoryrad_clone: Clone an existing repository by RIDrad_status: Get repository status and informationrad_sync: Sync repository with the networkrad_push: Push changes to the network
Collaboration Features
rad_patch_list: List patches (pull requests) in a repositoryrad_issue_list: List issues in a repositoryrad_remote_list: List remotes/nodes for a repository
Node & Identity
rad_id: Get your Radicle node IDrad_help: Get help for Radicle commands
Prerequisites
Radicle CLI: Ensure the
radcommand is installed and available in your PATH# Install Radicle (see https://radicle.xyz for installation instructions) curl -sSf https://install.radicle.xyz | shDeno: For running the GitHub MCP server
# Install Deno curl -fsSL https://deno.land/install.sh | shPython Environment: Python 3.8+ with the MCP library
pip install mcpGitHub Personal Access Token: For GitHub integration
Create a new token with repo, issues, and pull request permissions
Set as environment variable:
GITHUB_PERSONAL_ACCESS_TOKEN
Installation
Clone this repository
Install dependencies:
pip install -e .Install the official GitHub MCP server:
deno install -g --name github-mcp npm:@modelcontextprotocol/server-githubRun the setup script:
python setup_mcp.py
Usage
Quick Setup
# Set your GitHub token
export GITHUB_PERSONAL_ACCESS_TOKEN=your_token_here
# Run the setup script
python setup_mcp.pyGitHub ↔ Radicle Sync
# Test sync connectivity
python demo_sync.py
# Create a test issue (optional)
python create_test_issue.py
# Run full sync
python github_radicle_sync.py
# Or use CLI interface
python sync_cli.py --repo owner/repo --dry-run
python sync_cli.py --repo owner/repo --issues-onlyMCP Integration
The sync functionality is available as MCP tools:
github_sync_test: Test connectivitygithub_sync_issues: Sync issues onlygithub_sync_full: Full bidirectional sync
See SYNC_README.md for detailed sync documentation.
As Standalone Servers
# Radicle MCP Server
python -m radicle_mcp.server
# GitHub MCP Server
github-mcpWith Claude Desktop
The setup script automatically creates the configuration. Your claude_desktop_config.json will include:
{
"mcpServers": {
"radicle-mcp": {
"command": "/path/to/python",
"args": ["-m", "radicle_mcp.server"]
},
"github-mcp": {
"command": "/path/to/github-mcp",
"args": [],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_PERSONAL_ACCESS_TOKEN}"
}
}
}
}VS Code Integration
This project includes VS Code configuration for debugging the MCP server. Use the provided mcp.json file to connect compatible MCP clients.
Example Commands
Once connected to an MCP client, you can use natural language to interact with both platforms:
Radicle Operations
"Initialize a new Radicle repository called 'my-project'"
"Clone the repository with RID rad:z2..."
"Show me the current patches in this repository"
"Sync this repository with the network"
"What's my Radicle node ID?"
GitHub Operations
"Create a new GitHub repository called 'awesome-project'"
"List my recent GitHub repositories"
"Create an issue titled 'Bug fix needed'"
"Show me open pull requests in my repository"
"Search for repositories related to 'machine learning'"
Cross-Platform Workflows
"Publish this Radicle repository to GitHub"
"Sync issues between Radicle and GitHub"
"Compare this repository on both platforms"
Development
Running Tests
python -m pytest tests/Code Style
black src/
flake8 src/Project Structure
radicle-mcp/
├── src/radicle_mcp/
│ ├── __init__.py
│ └── server.py # Main MCP server implementation
├── .vscode/
│ └── mcp.json # VS Code MCP configuration
├── .github/
│ └── copilot-instructions.md
├── pyproject.toml # Project configuration
└── README.mdContributing
Fork the repository
Create a feature branch
Make your changes
Add tests if applicable
Submit a pull request
License
MIT License - see LICENSE file for details
Related Links
Available Tools
11 toolsrad_cloneB
Clone a Radicle repository.
Args:
rid: Repository ID (RID) to clone
path: Optional path where to clone the repository
Inputs: rid (required), path. Returns: result
rad_helpB
Get help for Radicle commands.
Args:
command: Specific command to get help for (optional)
Inputs: command. Returns: result
rad_idB
Get the current node's Radicle ID.
Inputs: no named parameters. Returns: result
rad_initB
Initialize a new Radicle repository.
Args:
name: Name of the repository
description: Description of the repository
public: Whether the repository should be public (default: True)
Inputs: name (required), description, public. Returns: result
rad_issue_listC
List issues in a Radicle repository.
Args:
repository_path: Path to the repository (default: current directory)
Inputs: repository_path. Returns: result
rad_patch_listB
List patches in a Radicle repository.
Args:
repository_path: Path to the repository (default: current directory)
Inputs: repository_path. Returns: result
rad_pushC
Push changes to the Radicle network.
Args:
repository_path: Path to the repository (default: current directory)
Inputs: repository_path. Returns: result
rad_remote_listB
List remotes in a Radicle repository.
Args:
repository_path: Path to the repository (default: current directory)
Inputs: repository_path. Returns: result
rad_statusA
Get the status of a Radicle repository.
Args:
repository_path: Path to the repository (default: current directory)
Inputs: repository_path. Returns: result
rad_syncC
Sync a Radicle repository with the network.
Args:
repository_path: Path to the repository (default: current directory)
Inputs: repository_path. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
Most tools have distinct purposes (clone, init, push, sync, status, remote_list, issue_list, patch_list), but rad_help and rad_id are more general utility functions that could overlap with other tools' documentation or identification needs. The descriptions are clear enough to differentiate them in most cases.
All tools follow a consistent 'rad_' prefix with descriptive action_noun naming (e.g., rad_clone, rad_init, rad_push). The pattern is uniform across all 11 tools, making them predictable and easy to understand.
With 11 tools, this server is well-scoped for Radicle repository management. It covers core operations like cloning, initializing, pushing, syncing, and querying issues/patches, which aligns well with the server's purpose without being overwhelming or too sparse.
The server covers basic repository lifecycle operations (init, clone, push, sync, status) and querying (issue_list, patch_list, remote_list), but lacks CRUD tools for issues and patches (e.g., create_issue, update_patch). This creates notable gaps that agents might struggle with for full workflow coverage.
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
An MCP server that gives your AI access to the source code and docs of all public github repos
Model Context Protocol server for Studex tools, notifications, and profile integrations
Related MCP Servers
- FlicenseBqualityCmaintenanceA Model Context Protocol server that enables AI models to interact with GitHub's API, allowing for repository creation and management with descriptions, topics, and website URLs through natural language commands.1-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables LLM agents to manage GitHub repositories, issues, pull requests, branches, files, and releases through a standardized interface.489 npm8Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA server-side implementation that handles context processing between GitHub repositories and AI models, enabling seamless integration of AI capabilities with codebases through the Model Context Protocol.1MIT
- FlicenseNot gradedqualityNot gradedmaintenanceModel Context Protocol server that enables interaction with GitHub repositories, issues, pull requests, and search functionality through natural language.1-