github-mcp-server-go
Provides a Go-based MCP (Model Context Protocol) server that exposes GitHub-related tools (e.g., repository search/create, branch and file operations, issue operations, commits, and various searches) backed by the GitHub REST API.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Uses GitHub PAT (documented via env var or Authorization header). README does not specify TLS requirements for the server, does not discuss token storage/log redaction, and does not describe rate limiting or authorization scope granularity. Prefer running behind HTTPS and ensuring tokens are not logged; consider using the least-privileged PAT.
⚡ Reliability
Best When
You want a lightweight Go MCP server that an agent can call to perform a bounded set of GitHub operations using a PAT, and you can run the server in your own environment.
Avoid When
You require robust, clearly specified rate-limit handling, OAuth with refresh tokens, or an officially maintained/high-coverage MCP interface with published error code semantics.
Use Cases
- • Enable an AI agent to perform GitHub automation tasks (repo/issue/file workflows) via MCP tools
- • Assist codebase exploration through GitHub search tools (repos/code/issues/users)
- • Automate branch/file updates and issue management from an agent without writing direct GitHub API calls
- • Internal/agent workflows that need GitHub actions exposed as discrete MCP tools
Not For
- • Production systems needing enterprise-grade governance features (fine-grained audit, policy enforcement) beyond GitHub PAT capabilities
- • Use cases requiring OAuth app flows or delegated user consent
- • Environments where server-side management of PATs is not allowed (e.g., strict secret-handling requirements)
Interface
Authentication
Authentication is via GitHub personal access token (PAT). README does not describe OAuth flows or fine-grained scope mapping.
Pricing
Repository README does not describe any hosted pricing; likely self-hosted.
Agent Metadata
Known Gotchas
- ⚠ No explicit guidance in README on idempotency for write operations (create/update/push).
- ⚠ No explicit guidance in README on pagination behavior or how tools return partial results.
- ⚠ No explicit retry/backoff guidance or rate-limit handling described for agent call patterns.
- ⚠ Tool coverage is described at a high level; absence of exact parameter schemas in README may require inspecting source to implement reliably.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for github-mcp-server-go.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
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
Scores are editorial opinions as of 2026-04-04.