GitPilot MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORKSPACE | No | Local workspace directory for cloning repositories. | ./workspace |
| GITHUB_TOKEN | Yes | GitHub personal access token with permissions to fork repositories and create pull requests. |
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 |
|---|---|
| fork_repoC | Fork a GitHub repository to your account. |
| get_issueC | Get details about a GitHub issue. |
| clone_repoC | Clone a repository to the workspace. |
| create_branchC | Create or checkout a branch. |
| sync_with_upstreamC | Sync local fork with upstream repository. |
| apply_patchC | Apply a git patch to the repository. |
| commit_and_pushC | Commit changes and push to origin. |
| create_pull_requestD | – |
| check_for_conflictsC | Check if there are merge conflicts with upstream. |
| update_pr_after_feedbackD | – |
| run_testsC | Run tests inside the repository. Returns stdout, stderr, and exit code. |
| retry_fix_with_testsC | Helper tool for Claude to manage test-fix loops. Claude should:
|
| index_repoA | Index a repository for semantic code search. The index is stored in a centralized location to avoid polluting the repository with .rag folders. |
| get_repo_contextB | Search the indexed repository for relevant code chunks. |
| list_indexed_repositoriesA | List all repositories that have been indexed. Returns: Dictionary with count and list of indexed repositories |
| get_index_storage_infoA | Get information about the centralized index storage location. Returns: Dictionary with storage path and statistics |
| reindex_repositoryA | Re-index a repository (useful after code changes). This will delete the old index and create a fresh one. |
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 17 tools
Most tools have distinct purposes, though create_pull_request and update_pr_after_feedback lack descriptions, causing ambiguity. retry_fix_with_tests is a meta-tool but clear in its intent. Overall, minimal overlap.
Tools predominantly use snake_case with verbs, but some are phrases like check_for_conflicts and retry_fix_with_tests, breaking consistency. get_index_storage_info uses 'info' instead of a standard noun.
With 17 tools, it covers a wide range of git/GitHub operations. Some tools like get_index_storage_info are niche but still relevant. Slightly above ideal but reasonable.
Core workflows (clone, branch, commit, PR) are present, but missing operations like branch deletion, merge, and issue creation. Indexing feature adds unique functionality but gaps remain.