github-repo-manager-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub personal access token with appropriate permissions |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_repositoryC | Create a new GitHub repository for the authenticated user or an organization. |
| update_repositoryC | Update repository details such as description, homepage, topics, visibility, default branch, and archived state. |
| delete_repositoryA | Delete a GitHub repository. Requires confirm=true. NOTE: Your PAT must have the 'delete_repo' scope enabled. |
| add_repository_topicsB | Add topics/tags to a repository without removing existing topics. |
| add_repository_labelsC | Create labels on a repository for organization. |
| list_repositoriesC | List repositories visible to the authenticated user with filters. |
| rename_repositoryD | Rename a repository. |
| archive_repositoryC | Archive a repository. |
| pin_repositoryB | Pin a repository to a GitHub profile using the GitHub GraphQL API. Requires Classic PAT with write:discussion scope. |
| get_file_contentA | Get the content of any file (e.g. README.md) from a GitHub repository using the authenticated token. |
| update_file_contentB | Create or update any file (e.g. README.md) in a GitHub repository using the authenticated token. Provide sha to update an existing file, omit to create a new one. |
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 11 tools
Most tools have distinct purposes, but update_repository overlaps with archive_repository and rename_repository. Descriptions help clarify boundaries.
All tools follow a consistent verb_noun pattern using snake_case (e.g., create_repository, delete_repository, update_file_content).
11 tools is well-scoped for a repository manager, covering core operations without being overwhelming.
Covers CRUD and common operations like labels and topics, but missing explicit get single repo details and collaboration management.