rad_initLABSCO SUMMARY
Radicle for assistants that only know GitHub.
Every tool here is a rad subcommand, so the ceiling is whatever your local Radicle install can already do and the identity it holds. The draw is the pairing: one client gets both networks, and the repository's sync keeps issues mirrored rather than making you copy them across.
What it is
A Python MCP server that fronts the rad command line so an assistant can work with Radicle repositories. The repository also ships configuration for the official GitHub MCP server alongside it, plus a bidirectional issue sync between the two.
What you get
- rad_init to start a Radicle repository, rad_clone to clone one by RID
- rad_status for repository state
- rad_sync and rad_push to exchange changes with the network
- rad_patch_list for patches — Radicle's pull requests — and rad_issue_list for issues
- rad_remote_list for the remotes and nodes a repository is seen on
- rad_id for your own node ID, rad_help for command documentation
- Issue and pull-request sync between GitHub and Radicle, idempotent, preserving the original author, links and timestamps in a mapping database
Requirements
The rad CLI installed and on PATH, and a reasonably current Python with the mcp library. The GitHub half needs Deno for the official GitHub server and a GitHub personal access token.
Setup effort
Follow the published steps — deno install -g --name github-mcp npm:@modelcontextprotocol/server-github
USE CASES
01
Getting an existing project onto Radicle
Initialise the repository, then push and sync it to the network.
02
Picking up a repository someone gave you an RID for
Clone by RID and read its state before touching anything.
03
Reviewing what is open on a peer-to-peer repo
List the patches and the issues in the conversation instead of switching to the Radicle interface.
04
Working out why your changes are not reaching anyone
Check the repository status and which remotes and nodes it is actually seen on before re-syncing.
05
Finding a rad command you half-remember
Ask for the command documentation and your own node ID without leaving the session.
13 tools
Listed in project docs. Your client may show a different list.
rad_clonerad_statusrad_syncrad_pushrad_patch_listrad_issue_listrad_remote_listrad_idrad_helpgithub_sync_testgithub_sync_issuesgithub_sync_fullBEFORE YOU INSTALL
What to know first
Tools you get
13 tools named in the project's documentation. github_sync_test, github_sync_issues and github_sync_full are documented under MCP Integration, not Available Tools. GitHub repository, issue and pull-request operations come from the separate @modelcontextprotocol/server-github.
Requires
GITHUB_PERSONAL_ACCESS_TOKEN in your environment
INSTALLATION
Connect your client
Server setup
Install the Radicle CLI so rad is on PATH: curl -sSf https://install.radicle.xyz | sh
Install Deno (needed to run the GitHub MCP server): curl -fsSL https://deno.land/install.sh | sh
Create a GitHub Personal Access Token at https://github.com/settings/tokens with repo, issues and pull request permissions
Clone this repository
TERMINAL
pip install -e .
deno install -g --name github-mcp npm:@modelcontextprotocol/server-github
export GITHUB_PERSONAL_ACCESS_TOKEN=<YOUR_GITHUB_PERSONAL_ACCESS_TOKEN>
python setup_mcp.pyMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"radicle-mcp": {
"command": "<YOUR_PATH_TO_PYTHON>",
"args": [
"-m",
"radicle_mcp.server"
]
},
"github-mcp": {
"command": "<YOUR_PATH_TO_GITHUB_MCP>",
"args": [],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_GITHUB_PERSONAL_ACCESS_TOKEN>"
}
}
}
}
