Mcp Git Commit Generator

Created By
theoklitosBam710 months ago
Generate conventional commit messages from your staged git changes using Model Context Protocol (MCP)
Overview

What is MCP Git Commit Generator?

MCP Git Commit Generator is a tool that generates conventional commit messages from your staged git changes using the Model Context Protocol (MCP).

How to use MCP Git Commit Generator?

To use the MCP Git Commit Generator, you can install it via uvx, pip, or Docker. After installation, stage your changes in a git repository and use the tool through your MCP client to generate a commit message.

Key features of MCP Git Commit Generator?

  • Automatic commit message generation based on staged git diffs.
  • Supports Conventional Commits.
  • MCP server with stdio and SSE transport options.
  • Inspector UI for interactive inspection.

Use cases of MCP Git Commit Generator?

  1. Automatically generating commit messages for git changes.
  2. Ensuring commit messages follow the Conventional Commits standard.
  3. Integrating with various MCP-compatible clients for enhanced development workflows.

FAQ from MCP Git Commit Generator?

  • Can I use MCP Git Commit Generator with any git repository?

Yes! It works with any git repository as long as you have the necessary dependencies installed.

  • Is there a recommended way to install MCP Git Commit Generator?

Yes! Using uvx is recommended for managing dependencies easily.

  • What are the transport options available?

You can use stdio (default) or SSE for transport.

Server Config

{
  "mcpServers": {
    "mcp-git-commit-generator": {
      "command": "uvx",
      "args": [
        "mcp-git-commit-generator"
      ]
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
theoklitosBam7
Star
-
Language
-
License
-
Tags

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago