mcp-jetbrains returns 429 rate limit errors with empty logs — cause and fix?
Using mcp-jetbrains with Claude, I get HTTP 429 errors after just a couple of calls; Claude reports a rate limit error but the IDE logs are empty, and it's unclear which rate limit is being hit. Other users see the same error, sometimes even on the first request. Is this a JetBrains-imposed limit and how do I fix it?
Originally asked on GitHub: https://github.com/JetBrains/mcp-jetbrains/issues/17
5 answers
Fixed: a JetBrains collaborator announced on 2025-03-26 that the issue was resolved in plugin version 1.0.17 and asked users to update. The thread does not state the exact root cause; one commenter noted that the MCP specification expects servers to implement rate limiting themselves, so the limit may be intentional on the plugin side rather than imposed by JetBrains the IDE.
Steps that appeared in the thread:
- Update mcp-jetbrains to 1.0.17. The collaborator said this fixes the issue, though nobody in the thread confirmed the update resolved it.
- Workaround: use the filesystem MCP instead. One user reported it works 100% and can edit files by replacing text, so it doesn't burn through the conversation as quickly.
- Build the plugin from a patched fork. A commenter shared commit https://github.com/minovap/mcp-server-plugin/commit/1f808fc8584d23c08896c3312098f03335490fbe (opens external site) that removes the rate limit; this requires forking the repo and building the plugin yourself.
If you still get 429 after updating to 1.0.17, the maintainers explicitly asked for IDE logs when it happens, so collect those and open a new issue.
General advice: several reporters saw the error at the very first request or after only a couple of calls, so verify which plugin version you run before assuming the limit comes from JetBrains or the model provider.
Did this work for you?What @MaXal tried on GitHub (Outcome unclear)
Collaborator announced the fix in plugin version 1.0.17 and asked users to update; no user confirmed the update resolved it in the thread.
Source: https://github.com/JetBrains/mcp-jetbrains/issues/17#issuecomment-2753697153 (opens external site)
Did this work for you?What @FilippTrigub tried on GitHub (Worked)
User stopped using mcp-jetbrains and switched to the filesystem MCP, reporting it works 100% and is reliable.
Source: https://github.com/JetBrains/mcp-jetbrains/issues/17#issuecomment-2752713563 (opens external site)
Did this work for you?What @minovap tried on GitHub (Outcome unclear)
User forked the repo and built the plugin with a patch commit that removes the rate limit; no confirmation it worked.
Source: https://github.com/JetBrains/mcp-jetbrains/issues/17#issuecomment-2747182190 (opens external site)
Did this work for you?What a GitHub user tried on GitHub (Outcome unclear)
Reporter hit 429 after a couple of calls, found empty logs, and could not determine which rate limit was hit; no fix found in the issue body.
Source: https://github.com/JetBrains/mcp-jetbrains/issues/17 (opens external site)
Did this work for you?
Related questions
- JetBrains MCP proxy: connected but no available tools in Claude
- Claude Desktop doesn't show JetBrains MCP tools: how to fix?
- How to filter which JetBrains MCP tools are exposed to Claude Code?
- How to get JetBrains IDE 'Problems' view inspection results via mcp-jetbrains?
- JetBrains MCP in Claude Desktop: 'No working IDE endpoint available' on tools/list