RepoControl MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | Your GitHub token used by the RepoControl MCP server to access the GitHub API. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_issueC | Create a new issue in a GitHub repository. |
| get_issue_commentsC | Retrieve recent discussion comments on an issue or pull request. |
| create_pull_requestB | Open a Pull Request with built-in branch safety validation. |
| list_pull_requestsC | List pull requests in repository filtered by state. |
| check_ci_statusB | Inspect GitHub Actions check-runs and overall CI status for a branch or commit SHA. |
| is_branch_protectedB | Check if a branch name is considered protected by safety rules. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct target action: creating issues, reading comments, creating/listing pull requests, checking CI, and checking branch protection. The only slight overlap is get_issue_comments covering issue or PR comments, but the intent remains clear.
All tool names use consistent snake_case with a predictable verb_noun or is_property pattern. The naming is readable and uniform across the set.
Six tools is well-scoped for a focused repository-control server. Each tool appears to earn its place without obvious redundancy.
The set covers issue creation/comments, PR creation/listing, CI status, and branch protection checks, but lacks obvious lifecycle operations such as updating/closing issues, merging PRs, or reviewing PRs. These gaps may force agents to work around missing operations.