github-mcp-server

Provides a Model Context Protocol (MCP) server that exposes GitHub-related tools (e.g., listing/searching and creating issues/PRs, pending reviews, and issue priority analysis). Tools are described as stateless and require authentication with permission checks.

Evaluated Apr 04, 2026 (17d ago)

Repo ↗ Infrastructure mcp github ai-agents issues pull-requests automation go

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

README states tools require authentication and are protected by permission checks, and expects a token via environment variable. However, it does not document whether transport uses HTTPS-only (for the MCP server), how tokens are stored/handled internally (logging/redaction), or whether tools enforce fine-grained scopes per operation.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want an agent-friendly, tool-based integration to GitHub issue/PR workflows via MCP, using a token-based auth model and controlled permissions.

Avoid When

You need a fully documented REST/OpenAPI interface, webhooks, or strong published guarantees about retries/idempotency and error formats beyond what is stated in the README.

Use Cases

• Enable LLM agents to list/search GitHub issues and pull requests
• Automate issue triage workflows (including priority analysis)
• Create issues from agent workflows with permissioned access
• Fetch PRs pending review for operational workflows

Not For

• Arbitrary GitHub data scraping without authenticated permissions
• High-risk write operations without reviewing tool semantics and idempotency
• Use cases requiring real-time webhook push events from this MCP server

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: GitHub OAuth App credentials / GitHub token (GITHUB_TOKEN env var)

OAuth: No Scopes: No

README indicates authentication via a GitHub token and permission checks, but does not document OAuth flow details or fine-grained scopes for MCP tools.

Pricing

Free tier: No

Requires CC: No

No pricing information provided (appears to be a self-hosted open-source-style repo).

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Write operations (e.g., create_issue) may require careful handling to avoid duplicates, but idempotency behavior is not documented in the README.
⚠ Pagination/limit behavior for list/search tools is not documented in the README.
⚠ Error formats and retry guidance are not documented in the README; agents may need to infer retry behavior from runtime errors.

Alternatives

GitHub REST API or GraphQL API directly GitHub Actions/workflows for automation Existing GitHub agent toolkits (varies by framework) Other MCP servers for GitHub (if available)

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for github-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.