Skip to main content
Glama
Radicle + GitHub MCP Server

Radicle + GitHub MCP Server

by fovi-llc

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 repository

  • rad_clone: Clone an existing repository by RID

  • rad_status: Get repository status and information

  • rad_sync: Sync repository with the network

  • rad_push: Push changes to the network

Collaboration Features

  • rad_patch_list: List patches (pull requests) in a repository

  • rad_issue_list: List issues in a repository

  • rad_remote_list: List remotes/nodes for a repository

Node & Identity

  • rad_id: Get your Radicle node ID

  • rad_help: Get help for Radicle commands

Prerequisites

  1. Radicle CLI: Ensure the rad command is installed and available in your PATH

    # Install Radicle (see https://radicle.xyz for installation instructions)
    curl -sSf https://install.radicle.xyz | sh
  2. Deno: For running the GitHub MCP server

    # Install Deno
    curl -fsSL https://deno.land/install.sh | sh
  3. Python Environment: Python 3.8+ with the MCP library

    pip install mcp
  4. GitHub Personal Access Token: For GitHub integration

Installation

  1. Clone this repository

  2. Install dependencies:

    pip install -e .
  3. Install the official GitHub MCP server:

    deno install -g --name github-mcp npm:@modelcontextprotocol/server-github
  4. Run 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.py

GitHub ↔ 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-only

MCP Integration

The sync functionality is available as MCP tools:

  • github_sync_test: Test connectivity

  • github_sync_issues: Sync issues only

  • github_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-mcp

With 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.md

Contributing

  1. Fork the repository

  2. Create a feature branch

  3. Make your changes

  4. Add tests if applicable

  5. Submit a pull request

License

MIT License - see LICENSE file for details

Available Tools

11 tools
github_sync_unavailableC

GitHub sync functionality is not available.

Inputs: no named parameters. Returns: result

rad_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

    B3.3/5.0

    Scored across 11 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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

    Related MCP Servers