MCP GitHub Reader
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_individual_file_contentD | – |
| get_entire_repo_contentsD | – |
| analyzeRepositoryD | – |
| searchRepositoryD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| repositoryOverview | |
| codeExplanation | |
| codeSearch | |
| repositoryInfo | |
| repositoryStructure | |
| fileContent | |
| branchList |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The tool names indicate distinct actions: 'analyzeRepository' suggests analysis, 'get_entire_repo_contents' and 'get_individual_file_content' differentiate by scope, and 'searchRepository' is for searching. Without descriptions, the names are clear enough to avoid major confusion.
The naming convention is inconsistent, mixing camelCase ('analyzeRepository', 'searchRepository') with snake_case ('get_entire_repo_contents', 'get_individual_file_content'). This lack of a consistent pattern makes it harder for agents to predict names.
With 4 tools, the set is well-scoped for a 'GitHub Reader' server. Each tool serves a distinct purpose (analysis, full content retrieval, single file retrieval, search) without being overly minimal or bloated.
The tools cover core reading operations (full content, file content, search), but notable gaps exist, such as retrieving repository metadata (e.g., description, stars) or listing branches. The surface is functional but not comprehensive.