Skip to main content
Glama
surajfale

Git Commit MCP Server

by surajfale

git_commit_and_push

Automates Git commits by detecting changes, generating conventional commit messages, staging, committing, and optionally pushing to remote repositories while updating CHANGELOG.

Instructions

Track changes, generate commit message, commit, and optionally push.

This tool automates the Git commit workflow by:

  1. Detecting all changes in the repository

  2. Generating a conventional commit message

  3. Staging and committing the changes

  4. Optionally pushing to remote (if confirm_push is True)

  5. Updating the CHANGELOG.md file

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirm_pushNo
repository_pathNo.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden and effectively discloses all key behaviors: automated workflow, commit message generation, staging, committing, optional pushing, CHANGELOG.md update, and error handling. No hidden behaviors are omitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a concise summary, numbered steps, clear Args and Returns sections, and no redundant information. Every sentence adds value and is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (2 parameters, output schema, no annotations), the description is complete: it explains the workflow, parameters, return values, and behavior. The output schema details are provided in the description, and the context of the sibling tool is implicitly covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides detailed parameter semantics beyond the schema, especially for 'repository_path' with examples and supported formats. 'confirm_push' is clearly explained with its default value. Since schema had 0% description coverage, the description fully compensates.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool automates the Git commit workflow including tracking changes, generating commit message, committing, and optionally pushing. It distinguishes from the sibling tool 'generate_commit_message' by covering the full workflow.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the tool's context and capabilities (local and remote repos, optional push) and implies when to use it, but does not explicitly state when not to use it or contrast with the sibling tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

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/surajfale/git-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server