Resharper MCP Server

Resharper MCP server exists for a simple reason — assistants are far more useful when they can act on Resharper directly instead of describing what you should do. ReSharper CLI inspection/cleanup via MCP. Unofficial: not affiliated with or endorsed by JetBrains.

What you get

resharper-cli-mcp is an MCP server that runs JetBrains' ReSharper command-line tools and exposes them to C# coding agents over stdio. It is unofficial — not affiliated with or endorsed by JetBrains.

What the assistant can call

Once Resharper is connected, these are the calls the assistant has available:

• resharper_inspect — no
• resharper_cleanup — yes

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

You will need 2 environment variables: JB_SOLUTION_PATH, JB_SETTINGS_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Resharper's toolset — resharper_inspect, resharper_cleanup — is a fair guide to whether it matches your workflow. It is maintained by andypgray; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the resharper mcp server does with a few real requests.