GravionLabs/elysion / .agents/skills/dotnet-mcp-server-generator
dotnet-mcp-server-generator
VerifiedGenerate a complete MCP server project in C# with tools, prompts, stdio transport and stderr logging. Use when asked to create or scaffold an MCP server in .NET or C#.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.6 KB |
| templates/Program.cs | other | 545 B |
| templates/Prompts.cs | other | 1.3 KB |
| templates/Tools.cs | other | 695 B |
SKILL.md
View on GitHub---
name: dotnet-mcp-server-generator
description: 'Generate a complete MCP server project in C# with tools, prompts, stdio transport and stderr logging. Use when asked to create or scaffold an MCP server in .NET or C#.'
disable-model-invocation: true
metadata:
opencode/autoinvoke: 'false'
---
Generate a Model Context Protocol (MCP) server in C#: a console application using the stable `ModelContextProtocol` package (2.x) with `Microsoft.Extensions.Hosting`, stdio transport, tools and prompts. Paths to `templates/` are relative to this skill's directory.
## Steps
1. Ask: project name, tools to expose (names, descriptions, input schemas), prompts to include
2. Create the project:
```powershell
dotnet new console -n <ProjectName>
cd <ProjectName>
dotnet add package ModelContextProtocol
dotnet add package Microsoft.Extensions.Hosting
```
3. Copy `templates/Program.cs`, `templates/Tools.cs`, `templates/Prompts.cs` and adapt them to the requested tools and prompts
4. Add `appsettings.json` with a `Logging` section routing all logs to stderr
5. Build and verify: `dotnet build`
## Templates
- **`Program.cs`** — host setup with `AddMcpServer()`, stdio transport, console logging to stderr, tool and prompt registration
- **`Tools.cs`** — `[McpServerToolType]` class with two example tools (sync + async with `CancellationToken`)
- **`Prompts.cs`** — `[McpServerPromptType]` class with an example `PromptMessage` return (`TextContentBlock` content)
## Constraints
- All logs must go to stderr — never stdout (stdio transport uses stdout for the MCP protocol)
- Tool methods should be `async Task<string>` or `async Task<CallToolResult>`
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |