{
"mcpServers": {
"remote-mcp-servers-using-dotnet-sdk-prompts": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
MIT. View license →
Is it maintained?
Last commit 23 days ago. 1 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
MCP Security Weekly
Get CVE alerts and security updates for Remote MCP Servers Using Dotnet Sdk Prompts and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
This repository contains a sample remote Model Context Protocol (MCP) server built with the .NET SDK and ModelContextProtocol.AspNetCore.
The server exposes:
/mcp/api/healthzThe 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 applicationsrc/McpServer/WeatherService: weather service used by the weather toolscripts: PowerShell scripts to list and call MCP tools/resources/promptspwsh or Windows PowerShell)10.0 (project targets net10.0)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/mcpNotes:
FUNCTIONS_CUSTOMHANDLER_PORT (defaults to 8081).http://localhost:8081/api/healthzThis 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.
Defined in src/McpServer/McpServer/McpServerTools.cs:
Ping(message: string)
GetWeather(city: string)
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.
Defined in src/McpServer/McpServer/McpServerPrompts.cs and registered in src/McpServer/McpServer/Program.cs with:
.WithPrompts<McpServerPrompts>();
Available prompts:
default_prompt
weather_query_guide(userContext?: string)
userContext: extra location or preference context appended to the prompt output.weather_data_interpretation
Use prompts/list to see exact prompt names and argument metadata in your runtime.
Use this pattern from McpServerPrompts when adding a new prompt.
[McpServerPromptType].[McpServerPrompt].[Description("...")] attribute so clients can show meaningful metadata.[Description("...")] attributes for better client introspection.string or Task<string>..WithPrompts<McpServerPrompts>()).prompts/list and prompts/get.Example (new prompt in McpServerPrompts.cs):
[McpServerPrompt]
[Description("Provides concise guidance for travel weather planning")]
public Task<string> TravelWeatherGuide(
[Description("Destination city")] string city,
[Description("Optional number of travel days")] int? days = nul
... [View full README on GitHub](https://github.com/azurecorner/remote-MCP-servers-using-dotnet-sdk-prompts#readme)