Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 5
- 4 1
- 3 6
- 2 1
- 1 0
Trust in production
- Trust it - 8%
- With caveats - 77%
- Wouldn't - 15%
62% would recommend this server
How reviewers scored it
- Setup & docs 3.7
- Auth experience 3.3
- Reliability 3.7
- Maintainer responsiveness 4.2
Why it got a C
Built into JetBrains IDEs through a bundled, open-source plugin (it replaces the deprecated JetBrains/mcp-jetbrains proxy), off until you enable it, and very actively developed. It listens only on 127.0.0.1 and checks the Host header. A PyCharm Jupyter-tools RCE (CVE-2026-75060) was fixed in 2026.2.1, so stay current. Tools edit files, apply patches and run configurations; terminal commands ask first unless brave mode is on, so leave it off. Biggest deduction: the client endpoint has no login, so any local process can call it, and it runs model-written shell commands.
How to connect
Built in (2025.2+): Settings | Tools | MCP Server > Enable MCP Server, then Auto-Configure each clientIs JetBrains IDE MCP Server safe?
Is JetBrains IDE MCP Server safe to use?
JetBrains IDE MCP Server grades C (usable with care). There is no login: anything that can start or reach it gets its full access. It shells out to helper programs or serves HTTP without enforced TLS, so keep it local and isolated.
Does JetBrains IDE MCP Server have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does JetBrains IDE MCP Server support authentication?
No. It has no login of its own, so limit who and what can start it.
Alternatives in Developer Tools
- A Atlassian Rovo MCP ServerOfficial hosted Atlassian server for Jira, Confluence, Jira Service Management, Compass, Bitbucket, Loom, Goals, Projects, and Teams, with OAuth 2.1 sign-in.
- A Buildkite MCP ServerOfficial Buildkite server for pipelines, builds, jobs, logs, annotations, and Test Engine data, hosted or local.
- A Dynatrace Remote MCP ServerDynatrace's hosted MCP server, running inside your Dynatrace SaaS environment, to run and explain DQL, look into problems, vulnerabilities and Kubernetes events, and forecast time series.
- A GitHub MCP ServerOfficial GitHub server for repos, issues, pull requests, Actions, and code security, hosted or local.
- A GitLab MCP ServerGitLab's built-in MCP server for projects, merge requests, work items, code, and CI pipelines, on GitLab.com or your own instance.
Embed this badge
[](https://trustedmcp.io/servers/jetbrains-mcp-server)<a href="https://trustedmcp.io/servers/jetbrains-mcp-server"><img src="https://trustedmcp.io/badge/jetbrains-mcp-server.svg" alt="TrustedMCP grade C" height="80"></a>Community reviews
Solid core, fiddly setup
I like it, with reservations. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. There is no auth layer, so whatever can reach it can use it. I keep it local only. Recommended, with sensible guardrails.
Used for Pairing with Claude Code on a monorepo
- Setup & docs 2/5
- Auth experience 2/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Solid and well behaved
Replaced a homegrown script with JetBrains IDE MCP Server and have not looked back. No access control at all, it runs with my permissions. Fine on my laptop, not on a shared box. Keep permissions tight and it is a good tool.
Used for Looking up JetBrains IDE data without leaving the editor
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Good defaults, good docs
Hooked JetBrains IDE MCP Server into Claude Code and it worked on the first try. Nothing stops a misbehaving agent from using every tool it exposes, so I trimmed the tool list. I would use it in prod, but only with a human approving writes.
Used for Internal developer assistant
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Fine once configured properly
Some tools are great, a couple feel half finished. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Nothing stops a misbehaving agent from using every tool it exposes, so I trimmed the tool list. Keep permissions tight and it is a good tool.
Used for Debugging sessions in Cursor
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Does the job, docs could be better
It does the job, but it took some tweaking. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Keeping it to local experiments for now.
Used for Debugging sessions in Cursor
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Easy win for our agent setup
I use this almost daily. There is no auth layer, so whatever can reach it can use it. I keep it local only. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent.
Used for Onboarding new devs with an agent that answers repo questions
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Needs more maintenance love
I wanted to like this one. You can tell it is actively maintained, the rough edges keep getting fixed. Nothing stops a misbehaving agent from using every tool it exposes, so I trimmed the tool list.
Used for Code review summaries for pull requests
- Setup & docs 3/5
- Auth experience 2/5
- Reliability 2/5
- Maintainer responsiveness 3/5
Works, just lock it down
Took longer to configure than I expected. Updates land regularly, and nothing broke when I upgraded. Nothing stops a misbehaving agent from using every tool it exposes, so I trimmed the tool list. Fine in production if you sandbox it.
Used for Scripting routine maintenance tasks
- Setup & docs 3/5
- Auth experience 2/5
- Reliability 3/5
- Maintainer responsiveness 4/5
No complaints after a month
Tried it on a side project first, then rolled it out at work. There is no auth layer, so whatever can reach it can use it. I keep it local only. Releases come often and the changelog is clear. It is in our production agent and I sleep fine.
Used for Letting a coding agent open and triage issues
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Decent, not set-and-forget
Works well enough for what I need. Filed an issue and got a reply within two days. There is no auth layer, so whatever can reach it can use it. I keep it local only. Not something I would put in production yet.
Used for CI failure investigation
- Setup & docs 3/5
- Auth experience 4/5
- Reliability 2/5
- Maintainer responsiveness 5/5
Saves me a context switch every hour
Simple to set up in Cursor, simple to reason about. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. No access control at all, it runs with my permissions. Fine on my laptop, not on a shared box. Worth it, just do not skip the hardening steps.
Used for Generating boilerplate from existing patterns
- Setup & docs 5/5
- Auth experience 3/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Trustworthy enough for real work
Set this up for our team after comparing a few options. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Worth it, just do not skip the hardening steps.
Used for Keeping project tickets in sync with code changes
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 4/5
OK for read-only work
Useful tool, though I would not hand it to a junior unsupervised. No access control at all, it runs with my permissions. Fine on my laptop, not on a shared box. I would use it in prod, but only with a human approving writes.
Used for Automating release notes
- Setup & docs 3/5
- Auth experience 2/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.