Resharper CLI MCP server
ReSharper CLI inspection/cleanup via MCP. Unofficial: not affiliated with or endorsed by JetBrains.
B83/100grade B
Adoption
New
0 stars
Reviews
Write oneNobody has reviewed Resharper CLI yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Resharper CLI tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it
no findings
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
The registry entry has no remote endpoint or installable package.
Resharper CLI: common questions
- Is Resharper CLI MCP server safe?
- Mostly: it is graded B (83/100). Read the Resharper CLI safety report
- Does Resharper CLI need an API key?
- No secret keys are declared. It reads 9 settings from the environment.
- Is Resharper CLI maintained?
- The last commit was 2 days ago (2026-09-19). The latest release is v1.7.0.