git-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub Personal Access Token for API 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_repositoryB | Get metadata for a GitHub repository. |
| list_branchesC | List branches in a repository. |
| get_file_contentB | Read a file from a repository. Optionally specify ref (branch, tag, or commit SHA). |
| list_commitsC | List recent commits, optionally filtered by branch. |
| list_issuesB | List issues in a repository. Pull requests are excluded. |
| get_issueC | Get full details and comments for an issue. |
| create_issueC | Create a new issue in a repository. |
| list_pull_requestsC | List pull requests in a repository. |
| get_pull_requestB | Get pull request details including reviews and changed files. |
| search_repositoriesC | Search GitHub repositories. |
| search_codeC | Search code across GitHub. Example query: 'addClass in:file language:js repo:jquery/jquery'. |
| get_user_infoC | Get public profile information for a GitHub user. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| authenticated_user | Profile of the authenticated GitHub user. |
| user_repositories | Repositories accessible to the authenticated user (up to 30). |
TDQS
Scored across 12 tools
Each tool targets a distinct resource and action with no overlap. Issues, branches, commits, pull requests, repositories, code search, and user info are all clearly separated, and list_issues explicitly excludes pull requests to avoid confusion.
All tools follow a consistent verb_noun snake_case pattern (e.g., create_issue, list_branches, get_file_content). The verbs and nouns are logically chosen, making the set predictable and easy to navigate.
With 12 tools, the server is well-scoped for interacting with GitHub repositories. Each tool serves a clear purpose without unnecessary bloat, fitting the typical range for a focused MCP server.
The tool set is heavily read-oriented (list, get, search) but lacks essential write operations for a full lifecycle. Missing update/delete for issues, no create for pull requests or repositories, and no branch creation or commit tools, leaving significant gaps for agent workflows.