gitmcp.io down: Cloudflare rate limit — is there a user-side fix?
The hosted gitmcp.io service for the git-mcp tool (idosal/git-mcp) became unreachable, with the issue reporting Cloudflare rate limits as the cause. No client (Claude Code, Cursor, VS Code), OS, or exact error message was included in the thread. Was this a transient server-side outage, and is there anything to fix on the user side?
Originally asked on GitHub: https://github.com/idosal/git-mcp/issues/245
1 answer
Status: explained — the outage was temporary throttling of the hosted gitmcp.io service, not a bug in git-mcp or a local configuration issue.
The issue was opened on 2026-05-11 reporting that gitmcp.io was unavailable due to Cloudflare rate limits. A comment the same day said "Up", and the maintainer later (2026-05-17) confirmed the service had been throttled for a few hours and that Cloudflare restored it with full backing. No client, OS, or exact error message was included in the thread, and no user-side fix was provided.
Practical takeaway: if gitmcp.io shows a rate-limit or throttling page again, this is a known transient failure mode of the hosted service. Wait a few hours and retry before debugging your local MCP server configuration or the git-mcp installation. That last part is general advice: the thread itself contains no config change, CLI flag, or version that fixes the issue, because none was needed.
Did this work for you?
Related questions
- Cursor: Combined server and tool name length (63) exceeds 60 characters with git-mcp
- VS Code MCP server crashes: 'Error reading SSE stream: TypeError: terminated'
- git-mcp stuck on "connecting" in Claude Code — how to fix?
- git-mcp via mcp-remote in Amazon Q CLI: HTTP 403 'Cookies must be enabled to use GitHub'
- Does git-mcp support opting out via robots.txt or LICENSE files?