github-mcp-lite
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | Your GitHub Personal Access Token (PAT) for 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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_repoC | Repository metadata: branch, visibility, stars, description. |
| search_codeC | Search code. Example: repo:owner/name TODO. |
| get_file_contentsA | Read a file or list a directory. Optional ref (branch, tag, sha). |
| list_pull_requestsC | List pull requests. state is open, closed, or all. |
| get_pull_requestA | Fetch one pull request with merge state and diff stats. |
| create_issueC | Create an issue. labels is a comma-separated list. |
| comment_on_issueC | Add a comment to an issue or pull request. |
| list_issuesB | List issues only. state is open, closed, or all. |
| search_repositoriesC | Search repositories using GitHub query syntax. |
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 9 tools
Each tool targets a distinct resource and action: issues, pull requests, repos, files, and search. No overlap in functionality; e.g., list_issues vs list_pull_requests are clearly separated.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_issue, get_repo, search_code), making it predictable for an agent.
With 9 tools, the server is well-scoped for a 'lite' GitHub MCP, covering essential operations without being bloated or too sparse.
The tool set covers read operations extensively (get, list, search) and create for issues, but lacks update/delete for issues and PR creation/update, which are notable gaps for common workflows.