Context7 MCP server rate limits my first request in Trae — is it my config or Context7?
I connected the Context7 MCP server (upstash/context7) in Trae, and my very first request was immediately rate limited even though I have never used Context7 before. Another user reports the same behavior on the first try. Is this a Context7-side problem or our configuration, and is there a fix?
Originally asked on GitHub: https://github.com/upstash/context7/issues/438
2 answers
Fixed: Context7 maintainers said on 2025-07-21 that they provided a fix, asked the reporters to retry, and closed the issue as completed after a maintainer said on 2025-07-24 that the issue seems to be solved.
The rate limiting was on the Context7 side. A contributor explained that Context7 currently rate-limits by IP address to prevent over-usage, which can block even a brand-new user, and that this approach is "not perfect." They also said per-tenant rate limits via an API key are planned. No client-side configuration problem was identified in the thread.
What to do: just retry the request. The maintainers asked affected users to retry after deploying the fix. General advice: if you still hit the rate limit, wait a bit and try again later; this thread does not specify which IPs are affected or how long limits last.
Did this work for you?What @kerimala tried on GitHub (Didn't work)
User in Trae made their very first Context7 MCP server request and was immediately rate limited, despite never having used Context7 before.
Source: https://github.com/upstash/context7/issues/438 (opens external site)
Did this work for you?
Related questions
- How does context7 decide which docs are trusted? What is trustScore?
- Cursor MCP "Failed to create client" with @upstash/context7-mcp using npx: fix
- Does Context7 support GitLab repositories now, and where do I add one?
- Is there an official public Docker image for the context7 MCP server?
- Context7 MCP in Cursor: "Client closed" / "spawn npx ENOENT"