Main
Start with the Docker images when you only need a working MCP server quickly; then open the sample directory to see the implementation patterns in .NET.
Treat the repo as a reference library: pick one sample (markdown-to-html, outlook-email, todo-list) and mirror its transport + tool shape in your own server.
Use the repo’s descriptions to decide integration scope: some samples are pure transformations (markdown→HTML) while others touch external services (Outlook).
Source-backed notes
- README frames MCP as a standardized connection layer (“USB‑C port for AI applications”).
- The sample table includes install links that embed Docker args for images like
ghcr.io/microsoft/mcp-dotnet-samples/markdown-to-html:latestand.../todo-list:latest. - README points to MCP official docs and the MCP GitHub repository for deeper protocol details.
FAQ
- Do I need .NET to try it?: Not necessarily — README’s install links include Docker-run servers you can start without building locally.
- Which sample should I start with?: Pick markdown-to-html for a self-contained transformation, then move to service-backed ones like Outlook Email.
- Is this only for Visual Studio?: No — README provides install links for VS Code and mentions using the samples in .NET apps broadly.