git-mcp-server

Created By
final-ila year ago
MCP Server handling GitHub/GitLab integrations
Overview

what is git-mcp-server?

The git-mcp-server is a server designed to handle integrations between GitHub and GitLab, facilitating seamless interactions between these two popular version control platforms.

how to use git-mcp-server?

To use git-mcp-server, set up the server by following the installation instructions provided in the GitHub repository. Once configured, it will manage the integration tasks automatically.

key features of git-mcp-server?

  • Handles GitHub and GitLab integrations efficiently.
  • Supports automated workflows between the two platforms.
  • Provides a centralized server for managing repository interactions.

use cases of git-mcp-server?

  1. Automating pull requests between GitHub and GitLab.
  2. Synchronizing issues and milestones across both platforms.
  3. Managing CI/CD pipelines that involve both GitHub and GitLab repositories.

FAQ from git-mcp-server?

  • What platforms does git-mcp-server support?

git-mcp-server supports integrations between GitHub and GitLab.

  • Is git-mcp-server open source?

Yes! git-mcp-server is open source and available on GitHub.

  • How can I contribute to git-mcp-server?

Contributions are welcome! Please check the contribution guidelines in the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
final-il
Star
0
Language
-
License
-

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