github-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_OWNER | Yes | GitHub username or organization. | |
| GITHUB_TOKEN | Yes | GitHub personal access token with repo and read:user scopes. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_reposB | List repositories for a user/org. Returns name, language, stars, and last updated. |
| get_repo_structureC | Get the file/directory tree of a repository (one level deep). |
| get_fileB | Read a file's content from a GitHub repository. |
| search_codeC | Search code across repositories. Optionally filter by owner or language. |
| list_issuesC | List issues for a repository. |
| get_commitsC | Get recent commits for a repository. |
| repo_statsB | Get repository stats: languages, size, open issues, forks, creation date. |
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 7 tools
Each tool targets a distinct resource and action: commits, file content, repo structure, issues, repos list, stats, and code search. No two tools have overlapping purposes.
Most tools follow a consistent verb_noun snake_case pattern (e.g., get_commits, list_issues). The exception is 'repo_stats', which uses noun_noun, but overall style remains uniform.
Seven tools is a well-scoped set for a read-oriented GitHub client. Each tool provides distinct functionality without redundancy.
Basic read operations are covered (repos, files, commits, issues, search), but gaps exist: no single-repo details, no single-issue view, and no write operations (create/update). Agents may face dead ends.