GitHub MCP Server Plus
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_PERSONAL_ACCESS_TOKEN | Yes | GitHub Personal Access Token with appropriate permissions (repo scope for full control of private repositories, or public_repo scope for public repositories only) |
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
| Name | Description |
|---|---|
| create_or_update_fileC | Create or update a single file in a GitHub repository |
| search_repositoriesC | Search for GitHub repositories |
| create_repositoryC | Create a new GitHub repository in your account |
| get_file_contentsC | Get the contents of a file or directory from a GitHub repository |
| push_files_contentA | Push multiple files with direct content to a GitHub repository in a single commit |
| push_files_from_pathA | Push multiple files from filesystem paths to a GitHub repository in a single commit |
| create_issueC | Create a new issue in a GitHub repository |
| create_pull_requestC | Create a new pull request in a GitHub repository |
| fork_repositoryC | Fork a GitHub repository to your account or specified organization |
| create_branchC | Create a new branch in a GitHub repository |
| list_commitsC | Get list of commits of a branch in a GitHub repository |
| list_issuesC | List issues in a GitHub repository with filtering options |
| update_issueC | Update an existing issue in a GitHub repository |
| add_issue_commentC | Add a comment to an existing issue |
| search_codeC | Search for code across GitHub repositories |
| search_issuesC | Search for issues and pull requests across GitHub repositories |
| search_usersC | Search for users on GitHub |
| get_issueC | Get details of a specific issue in a GitHub repository. |
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 18 tools
Most tools have distinct purposes targeting specific GitHub resources and actions, but there is some overlap between push_files_content and push_files_from_path (both push multiple files, differing only in input source) and between list_issues and search_issues (both retrieve issues, differing in scope). Descriptions help clarify these distinctions, but agents might occasionally confuse them.
All tools follow a consistent verb_noun or verb_noun_preposition pattern (e.g., create_issue, get_file_contents, search_repositories), with no mixing of conventions like camelCase or snake_case variations. The naming is predictable and readable throughout the set.
With 18 tools, the count is slightly high but reasonable for a comprehensive GitHub server covering repositories, issues, files, search, and operations. It avoids being excessive (under 25) and each tool appears to serve a specific function, though some could be consolidated (e.g., the two push tools).
The tool set provides complete coverage for core GitHub workflows, including CRUD operations for repositories, issues, files, and branches, along with search across code, issues, repositories, and users. There are no obvious gaps; agents can perform end-to-end tasks like creating repos, managing issues, and pushing code without dead ends.