Skip to main content
Glama
fovi-llc

Radicle + GitHub MCP Server

by fovi-llc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
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)
rad_cloneB
Clone a Radicle repository.

Args:
    rid: Repository ID (RID) to clone
    path: Optional path where to clone the repository
rad_syncC
Sync a Radicle repository with the network.

Args:
    repository_path: Path to the repository (default: current directory)
rad_pushC
Push changes to the Radicle network.

Args:
    repository_path: Path to the repository (default: current directory)
rad_patch_listB
List patches in a Radicle repository.

Args:
    repository_path: Path to the repository (default: current directory)
rad_issue_listC
List issues in a Radicle repository.

Args:
    repository_path: Path to the repository (default: current directory)
rad_idB

Get the current node's Radicle ID.

rad_statusA
Get the status of a Radicle repository.

Args:
    repository_path: Path to the repository (default: current directory)
rad_remote_listB
List remotes in a Radicle repository.

Args:
    repository_path: Path to the repository (default: current directory)
rad_helpB
Get help for Radicle commands.

Args:
    command: Specific command to get help for (optional)
github_sync_unavailableC

GitHub sync functionality is not available.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

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.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources