.NET Types Explorer MCP Server

Explore .NET assemblies, namespaces, types and NuGet packages via reflection so AI agents write accurate code.

Unverified

stdio (local)

No auth

View repo 27

Add to your client

Copy the config for your MCP client and paste it into its config file.

Install / run

docker pull vrogozhin/dotnet-types-explorer-mcp:latest

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

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

Requires Docker to be installed and running.

Step-by-step guides: Add to Claude Desktop · Add to Cursor · Add to Windsurf

Before you start

.NET 9.0 SDK or later (for native installation)
A .NET project to explore (built for project-specific types; restored for NuGetCache mode)
Docker (optional, for the containerized deployment)
An MCP-compatible client (e.g. Roo Code / Cline, Cursor, Claude Desktop)

About .NET Types Explorer MCP Server

An MCP server that uses reflection and MSBuild to extract detailed type information from compiled .NET projects, helping AI coding agents understand third-party and project APIs. It walks a project top-down (referenced assemblies -> namespaces -> types) and exposes member-level detail (constructors, methods, properties, fields, events), plus NuGet package search and version/dependency lookup against nuget.org and configurable feeds. Assembly resolution supports build-output, NuGet-cache (restore-only), or automatic fallback, and every explorer tool supports wildcard filters and pagination.

Tools & capabilities (5)

ReferencedAssembliesExplorer

Retrieves the assemblies referenced by a .NET project, with wildcard full-text filtering and pagination. Requires the project file absolute path.

NamespacesExplorer

Retrieves the namespaces contained in specified assemblies of a project, with wildcard filtering and pagination.

NamespaceTypes

Retrieves detailed type information (full name, implemented interfaces, constructors, methods, properties, fields, events) for types within specified namespaces, with wildcard filtering and pagination.

NuGetPackageSearch

Searches for NuGet packages on nuget.org (and configured feeds) by query, with optional prerelease inclusion, wildcard filtering and pagination.

NuGetPackageVersions

Retrieves version history and dependency information (per target framework) for a specific NuGet package, with optional prerelease inclusion, wildcard filtering and pagination.

When to use it

Let an AI coding agent discover and inspect the real API surface of third-party NuGet libraries before writing code against them.
Explore a large .NET solution's types namespace-by-namespace with wildcard filters instead of dumping entire assemblies.
Check available NuGet package versions and their per-framework dependencies to reason about compatibility.
Browse package APIs without a full build by resolving assemblies from the NuGet cache after only a restore.

Security notes

Reads .NET projects via MSBuild/reflection from the local filesystem; the Docker config mounts a host project directory into the container at /workspace, granting the server access to every project in that path. NuGet tools make outbound requests to nuget.org and any custom feeds configured in appsettings.json. No authentication is required.

.NET Types Explorer MCP Server FAQ

Does the project need to be built first?

It depends on the resolution mode. In the default BuildOutput mode the project must be built before scanning. In NuGetCache mode only `dotnet restore` is required to inspect third-party package APIs, though project-specific types are still only available after a build.

Does it follow references to other projects in a solution?

No. It only inspects the specified project and its NuGet dependencies. To analyze multiple projects you must scan each one separately.

Can it query private or custom NuGet feeds?

Yes. Configure additional sources under Tools.NuGetSources in appsettings.json; all enabled sources are queried in parallel with priority-based deduplication. nuget.org is added by default only when no sources are configured.

How do I run it without installing the .NET SDK?

Use the Docker image vrogozhin/dotnet-types-explorer-mcp, mounting your projects directory to /workspace. It bundles MSBuild and all required dependencies.

#dotnet #csharp #reflection #code-exploration #nuget #ai-coding-agent #msbuild #docker

Alternatives to .NET Types Explorer MCP Server

Compare all alternatives →

Playwright MCP Server

Developer Tools

24k

Microsoft's official browser-automation MCP using Playwright's accessibility tree (no vision model).

Featured

Verified

stdio (local)

No auth

TypeScript

12 tools

Updated 21 days agoRepo

Context7 MCP Server

Developer Tools

28k

Up-to-date, version-specific library documentation injected into your coding agent.

Verified

stdio (local)

API key

TypeScript

2 tools

Updated 25 days agoRepo

codebase-memory-mcp

Developer Tools

16k

Code intelligence engine that indexes repos into a persistent knowledge graph for AI coding agents.

Unverified

stdio (local)

No auth

14 tools

Updated 11 hours agoRepo

Compare .NET Types Explorer MCP Server with:

vs Playwright MCP Server vs Context7 MCP Server vs codebase-memory-mcp vs Serena