Skip to content

Roslyn Workbench MCP — 0.1.0-beta.294

Roslyn Workbench MCP is a local stdio server for Roslyn-powered C# inspection and transactional refactoring. The 0.1.0 beta follows successful evaluation across several solutions, including a large enterprise solution, and is intended for wider feedback on trusted repositories. Tool contracts, configuration and persisted state may change before v1; review release notes before upgrading and finish or discard active transactions before replacing the server.

What is included

  • Persistent Workspace sessions and semantic inspection of symbols, references, diagnostics, code structure and change impact.
  • Bounded results with snapshot-aware selectors and a versioned tool reference for deeper guidance.
  • Mutation staging, previews, undo/redo, rollback, explicit commit, conflict detection and durable recovery.
  • Roslyn Code Action discovery, Fix All preparation and staging through the same transaction boundary.
  • Local correlated diagnostics and an explicit, user-consented reporting workflow.

Requirements and support

A supported .NET 10 SDK and an MCP client able to launch a local stdio process are required. Install the SDKs/build tooling needed by the projects being analysed as well. Windows x64, Linux x64 and WSL2 x64 are supported. macOS x64 and ARM64 are best effort; Windows ARM64 and Linux ARM64 are not supported release targets.

Only open fully trusted repositories. MSBuild evaluation, project analysers and plugins can execute with the Host's permissions; Roslyn Workbench is not a sandbox. Stop other tools from changing affected source or directory structure during commit application and startup recovery.

Install from NuGet.org

The 0.1.0 beta is distributed through NuGet.org; GitHub Packages credentials are not required.

dotnet tool install --global Roslyn.Workbench.Mcp --version 0.1.0-beta.294
roslyn-workbench-mcp --version

For an existing installation, use dotnet tool update --global Roslyn.Workbench.Mcp --version 0.1.0-beta.294. The reported version must match the release.

Connect and evaluate

Configure the MCP client to launch roslyn-workbench-mcp. See the release's getting-started guidance for state-directory configuration, Workspace loading and a first transaction. The running server's tools/list is authoritative for its enabled tool set.

Client support and approval policy determine whether optional elicitation prompts appear. If reporting is blocked, no error report is sent. Review prepared payloads carefully: exception messages may contain source text, paths, identifiers or secrets. Choose the option without exception messages when needed.

Known limitations

  • This is not a compatibility-stable release. Handles, error records and Code Action references are process-local and expire; restart requires rediscovery.
  • Only supported SDK-style C# projects participate in queries. Unsupported projects may be skipped; evaluated external documents are read-only and generated/non-addressable source is excluded.
  • Concurrent query support does not permit concurrent mutation of the same transaction. One Workspace owns the process's active transaction slot.
  • The Plugins NuGet package, supported plugin-authoring documentation, curated plugin repository and native installers are deferred. Trusted source-built plugins still work in the existing runtime.
  • External pull requests are not accepted before v1 preparation. There is no release-cadence guarantee.

Feedback and removal

Use Issues for reproducible defects and documentation problems, Q&A for help, and Ideas for exploratory proposals. Follow the security policy for private vulnerability reports. Include version, platform and redacted reproduction details, not private source or credentials.

Remove the client's server entry, stop the process and run dotnet tool uninstall --global Roslyn.Workbench.Mcp. Keep unresolved recovery state until recovery is understood; see troubleshooting and removal.

The package is MIT-licensed. Release assets include symbols, checksums, source identity and a coverage snapshot. Performance comparisons are advisory and are included only when comparable manual evidence exists.