@cloud9-labs/mcp-github
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub Personal Access Token for API authentication |
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 |
|---|---|
| github_list_reposC | List repositories for the authenticated user |
| github_get_repoC | Get details of a specific repository |
| github_create_repoB | Create a new repository for the authenticated user |
| github_list_issuesB | List issues for a repository |
| github_get_issueB | Get details of a specific issue |
| github_create_issueB | Create a new issue in a repository |
| github_update_issueC | Update an existing issue |
| github_list_pull_requestsB | List pull requests for a repository |
| github_get_pull_requestB | Get details of a specific pull request |
| github_create_pull_requestB | Create a new pull request |
| github_list_branchesB | List branches in a repository |
| github_get_file_contentC | Get the contents of a file in a repository |
| github_search_reposC | Search for repositories on GitHub |
| github_search_codeC | Search for code across GitHub repositories |
| github_list_commitsB | List commits in a 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 15 tools
Each tool targets a distinct resource and action (e.g., list_commits vs. create_issue), and even similar tools like list_repos vs. search_repos are clearly differentiated by scope. There is no overlap or ambiguity among the tool purposes.
All tool names follow a uniform pattern: 'github_' prefix followed by a verb_noun structure (e.g., github_create_repo, github_list_pull_requests). The naming is perfectly consistent and predictable.
With 15 tools, the server covers the primary GitHub resources (repos, issues, PRs, commits, branches, files, search) without being bloated. Each tool serves a clear purpose in the GitHub domain, making the count well-scoped.
The surface covers core CRUD for issues (create/get/update/list) and read operations for repos, PRs, commits, branches, and file content. Minor gaps exist (e.g., no PR update/merge, no file write, no commit detail), but these are not fatal and can be worked around via other tools.