GitHub PR MCP Server

Created By
ibraheem4a year ago
Claude MCP Server for Github with Linear integration
Overview

What is GitHub PR MCP Server?

GitHub PR MCP Server is an enhanced server for managing GitHub Pull Requests using the Model Context Protocol (MCP), providing a structured and comprehensive workflow for PR creation.

How to use GitHub PR MCP Server?

To use the server, you can run it directly using npx or build it locally. Ensure you have the required GitHub Personal Access Token and Linear API Key set up in your environment.

Key features of GitHub PR MCP Server?

  • Structured PR templates with predefined sections
  • Rich media attachment support
  • Automated quality checklists
  • Advanced issue linking and tracking
  • Compatibility with existing GitHub workflows

Use cases of GitHub PR MCP Server?

  1. Creating detailed pull requests with structured information.
  2. Managing PRs with automated quality checks.
  3. Integrating with Linear for issue tracking.

FAQ from GitHub PR MCP Server?

  • What are the prerequisites for using the server?

You need Node.js 18+, a GitHub Personal Access Token, and a Linear API Key.

  • Can I run this server alongside the base GitHub server?

Yes, both servers can run simultaneously, allowing you to choose based on your needs.

  • How do I troubleshoot common issues?

Check your GitHub token permissions, ensure environment variables are set correctly, and verify Node.js version compatibility.

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

17 hours ago
Voyei

7 hours ago