Agentifact assessment — independently scored, not sponsored. Last verified Mar 6, 2026.
GitHub
MCP server for GitHub repository management and API access. Provides code collaboration tools for development agents.
Viable option — review the tradeoffs
You need your autonomous agents to manage repositories, collaborate on code, and integrate with GitHub workflows without manual intervention.
Reliable for core repo ops and collaboration; rate limits apply (5k req/hr), some advanced features need fine-grained tokens; solid 78/100 performance.
Your agents generate code/artifacts that must be versioned, reviewed, and deployed through GitHub Actions.
Seamless for CI/CD automation; secrets encrypted/not returned for security; expect occasional 403/429 on high-volume ops.
GitHub API Rate Limits
Secondary limits (5000 req/hr for authenticated) can throttle high-frequency agent ops; no direct MCP overrides.
Token Scope Gotchas
Insufficient scopes cause 403 errors on PRs/deployments/secrets; always use fine-grained tokens and test endpoints first.
GitHub Token Setup
Requires PAT or GitHub App with repo/write scopes for full management; classic tokens deprecated soon.
Trust Breakdown
What It Actually Does
Lets developers automate repository tasks like managing access, enforcing code review rules, and organizing projects through GitHub's API. It connects agent tools to GitHub so they can handle routine repository work without manual intervention.
MCP server for GitHub repository management and API access. Provides code collaboration tools for development agents.
Fit Assessment
Best for
- ✓code-generation
- ✓file-operations
- ✓database-query
- ✓knowledge-retrieval
Not ideal for
- ✗rate limit under burst load above 100 RPM
Connection Patterns
Blueprints that include this tool:
Known Failure Modes
- rate limit under burst load above 100 RPM
Score Breakdown
Protocol Support
Capabilities
Governance
- permission-scoping
- audit-log
- vulnerability-scanning
- secret-detection