GitHub MCP Server

Created By
yamagaia year ago
GitHub MCP Server (SSE)
Overview

what is GitHub MCP Server?

GitHub MCP Server is an integration server that uses the Model Context Protocol (MCP) to provide a standardized interface for large language model (LLM) applications to communicate with the GitHub API.

how to use GitHub MCP Server?

To use the GitHub MCP Server, you can run it in standard input/output mode or in Server-Sent Events (SSE) mode. Set your GitHub token as an environment variable and start the server using the provided commands.

key features of GitHub MCP Server?

  • Search for repositories
  • Create new repositories
  • Retrieve file contents
  • Create or update files
  • Bulk push multiple files
  • Fork repositories
  • Create pull requests
  • Retrieve details of pull requests
  • Add reviews to pull requests

use cases of GitHub MCP Server?

  1. Automating repository management tasks.
  2. Integrating LLM applications with GitHub for enhanced functionality.
  3. Facilitating collaborative development through pull requests and reviews.

FAQ from GitHub MCP Server?

  • What programming language is GitHub MCP Server written in?

GitHub MCP Server is written in Go.

  • Is there a Docker container available for GitHub MCP Server?

Yes, a Docker container is provided for running the server in SSE mode.

  • How can I customize the port for the SSE server?

You can specify a custom port using the -p option when starting the server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
yamagai
Star
0
Language
Go
License
-

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.

34 minutes ago