| FMRS | 67 / 100 · C | 79 / 100 · B |
|---|
| Reliability | 9 / 20 | 12 / 20 |
|---|
| Security and permissions | 13 / 20 | 18 / 20 |
|---|
| Maintenance | 15 / 20 | 16 / 20 |
|---|
| Documentation | 16 / 20 | 18 / 20 |
|---|
| Setup experience | 14 / 20 | 15 / 20 |
|---|
| Best for | - Developers using MCP-capable AI coding tools like Cursor, Claude Desktop, Windsurf, or VS Code
- Users who frequently need up-to-date docs/code from one or many public GitHub projects
- Teams wanting a zero-install, zero-config remote documentation service
| - Engineering teams scaling AI coding agents while controlling spend
- Platform teams that need auditable, rollback-aware agent execution records
- Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
|
|---|
| Not for | - Accessing private repositories or content requiring authentication (GitMCP only serves publicly available content and has no auth)
- Users who need write access — creating commits, PRs, or issues — since GitMCP only provides read-only documentation/code retrieval
- AI tools that don't support the Model Context Protocol
| - Developers who just want a simple code-completion helper without run governance
- Teams unwilling to accept local JSONL run records with HMAC signing
- Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
|
|---|
| Required permissions | - No GitHub authentication required; only accesses content that is already publicly available
- Respects robots.txt directives when accessing GitHub Pages sites
- Runs as a remote cloud service, so the client must be allowed to make outbound network requests (tool calls typically require user approval)
| - Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
- Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
- Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
- Execution of user-configured verifier commands (e.g. npm test)
|
|---|
| Risks and side effects | - As a third-party remote service, GitMCP explicitly states it is not affiliated with GitHub or any AI tool vendor, so trust in the hosted service should be evaluated independently
- The fetch_url_content tool may retrieve third-party external links referenced in a repo's docs, so content quality/safety depends on the original source
- The maintainers state no personal data or queries are stored, but users relying on external hosted infrastructure should weigh this against their own compliance needs
| - Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
- Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
- Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
- Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
|
|---|
| Supported clients | Cursor, Claude Desktop, Windsurf, VS Code, Cline, Highlight AI, Augment Code, Msty AI | Claude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue |
|---|
| Tools | 4 | 0 |
|---|