feat: Add Intelij Rider for Autoconfig support

[DeTandtThibaut]

Summary

• Adds RiderConfigurator to enable automatic MCP configuration for JetBrains Rider with GitHub Copilot users
• Implements platform-specific config paths for Windows, macOS, and Linux
• Uses IsVsCodeLayout = true as Rider stores settings in VS Code-compatible format

Config Paths

• Windows: %APPDATA%/JetBrains/Rider/mcp.json
• macOS: ~/Library/Application Support/JetBrains/Rider/mcp.json
• Linux: ~/.config/JetBrains/Rider/mcp.json

Test Plan

☐ Open MCP for Unity window in Unity Editor
☐ Verify "Rider GitHub Copilot" appears in the client list
☐ Test "Check Status" button with Rider installed
☐ Test "Configure" button to auto-configure MCP settings

Summary by CodeRabbit

• New Features
  • Rider GitHub Copilot integration for the Unity Editor with automatic platform detection and support for Windows, macOS, and Linux.
  • In-editor, step-by-step installation and configuration guidance to help set up the GitHub Copilot plugin and MCP settings in Rider.

✏️ Tip: You can customize this high-level summary in your review settings.

Summary by CodeRabbit

• New Features
  • Added support for configuring GitHub Copilot in Rider IDE with platform-specific setup paths
  • Includes a detailed step-by-step installation guide for Rider users

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

A new RiderConfigurator class is introduced that extends JsonFileMcpConfigurator to configure the Model Context Protocol for JetBrains Rider with GitHub Copilot. The class initializes platform-specific mcp.json paths and provides a four-step installation guide for users.

Changes

Cohort / File(s)	Summary
Rider Configurator MCPForUnity/Editor/Clients/Configurators/RiderConfigurator.cs	New public class extending JsonFileMcpConfigurator. Constructor initializes McpClient with Rider-specific configuration including platform-specific mcp.json paths and VSCode layout settings. Implements GetInstallationSteps() override returning four-step installation sequence for configuring Copilot in Rider.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify proper base class initialization and inheritance pattern consistency
• Validate platform-specific mcp.json paths are correct for all supported platforms
• Confirm installation steps are accurate and user-friendly

Poem

🐰 A Rider takes flight through the code so bright,
With Copilot whispering in the IDE night,
Four steps to configure, now easy and clear,
The Rabbit hops onward—innovation is here! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding Rider (JetBrains IDE) support for automatic MCP configuration with GitHub Copilot integration.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

MCPForUnity/Editor/Clients/Configurators/RiderConfigurator.cs (1)

20-25: Installation steps are minimal; consider adding Rider‑specific pointers later

The four installation steps are clear and usable as a starting point. As a follow‑up (not blocking), you might later expand them with Rider‑specific navigation hints (e.g., where to find the plugin/settings, or how to open the config directory) to reduce friction for less experienced users.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8a17cde and ece1fac.

📒 Files selected for processing (1)

• MCPForUnity/Editor/Clients/Configurators/RiderConfigurator.cs (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: msanatan
Repo: CoplayDev/unity-mcp PR: 401
File: MCPForUnity/Editor/Clients/Configurators/VSCodeConfigurator.cs:10-18
Timestamp: 2025-11-27T21:09:35.011Z
Learning: VS Code GitHub Copilot MCP configuration supports mcp.json files placed directly in the Code/User directory: %APPDATA%\Code\User\mcp.json on Windows, ~/Library/Application Support/Code/User/mcp.json on macOS, and ~/.config/Code/User/mcp.json on Linux. This is in addition to workspace-scoped .vscode/mcp.json files.

🧬 Code graph analysis (1)

MCPForUnity/Editor/Clients/Configurators/RiderConfigurator.cs (1)

MCPForUnity/Editor/Models/McpClient.cs (1)

• McpClient (5-55)

🔇 Additional comments (1)

MCPForUnity/Editor/Clients/Configurators/RiderConfigurator.cs (1)

10-16: Confirm .NET/Unity support for Environment.SpecialFolder.UserProfile and Rider path layout

The OS-specific paths look correct and match the PR description, but there are two things worth double-checking:

• That Environment.SpecialFolder.UserProfile is available and behaves as expected on all Unity/.NET targets you support (especially older LTS versions).
• That GitHub Copilot in Rider actually resolves mcp.json from the non‑versioned JetBrains/Rider directory (and not a versioned folder like Rider2024.2).

If both assumptions are already validated in manual tests, this is fine as‑is; otherwise, it may be safer to align with whatever pattern you used in VSCodeConfigurator or factor out a small helper for “user home + config subpath” to keep behavior consistent.