GitHub Prod MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level. | INFO |
| GITHUB_TOKEN | Yes | GitHub personal access token with scopes for the operations you plan to use. | |
| GITHUB_USER_AGENT | No | User agent for GitHub API requests. | github-prod-mcp/0.1.0 |
| GITHUB_API_VERSION | No | GitHub API version header. | 2022-11-28 |
| GITHUB_API_BASE_URL | No | Base URL for GitHub API. | https://api.github.com |
| GITHUB_TIMEOUT_SECONDS | No | Timeout in seconds for GitHub API requests. | 30 |
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 |
|---|---|
| get_authenticated_userA | Get the authenticated GitHub user |
| create_repositoryC | Create a repository for the authenticated user |
| get_repositoryC | Get repository metadata |
| list_branchesC | List repository branches |
| get_branchC | Get a branch by name |
| get_repository_detailsC | Get repository details including optional branches, root files, and README metadata |
| list_repository_filesC | List repository files or directory contents |
| get_file_contentC | Get repository file content metadata |
| search_repositoriesD | Search repositories |
| search_codeD | Search code |
| search_issuesC | Search issues and pull requests |
| list_issuesC | List repository issues |
| get_issueD | Get an issue |
| create_issueD | Create an issue |
| update_issueC | Update an issue |
| create_issue_commentC | Create an issue comment |
| list_pull_requestsC | List pull requests |
| get_pull_requestC | Get a pull request |
| create_pull_requestC | Create a pull request |
| merge_pull_requestC | Merge a pull request |
| get_commitC | Get a commit |
| compare_commitsD | Compare commits |
| create_or_update_fileC | Create or update a repository file |
| delete_fileC | Delete a repository file |
| create_repository_dispatchC | Create a repository dispatch event |
| trigger_workflow_dispatchD | Trigger a workflow dispatch |
| list_workflow_runsC | List workflow runs |
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 27 tools
Most tools have distinct purposes, but get_repository and get_repository_details overlap with similar descriptions, and list_issues vs search_issues could cause confusion.
All tools follow verb_noun snake_case (e.g., create_issue, list_branches) with no mixing of conventions.
27 tools exceed the 25+ threshold for 'too many', making the surface heavier than ideal for most agents.
Covers core repository, issue, PR, and workflow operations, but lacks update_pull_request, create_branch, and detailed workflow management.