Template FAQs

Question 1

What kind of architectural pattern does this template follow?

Accepted Answer

The template strictly adheres to a clean architecture pattern, emphasizing separation of concerns through distinct layers such as Tools, Services, Interfaces, and Models, all managed with robust Dependency Injection.

Question 2

What are the core features of this MCP Server template?

Accepted Answer

Key features include MCP server implementation with ModelContextProtocol.AspNetCore, dual transport support for HTTP and Stdio, structured logging using Serilog, clean architecture with Dependency Injection, and sample MCP tools demonstrating the pattern.

Question 3

Can I extend this template to create my own custom MCP tools?

Accepted Answer

Yes, extending the template is straightforward. You can create new MCP tools by defining tool classes in the `Tools/` folder with `[McpServerTool]` attributes and registering them in `Program.cs`, allowing full customization.

Question 4

What is the Template MCP Server designed for?

Accepted Answer

The Template MCP Server provides a foundational C# API template for developers to quickly build Model Context Protocol (MCP) servers with a clean architecture, offering a solid starting point for robust backend services.

Question 5

How does the Template MCP Server integrate with VS Code and GitHub Copilot?

Accepted Answer

It's designed for seamless integration using Stdio transport, allowing VS Code and Copilot to communicate with your MCP server via a `.vscode/mcp.json` configuration, streamlining your development workflow.

Template

概要

主な機能

ユースケース