GitHub MCP Server
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 |
|---|---|
| list_repositoriesA | List all repositories of the authenticated user. |
| get_repositoryD | Get details of 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 2 tools
The two tools are clearly distinct: one retrieves details of a specific repository, the other lists all repositories. No overlap in purpose.
Both tools follow a consistent verb_noun pattern ('get_repository', 'list_repositories'), with appropriate singular/plural usage.
With only 2 tools, the server is extremely limited for a GitHub-related service. Typical functionality requires many more tools (issues, PRs, etc.).
The tool surface is severely incomplete; it lacks any operations related to issues, pull requests, commits, content, or repository management beyond basic retrieval.