Git Commit MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AI_MODEL | No | OpenAI model to use (default: gpt-4o-mini) | gpt-4o-mini |
| ENABLE_AI | No | Set to true to use AI generation (default: true) | true |
| LOG_LEVEL | No | Logging level: DEBUG, INFO, WARNING, ERROR (default: INFO) | INFO |
| FORCE_SSH_ONLY | No | Require SSH for Git operations (default: true) | true |
| OPENAI_API_KEY | Yes | Required when ENABLE_AI=true for AI-powered commit messages |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| git_commit_and_pushA | Track changes, generate commit message, commit, and optionally push. This tool automates the Git commit workflow by:
Supports both local repositories and remote repository URLs. For remote repositories, the tool will clone them to a workspace and perform operations there. Args: repository_path: Path to the Git repository or remote URL (default: current directory) Supports: - Local paths: ".", "/path/to/repo", "relative/path" - SSH URLs: "git@github.com:user/repo.git" - HTTPS URLs: "https://github.com/user/repo.git" confirm_push: Whether to push to remote after committing (default: False) Returns: Dictionary containing commit result information: - success: Whether the operation completed successfully - commit_hash: The SHA hash of the created commit - commit_message: The full commit message used - files_changed: Number of files affected - pushed: Whether the commit was pushed to remote - changelog_updated: Whether CHANGELOG.md was updated - message: Human-readable status message - error: Error message if operation failed |
| generate_commit_messageA | Analyze changes and generate a Conventional Commit message using AI.
Returns: { success, commit_message, files_changed, message, error? } |
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 have clearly distinct purposes: one performs the full commit and push workflow, while the other only generates a commit message. There is no overlap or ambiguity.
Both tool names follow the same snake_case convention and use a verb_noun pattern. 'git_commit_and_push' and 'generate_commit_message' are consistent in style.
With only two tools, the server feels minimal but is scoped to git commit operations. It is borderline acceptable; more tools could be added for a richer experience.
The server covers commit and push, and commit message generation, but is missing other common git operations like staging/unstaging, viewing status, or undoing commits. Some gaps exist for a complete commit workflow.