gh-github-mcp-server

Provides a GitHub CLI extension that installs and runs a GitHub MCP server in stdio mode, reusing the user’s existing `gh` authentication, with a short VS Code configuration example.

Evaluated Apr 04, 2026 (17d ago)
Repo ↗ DevTools ai-ml devtools api-gateway automation mcp github cli-extension stdio
⚙ Agent Friendliness
35
/ 100
Can an agent use this?
🔒 Security
50
/ 100
Is it safe for agents?
⚡ Reliability
14
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
55
Documentation
45
Error Messages
0
Auth Simplicity
80
Rate Limits
0

🔒 Security

TLS Enforcement
70
Auth Strength
55
Scope Granularity
20
Dep. Hygiene
40
Secret Handling
60

Auth appears to rely on `gh` credentials (reducing need to manage tokens in the extension), but there is no documentation here about scopes, secure storage, logging behavior, or transport/security details of the MCP server itself.

⚡ Reliability

Uptime/SLA
0
Version Stability
45
Breaking Changes
0
Error Recovery
10
AF Security Reliability

Best When

You already use the GitHub CLI (`gh auth login`) and want a straightforward MCP stdio server wired into an MCP client (like VS Code).

Avoid When

You need fine-grained OAuth scopes, documented rate limits, or strong interface-level observability/error semantics for automated agents.

Use Cases

  • Enable an MCP-powered GitHub toolchain inside editors that support MCP (e.g., VS Code) using stdio transport
  • Avoid manual token configuration by leveraging existing GitHub CLI auth
  • Quick setup for agents that need GitHub operations through the MCP interface

Not For

  • Production-grade deployments that require documented SLAs, detailed API contracts, or comprehensive error/rate-limit guidance
  • Environments where adding a CLI extension is not permitted or where `gh` auth cannot be used
  • Use cases requiring an OpenAPI/SDK/REST contract beyond the MCP stdio interface

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: GitHub CLI authentication (reused by extension)
OAuth: No Scopes: No

README indicates “Zero Configuration” and “Uses your existing GitHub CLI authentication,” implying auth is handled via `gh` rather than explicit OAuth flows in this extension’s docs.

Pricing

Free tier: No
Requires CC: No

No pricing information provided in README/repo metadata.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • No information provided about MCP tool names, schemas, or error formats; agent behavior may depend on undocumented server specifics.
  • No explicit guidance on retries/backoff for rate limiting or transient failures.
  • Auth is implicit via `gh`; if `gh` credentials are missing/expired, MCP startup or calls may fail without clear documented remediation steps.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for gh-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

$3

Score Monitoring

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

Continuous monitoring

$3/mo

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

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered