Radicle + GitHub MCP Server
Related Servers
Alternatives to Radicle + GitHub MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityNot gradedmaintenanceModel Context Protocol server that enables interaction with GitHub repositories, issues, pull requests, and search functionality through natural language.1-
- -licenseCqualityNot gradedmaintenanceA Model Context Protocol server with GitHub API integration that enables interaction with repositories, issues, pull requests, and file management through a standardized interface.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.642 npm8Apache 2.0
- FlicenseBqualityDmaintenanceA 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 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
- AlicenseNot gradedqualityDmaintenanceProvides a GitHub-integrated Model Context Protocol server with Octokit client, enabling AI models to interact with GitHub repositories, issues, and pull requests.ISC
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.