MCP Git Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REPOSITORY_PATH | No | Path to Git repository |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| git_statusC | Shows the working tree status |
| git_diff_unstagedB | Shows changes in the working directory that are not yet staged |
| git_diff_stagedC | Shows changes that are staged for commit |
| git_diffC | Shows differences between branches or commits |
| git_commitC | Records changes to the repository |
| git_addC | Adds file contents to the staging area |
| git_resetC | Unstages all staged changes |
| git_logC | Shows the commit logs |
| git_create_branchC | Creates a new branch from an optional base branch |
| git_checkoutC | Switches branches |
| git_showC | Shows the contents of a commit |
| git_initC | Initialize a new Git repository |
| git_pushC | Push commits to remote repository |
| git_pullC | Pull changes from remote repository |
| git_diff_branchesC | Show differences between two branches |
| github_get_pr_checksC | Get check runs for a pull request |
| github_get_failing_jobsC | Get detailed information about failing jobs in a PR |
| github_get_workflow_runC | Get detailed workflow run information |
| github_get_pr_detailsC | Get comprehensive PR details |
| github_list_pull_requestsC | List pull requests for a repository with filtering and pagination |
| github_get_pr_statusC | Get the status and check runs for a pull request |
| github_get_pr_filesC | Get files changed in a pull request with pagination support |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| commit-message | Generate a conventional commit message based on staged changes |
| pr-description | Generate a comprehensive pull request description |
| release-notes | Generate release notes from commit history |
| code-review | Generate a code review prompt for a diff |
| merge-conflict-resolution | Help resolve merge conflicts systematically |
| git-workflow-guide | Guide for Git workflow best practices |
| branch-strategy | Recommend branching strategy for a project |
| git-troubleshooting | Help troubleshoot common Git issues |
| changelog-generation | Generate changelog from commit history |
| rebase-interactive | Guide for interactive rebase operations |
| github-actions-failure-analysis | Analyze GitHub Actions failures and suggest fixes |
| ci-failure-root-cause | Identify root cause of CI failures and provide solutions |
| pr-readiness-assessment | Assess PR readiness and suggest improvements |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/MementoRC/mcp-git'
If you have feedback or need assistance with the MCP directory API, please join our Discord server