home / mcp / .net types explorer mcp server

.NET Types Explorer MCP Server

A Model Context Protocol (MCP) server that provides detailed type information from .NET projects for AI coding agents.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "v0v1kkk-dotnetmetadatamcpserver": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-v",
        "/path/to/your/dotnet/projects:/workspace",
        "vrogozhin/dotnet-types-explorer-mcp:latest"
      ]
    }
  }
}

You can explore and extract rich type information from .NET projects using the .NET Types Explorer MCP Server. It exposes structured data about assemblies, namespaces, and types to AI coding agents, enabling accurate, context-aware code assistance and easier library discovery.

How to use

Use this MCP server with an MCP client to explore a .NET codebase end-to-end. Start by ensuring you can run the MCP container or native server, then configure your MCP client to connect to the server. The tools let you inspect referenced assemblies, namespaces, types, and NuGet packages, and to view type details such as methods, properties, and dependencies.

How to install

Prerequisites: Install Docker if you plan to run the server in a container. You can also build and publish a native binary if you prefer running the server directly.

# Docker installation and run (recommended for quick start)
docker pull vrogozhin/dotnet-types-explorer-mcp:latest

docker run --rm -i \
  -v /path/to/your/dotnet/projects:/workspace \
  vrogozhin/dotnet-types-explorer-mcp:latest

Native installation steps if you want to build and publish from source. You need the .NET SDK installed on your machine.

# Clone the repository and build
git clone https://github.com/V0v1kkk/DotNetMetadataMcpServer.git
cd DotNetMetadataMcpServer

dotnet build -c Release

dotnet publish -c Release -r <runtime-identifier> --self-contained false

Run the published server locally with the final start command you use in your environment. If you prefer Docker, see the Docker method above.

Configuration

Configure how the MCP client talks to the server and how the server resolves assemblies. The following example shows how to configure a Docker-based deployment for MCP usage. You can adapt paths and container options to your environment.

{
  "mcpServers": {
    "dotnettypes": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-v",
        "/path/to/your/dotnet/projects:/workspace",
        "vrogozhin/dotnet-types-explorer-mcp:latest"
      ],
      "disabled": false,
      "alwaysAllow": [],
      "timeout": 300
    }
  }
}

Notes and usage tips

The server relies on compiled assemblies to extract type information. In BuildOutput mode, you must build the project before scanning. In NuGetCache mode, you only need to restore packages. The tool does not follow references to other projects; analyze each project individually.

The NuGet integration supports multiple sources and prioritizes sources by their order in configuration. Enabled sources are queried in parallel with deduplication, and the highest-priority source’s metadata is used for duplicates.

Available tools

ReferencedAssembliesExplorer

Retrieves referenced assemblies from a .NET project with filters and pagination.

NamespacesExplorer

Retrieves namespaces from specified assemblies with filters and pagination.

NamespaceTypes

Retrieves types from specified namespaces with filters and pagination.

NuGetPackageSearch

Searches for NuGet packages on nuget.org with filtering and pagination.

NuGetPackageVersions

Retrieves version history and dependency information for specific NuGet packages.