Remote MCP Server Using .NET SDK Resources and Tools

This repository contains a sample remote Model Context Protocol (MCP) server built with the .NET SDK and ModelContextProtocol.AspNetCore.

The server exposes:

• MCP tools (for operations such as ping and weather lookup)
• MCP resources (for server information and runtime status)
• HTTP MCP endpoint at /mcp
• Health endpoint at /api/healthz

What This Project Is

The project is an ASP.NET Core MCP server that can be used by MCP clients (including VS Code MCP client configuration in .vscode/mcp.json).

Source layout:

• src/McpServer/McpServer: MCP host application
• src/McpServer/WeatherService: weather service used by the weather tool
• scripts: PowerShell scripts to list and call MCP tools/resources

Prerequisites

• Windows with PowerShell (pwsh or Windows PowerShell)
• .NET SDK 10.0 (project targets net10.0)
• VS Code with MCP client support
• Internet access for weather lookup (uses Open-Meteo APIs)

Run The Server Locally

From the repository root:

dotnet restore .\src\McpServer\McpServer.slnx
dotnet run --project .\src\McpServer\McpServer\McpServer.csproj

Default server URL:

• http://0.0.0.0:8081/mcp

Notes:

• Port is controlled by FUNCTIONS_CUSTOMHANDLER_PORT (defaults to 8081).
• Health check endpoint: http://localhost:8081/api/healthz

VS Code MCP Client Configuration

This repository already includes .vscode/mcp.json:

{
  "servers": {
    "local-mcp-server": {
      "url": "http://0.0.0.0:8081/mcp",
      "type": "http"
    }
  }
}

If needed, update url to match your local port.

Exposed MCP Tools

Defined in src/McpServer/McpServer/McpServerTools.cs:

• Ping(message: string)
  • Verifies server responsiveness and optionally echoes a message.
• GetWeather(city: string)
  • Returns current weather data for the requested city.

Tool names shown by MCP clients can be normalized by the MCP library. Use tools/list (or the script below) to confirm exact callable names in your environment.

Exposed MCP Resources

Defined in src/McpServer/McpServer/McpServerResources.cs:

• ServerInfo
  • Basic server metadata (name, version, host info, runtime framework, OS, capabilities).
• Status
  • Current runtime status (health, timestamp, uptime, memory, CPU usage).

Use resources/list (or the script below) to view exact resource URIs returned by the server.

How To Create A New MCP Resource

Use this pattern from McpServerResources when adding a new resource.

1. Add or reuse a resource container class and mark it with [McpServerResourceType].
2. Add a public method and mark it with [McpServerResource].
3. Add a [Description("...")] attribute so clients can show meaningful metadata.
4. Return serializable content (string or JSON payload).
5. Ensure the resource type is registered in startup (already done in this project with .WithResources<McpServerResources>()).
6. Run the server and validate with resources/list and resources/read.

Example (new resource in McpServerResources.cs):

[McpServerResource]
[Description("Returns current process metrics")]
public string ProcessMetrics()
{
    var data = new
    {
        Timestamp = DateTimeOffset.UtcNow,
        WorkingSet = Environment.WorkingSet,
        Memory = GC.GetTotalMemory(false),
        ProcessorCount = Environment.ProcessorCount
    };

    return JsonSerializer.Serialize(data, new JsonSerializerOptions { WriteIndented = true });
}

After adding the method, test it:

# 1) Start server
 dotnet run --project .\src\McpServer\McpServer\McpServer.csproj

# 2) List resources and find the URI generated for ProcessMetrics
 .\scripts\list-mcp-server-resources.ps1

# 3) Read the resource (example URI pattern)
 .\scripts\call-mcp-resources.ps1 -ResourceUri "resource://mcp/process_metrics"

How your current implementation works:

• ServerInfo() provides static/dynamic host and runtime

... View full README on GitHub