| FMRS | 67 / 100 · C | 79 / 100 · B |
|---|
| Reliability | 9 / 20 | 12 / 20 |
|---|
| Security and permissions | 13 / 20 | 16 / 20 |
|---|
| Maintenance | 15 / 20 | 18 / 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
| - Developers auditing NPM dependencies within AI workflows
- Teams performing supply chain security assessments
- Users of Claude Desktop, Cursor, or VS Code
|
|---|
| 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
| - Projects outside the NPM ecosystem (e.g., pure Python/Go)
- Environments without network access to deps.dev, OSV.dev, and the npm registry
- Scenarios requiring maintenance by an official upstream vendor
|
|---|
| 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)
| - Network access to the NPM registry and external services (deps.dev, OSV.dev, OpenSSF, npms.io, GitHub)
- Read access to workspace lockfiles (pnpm-lock.yaml, package-lock., yarn.lock) for cache invalidation
|
|---|
| 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
| - Third-party READMEs and changelogs are untrusted external content; they are wrapped in tags with _meta flags but should still be handled cautiously
- Depends on availability and accuracy of external services
- Batch requests are capped at 25 packages to prevent registry enumeration; larger sets require batching
- Third-party open source project, not officially maintained by NPM or Anthropic
|
|---|
| Supported clients | Cursor, Claude Desktop, Windsurf, VS Code, Cline, Highlight AI, Augment Code, Msty AI | Claude Desktop, VS Code, Cursor |
|---|
| Tools | 4 | 19 |
|---|