MCP GitHub Repository Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is MCP GitHub Repository Server?

MCP GitHub Repository Server is an MCP (Model Context Protocol) server that provides access to GitHub repository contents, allowing AI assistants to browse and read files from specified GitHub repositories.

how to use MCP GitHub Repository Server?

To use the server, configure it with your GitHub Personal Access Token and repository details, then run the server to access files via the provided API endpoints.

key features of MCP GitHub Repository Server?

  • Access any file in a GitHub repository via URI
  • List repository contents and navigate directories
  • Support for branch-specific file access
  • File contents served as plain text
  • Error handling for various issues

use cases of MCP GitHub Repository Server?

  1. AI assistants retrieving code files from GitHub repositories.
  2. Developers accessing documentation files directly from repositories.
  3. Automated tools listing and reading files in a repository for analysis.

FAQ from MCP GitHub Repository Server?

  • What is required to run the server?

You need a GitHub Personal Access Token and the repository details to configure the server.

  • Can I access private repositories?

Yes, as long as your token has the appropriate permissions.

  • How do I debug the server?

Use the MCP Inspector for debugging, which provides a URL to access debugging tools in your browser.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
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.

3 hours ago