TropinAlexey/MCP-Server-Extension-for-JetBrains-Rider

A JetBrains Rider plugin that extends the built-in MCP Server with full IDE observability and control tools for AI agents.
What's New →
## Why This Exists
The built-in MCP server covers files, search, and running things, but most of what it exposes either duplicates what MCP clients already do better natively (file reading/editing, git operations) or misses the IDE surfaces that matter day to day.
The core problem: your AI assistant is blind to what happens inside the IDE.
A programmer staring at Rider sees dozens of information surfaces simultaneously — Build Output streaming in real time, Problems panel lighting up with errors, test runner trees expanding, progress bars showing indexing status, notifications popping up about package restores. An MCP client sees none of this.
When a build hangs, you see the output frozen at "Building Project7..." — your assistant sees nothing. When a test run or Publish is still going, you see the progress bar — your assistant only knows it started. When the app you are debugging prints an exception, you see it in the Debug console — your assistant sees the debugger, but not the app's output.
This plugin bridges that gap. It gives any MCP-compatible client (Claude Code, Codex, Gemini CLI, GitHub Copilot, Cursor, Junie, Windsurf, Continue, custom agents) the same situational awareness a programmer has — the ability to see what the IDE is doing, what it's showing, and what's happening in the background.
### What the stock MCP plugin provides vs. what this adds
Rider 2026.2 ships a strong built-in MCP server. This plugin covers what it does not, and steers agents to the built-in tool where that one is the better choice (state as of Rider 2026.2):
| Capability | Built-in MCP Server | This Extension |
| Read/edit files, search, refactorings | ✅ readfile, applypatch, search, renamerefactoring, extractmethod, safedelete, … | — |
| Code analysis of files | ✅ getfileproblems, lintfiles, reformatfile | — |
| Build solution | ✅ buildsolutionstart + buildsolutionstate (result + problems with file/line) | — (raw build log via ridertoolwindow(windowId='Build')) |
| Problems / solution-wide errors | Partial: getprojectproblems reads the Problems View | ✅ ridersweaerrors: Solution Wide Analysis counts per project, top codes, samples |
| Run an app / run configurations | ✅ getrunconfigurations, executerunconfiguration (output, exit code, one-time args/env) | ✅ riderrunconfig(action=create/update/delete) — persistent configs, clone with args/env |
| Debugger | ✅ xdebug: sessions, breakpoints, stack, evaluate, attach, memory | ✅ the debugged app's own stdout: ridertoolwindow(windowId='Debug', section='Console') |
| Test runner | Partial: run a test from a gutter run point via executerunconfiguration; findTests locates the test file | ✅ ridertests(action=run/runandwait/results/rerunfailed): scoped by filter/class/method, structured results with stack traces |
| Publish | Partial: run a Publish configuration via executerunconfiguration | ✅ riderpublish streams the output and records Configuration/RID/publishDir for riderworkspaceconfig |
| Workspace build configuration | ❌ | ✅ riderworkspaceconfig: Configuration, Platform, TargetFramework, exePath per runnable project |