mcp-server-github
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub personal access token |
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 |
|---|---|
| list_reposC | List repositories for a user, organization, or the authenticated user |
| create_issueB | Create an issue in a GitHub repository with title, body, labels, and assignees |
| list_pull_requestsA | List pull requests in a repository with optional state and sort filters |
| get_file_contentsB | Get file or directory contents from a GitHub repository |
| search_codeB | Search code across GitHub repositories using GitHub search syntax |
| create_branchB | Create a new branch in a repository from a source branch |
| list_workflowsB | List GitHub Actions workflows in a repository |
| get_workflow_runsB | Get workflow run history for a specific GitHub Actions workflow |
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 8 tools
Each tool targets a distinct GitHub resource or action: branches, issues, file contents, workflow runs, pull requests, repos, workflows, and code search. No overlap in purpose.
All tool names use a consistent verb_noun pattern in snake_case (e.g., create_branch, list_pull_requests), making them predictable and easy to interpret.
With 8 tools, the set is well-scoped for a GitHub MCP server, covering essential read operations and some write operations without being bloated.
Missing critical operations like updating or closing issues, creating or merging pull requests, and managing repositories. The surface has notable gaps for typical GitHub workflows.