Git Mcp

Created By
kjozsaa year ago
MCP server for managing Git operations on local repositories. Fetching commit messages, git tags, creating new tags.
Overview

what is Git MCP?

Git MCP is a server designed for managing Git operations on local repositories, allowing users to fetch commit messages, manage git tags, and perform various Git-related tasks efficiently.

how to use Git MCP?

To use Git MCP, you can install it via Smithery or manually. After installation, configure the MCP server with the required environment variables and JSON configuration snippet, then utilize the available methods to manage your Git repositories.

key features of Git MCP?

  • List all Git repositories in a specified path.
  • Fetch the last Git tag from a repository.
  • List commit messages between the last tag and HEAD.
  • Create new Git tags with optional messages.
  • Push existing tags to the remote repository.
  • Checkout and pull the main branch from all remotes.

use cases of Git MCP?

  1. Managing multiple Git repositories in a local environment.
  2. Automating the process of tagging and pushing changes to remote repositories.
  3. Simplifying the retrieval of commit history and tags for project documentation.

FAQ from Git MCP?

  • How do I install Git MCP?

You can install Git MCP using the command npx -y @smithery/cli install @kjozsa/git-mcp --client claude or manually with uvx install git-mcp.

  • What environment variables do I need to set?

You need to set GIT_REPOS_PATH to the directory containing your Git repositories.

  • Can I run tests on Git MCP?

Yes! The project includes test scripts to verify the functionality of both the Git commands and the MCP server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kjozsa
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day 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.

8 hours ago