GitHub MCP Server

Created By
tradesdontliea year ago
A GitHub MCP Server with SSE transport built with TypeScript and Express
Overview

what is GitHub MCP Server?

GitHub MCP Server is a Model Context Protocol (MCP) server designed to provide tools for managing GitHub repositories and task management.

how to use GitHub MCP Server?

To use GitHub MCP Server, clone the repository, install the dependencies, set up your GitHub token in the .env file, and run the server using npm start.

key features of GitHub MCP Server?

  • GitHub Integration: Create and manage issues, handle pull requests, and work with repositories.
  • Task Management: Create and organize tasks with priorities, track dependencies, mark tasks as complete, and get the next highest priority task to work on.

use cases of GitHub MCP Server?

  1. Managing GitHub issues and pull requests efficiently.
  2. Organizing and prioritizing tasks for software development projects.
  3. Tracking task dependencies to streamline project workflows.

FAQ from GitHub MCP Server?

  • Can I use GitHub MCP Server for any GitHub repository?

Yes! GitHub MCP Server can be used with any GitHub repository as long as you have the necessary permissions.

  • Is there a setup guide available?

Yes! Detailed setup instructions are provided in the repository's documentation.

  • What programming language is GitHub MCP Server built with?

GitHub MCP Server is built with TypeScript and Express.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tradesdontlie
Star
0
Language
TypeScript
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.

6 hours ago