Git MCP Server

Created By
cyanheadsa year ago
An MCP (Model Context Protocol) server enabling LLMs and AI agents to interact with Git repositories. Provides tools for comprehensive Git operations including clone, commit, branch, diff, log, status, push, pull, merge, rebase, worktree, tag management, and more, via the MCP standard. STDIO & HTTP.
Overview

what is Git MCP Server?

Git MCP Server is a Model Context Protocol (MCP) server that provides comprehensive Git functionality for Large Language Models (LLMs), enabling them to perform version control operations through a secure and standardized interface.

how to use Git MCP Server?

To use Git MCP Server, clone the repository from GitHub, install the dependencies, and configure it in your MCP client settings. After that, you can integrate its operations with your Git workflows.

key features of Git MCP Server?

  • Core Git operations including repository management and file handling
  • Bulk operations for executing multiple Git commands in sequence
  • Safety features for path validation and error reporting

use cases of Git MCP Server?

  1. Integrating version control capabilities within LLM applications.
  2. Automating repository management tasks using AI agents.
  3. Enhancing development environments with secure Git operations.

FAQ from Git MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a standardized communication protocol that allows LLMs to interact with external systems, such as Git servers.

  • Is Git MCP Server open source?

Yes! Git MCP Server is open source under the Apache License 2.0.

  • Can I contribute to Git MCP Server?

Absolutely! Contributions are welcome; just follow the guidelines provided in the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
cyanheads
Star
69
Language
TypeScript
License
Apache-2.0 license
Tags

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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.

an hour ago
Gpt Scrambler

2 days ago