npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

roslyn-mcp-server

v1.1.0

Published

An unconditionally robust MCP server for Microsoft Roslyn Language Server (C#)

Readme

Roslyn MCP Server

A robust, TypeScript-based Model Context Protocol (MCP) server integration for the official Microsoft Roslyn Language Server (C#).

This standalone tool connects the Model Context Protocol with the C# Language Server Protocol (LSP), allowing AI agents—such as Claude Desktop, Cursor, and other MCP-compatible clients—to semantically understand, navigate, and analyze your C# and .NET codebases just like a native IDE.

Features

  • Full C# LSP Coverage: Exposes core semantic tools including advanced hover documentation, definition seeking, project-wide references, and diagnostic build errors.
  • High Stability: Internally manages didOpen document synchronization and handles LSP buffer states automatically, preventing the NullReferenceException bugs occasionally seen in other LSP wrappers.
  • Zero Configuration: Installs seamlessly and falls back to tracking your Current Working Directory dynamically if you don't enforce an absolute project path.

Global Installation

npm install -g roslyn-mcp-server

Pre-requisites

You must have the .NET 8 SDK (or above) installed along with the official roslyn-language-server dotnet tool.

dotnet tool install -g Microsoft.CodeAnalysis.LanguageServer

How to Configure in MCP Clients

Add the following to your MCP Host configurations (e.g., claude_desktop_config.json, mcp_config.json, etc.):

{
  "mcpServers": {
    "csharp-lsp": {
      "command": "roslyn-mcp-server",
      "args": ["<OPTIONAL_ABSOLUTE_PATH_TO_CSHARP_PROJECT>"]
    }
  }
}

Tip: If you do not provide <OPTIONAL_ABSOLUTE_PATH_TO_CSHARP_PROJECT> in args, the server will gracefully fallback and index the Current Working Directory (CWD).

Exposed MCP Tools

  • csharp_hover: Fetches the semantic type or variable definitions in markdown formatting precisely at line/column boundaries.
  • csharp_definition: Retrieves the concrete origination URI of the symbol.
  • csharp_references: Locates all occurrences or assignments of methods/properties across the entire initialized workspace.
  • csharp_diagnostics: Summarizes the active syntax errors and build warnings on a targeted component.
  • csharp_workspace_symbol: Queries fuzzy name references broadly across large infrastructures without needing to know exact paths.

Local Development

  1. Run npm install to gather dependencies.
  2. Run npm run build to compile the TypeScript payload into dist/.
  3. Use npm start to execute the production payload, or use the provided src/test.ts to perform end-to-end local debugging simulating an MCP client.