.NET Metadata

v1.0.0Developer Toolsstable

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

dotnetmetadatamcpservermcpai-integration
Share:
26
Stars
0
Downloads
0
Weekly
0/5

What is .NET Metadata?

.NET Metadata is a Model Context Protocol (MCP) server that allows AI assistants like Claude, Cursor, and VS Code to model context protocol (mcp) server that provides detailed type information from .net projects for ai coding agents.

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

This server falls under the Developer Tools category on MCPgee, the world's largest MCP server directory with 33,000+ servers.

Features

  • A Model Context Protocol (MCP) server that provides detailed

Use Cases

Provide type information from .NET projects to AI coding agents.
Enable type-aware code completion and analysis.
Support cross-project type discovery for C# development.
V0v1kkk

Maintainer

LicenseApache-2.0
Languagec#
Versionv1.0.0
UpdatedMay 6, 2026
Statushealthy
Maintenanceactive

Works with

ClaudeOpenAIwindowsmacoslinux

Installation

Manual Installation

npx dotnetmetadatamcpserver

Configuration

Configuration Details

Config File

claude_desktop_config.json

Performance

Response Metrics

Response Time< 200ms
ThroughputMedium

Resource Usage

Memory UsageLow
CPU UsageLow

How to Set Up and Use .NET Metadata

DotNetMetadataMcpServer is an MCP server that provides AI coding agents with deep type information from .NET projects — exposing namespaces, type definitions, methods, properties, fields, events, and NuGet package metadata from compiled assemblies or the NuGet cache. It supports three assembly resolution modes (BuildOutput, NuGetCache, and Auto) and can be run as a self-contained binary or as a Docker container mounted to your project directory. .NET developers use it to give AI assistants like Claude accurate, up-to-date type signatures without relying on training data, enabling precise code generation and cross-project type discovery.

Prerequisites

  • .NET 9.0 SDK or later installed
  • Your .NET project must be built (dotnet build) for BuildOutput mode, or packages restored for NuGetCache mode
  • Docker (optional, for the containerized deployment)
  • An MCP-compatible client such as Claude Desktop or Claude Code
1

Clone and build the server

Clone the repository and build a Release binary.

git clone https://github.com/V0v1kkk/DotNetMetadataMcpServer.git
cd DotNetMetadataMcpServer
dotnet build -c Release
2

Publish a self-contained binary

Publish for your target runtime to get a single executable you can reference in your MCP config.

dotnet publish -c Release -r linux-x64 --self-contained false
# Output will be in: bin/Release/net9.0/linux-x64/publish/
3

Alternative: use the Docker image

Pull the pre-built Docker image and run it with your project directory mounted as a volume.

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
4

Build your .NET project

Ensure your target .NET project is built so the server can resolve assemblies from the build output.

cd /path/to/your/dotnet-project
dotnet build -c Debug
5

Configure Claude Desktop

Add the server to your claude_desktop_config.json, pointing to the published binary and specifying the home directory.

{
  "mcpServers": {
    "dotnet-metadata": {
      "command": "/path/to/DotNetMetadataMcpServer/bin/Release/net9.0/linux-x64/publish/DotNetMetadataMcpServer",
      "args": ["--homeEnvVariable", "/home/user"],
      "timeout": 300
    }
  }
}

.NET Metadata Examples

Client configuration

Claude Desktop configuration using the Docker image, mounting the project workspace.

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

Prompts to try

Example prompts for .NET type discovery and code assistance.

- "List all namespaces in the MyCompany.Core assembly"
- "Show me all public methods on the UserRepository class in the MyApp.Data namespace"
- "Search NuGet for packages related to JWT authentication and show the latest versions"
- "What interfaces does the OrderService class implement in my solution?"

Troubleshooting .NET Metadata

Server returns empty results or cannot find assemblies

Ensure your .NET project has been built with 'dotnet build' before querying. In BuildOutput mode the server reads from the build output directory — if the project has not been compiled, no assemblies are available. Switch to NuGetCache or Auto mode in appsettings.json if build output is not available.

Docker container exits immediately with volume mount errors

Check that the host path in the -v flag exists and uses absolute paths. On macOS, ensure Docker Desktop has permission to access the directory in Settings > Resources > File Sharing.

MCP client times out waiting for the server to respond

Set a higher timeout in your MCP config (e.g. 300 seconds). The first query on a large solution can take 10-30 seconds while the server resolves and indexes assemblies. Subsequent queries are faster due to in-process caching.

Frequently Asked Questions about .NET Metadata

What is .NET Metadata?

.NET Metadata is a Model Context Protocol (MCP) server that model context protocol (mcp) server that provides detailed type information from .net projects for ai coding agents. It connects AI assistants to external tools and data sources through a standardized interface.

How do I install .NET Metadata?

Follow the installation instructions on the .NET Metadata GitHub repository. Clone the repo, install dependencies, and add the server config to your AI client.

Which AI clients work with .NET Metadata?

.NET Metadata works with all major MCP-compatible AI clients including Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and Cline.

Is .NET Metadata free to use?

Yes, .NET Metadata is open source and available under the Apache-2.0 license. You can use it freely in both personal and commercial projects.

Browse More Developer Tools MCP Servers

Explore all developer tools servers available in the MCPgee directory. Each server includes setup guides for Claude, Cursor, and VS Code.

Quick Config Preview

{ "mcpServers": { "dotnetmetadatamcpserver": { "command": "npx", "args": ["-y", "dotnetmetadatamcpserver"] } } }

Add this to your claude_desktop_config.json or .cursor/mcp.json

Read the full setup guide →

Ready to use .NET Metadata?

Browse our complete directory of 33,000+ MCP servers, read setup guides for your editor, and start building with the Model Context Protocol.

33,000+ ServersFree & Open SourceStep-by-Step Guides