GitHub MCP Server

Created By
brukhabtua year ago
A Management Control Panel server for GitHub projects using Issues API
Overview

what is GitHub MCP Server?

GitHub MCP Server is a Management Control Panel (MCP) server designed for managing GitHub projects using the GitHub Issues API, allowing users to manage tasks and team collaboration without directly using GitHub's Projects feature.

how to use GitHub MCP Server?

To use the GitHub MCP Server, clone the repository, install the dependencies, set up your GitHub Personal Access Token, and start the server. Access the MCP interface through your browser at http://localhost:3000.

key features of GitHub MCP Server?

  • View all your repositories
  • Create, update, and track issues across repositories
  • Assign issues to team members
  • Add comments to issues
  • Create and manage labels to categorize tasks
  • View repository milestones
  • See repository collaborators

use cases of GitHub MCP Server?

  1. Managing multiple GitHub repositories efficiently.
  2. Collaborating with team members on tasks and issues.
  3. Organizing project tasks with labels and milestones.

FAQ from GitHub MCP Server?

  • What are the prerequisites to run GitHub MCP Server?

You need Node.js (v14 or higher), npm or yarn, and a GitHub Personal Access Token with repo scope.

  • Can I customize the GitHub MCP Server?

Yes! You can add more API endpoints, create a custom frontend, implement authentication, and add database support for project metadata.

  • Is there a license for GitHub MCP Server?

Yes, it is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
brukhabtu
Star
0
Language
JavaScript
License
-
Tags

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