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.