
Dotnet Template Mcp
io.github.YuliiaKovalova由 GitHub 账号 YuliiaKovalova 发布v2.0.0更新于 Oct 24, 2026
MCP server for dotnet new: discover, inspect, preview and create .NET projects from templates.
概览
面向 dotnet new 的 MCP 服务器,让助手用自然语言搜索、查看、预览并创建 .NET 项目和模板。
- 可以做什么
- 在本地和 NuGet.org 上搜索、列出模板,并查看其参数与约束
- 按意图创建项目、在不写盘的情况下预览生成文件,并在一次流程中组合多个模板
- 安装、卸载和清点模板包,缺失时自动从 NuGet 解析
- 校验和对比模板,并从现有项目生成可复用模板
- 分析解决方案结构,扫描过时的 NuGet 版本并报告或应用升级
- 适用场景
- 适合让助手搭建 .NET 项目、挑选合适的模板与参数,或在发布前检查自定义模板,而无需记住 dotnet new 的各种参数。也适合审查解决方案结构和包版本。
- 运行要求
- 以 .NET 工具形式通过 stdio 本地运行(全局安装需 .NET 8+,或用 dnx 免安装需 .NET 10+);需要 .NET SDK 和访问 NuGet 的网络。可选的 HTTP 模式需在 MCP_TEMPLATE_HTTP_TOKEN 中设置共享令牌,或显式允许匿名访问。
安装
在 SourceWeft 中
- 打开 控制台中的 Dotnet Template Mcp,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
DotnetTemplateMCP
An MCP server that lets AI agents work with dotnet new templates — search, inspect, preview, and create projects through natural conversation instead of memorizing CLI flags.
Instead of this:
Your AI agent just says: "I need a web API with authentication and controllers" — and the MCP server figures out the rest.
Template Validation for Authors
Building a custom dotnet new template? template_validate catches mistakes before you publish — no more guessing if your template.json is correct:
What it catches: missing required fields, invalid identity format, short name conflicts with CLI commands, parameter issues (missing defaults, empty choices, prefix collisions, type mismatches), broken computed symbols, constraint misconfiguration, and missing tags.
How this relates to the official tooling. Microsoft ships template authoring validation already, and you should know about it:
What template_validate adds is not the validation itself — it is the delivery: a single structured JSON payload, split into errors/warnings/suggestions with fix-oriented messages, returned in-band to an agent that is already editing the template. No install step, no output parsing, no second tool in the loop. If you are a human authoring templates in CI, prefer the official tools above; they are the reference implementation and cover cases this does not.
Tools
Hosted deployment
A hosted deployment is available on Fronteir AI.
Quick Start
Global tool (.NET 8+)
Zero-install with dnx (.NET 10+)
VS Code / GitHub Copilot
Add to mcp.json:
📖 Claude Desktop, Cursor, and more →
Transport Modes
Stdio (default)
Standard I/O transport for local CLI and tool usage:
HTTP (remote / team-shared)
Streamable HTTP transport for remote or CI/CD deployment.
Authentication is mandatory. Every tool in this server writes files and installs NuGet packages, so an open endpoint is a remote code execution surface. The server refuses to start the HTTP transport unless you either set a token or explicitly opt in to anonymous access:
Clients authenticate with Authorization: Bearer <shared-secret>. Requests to /mcp are rate limited per client (default 120/minute, MCP_TEMPLATE_HTTP_RATE_LIMIT=0 disables). /health stays anonymous for probes.
Not multi-tenant.
TemplateEngineServiceis a process-wide singleton withvirtualizeSettings: false, so the installed-template set is shared by every caller, and the workspace root is process-wide. Run one instance per trusted team or per tenant — do not expose a single instance to mutually untrusting users.
The HTTP server exposes:
/mcp— MCP streamable HTTP endpoint (bearer token required)/health— Health check endpoint (anonymous)
Configure the listen URL:
Connect your MCP client:
Interactive Elicitation
When a template has required parameters that weren't provided, the server asks the user interactively via MCP elicitation — instead of failing. Template parameter types are mapped to form fields:
Disable with MCP_TEMPLATE_ELICITATION=false.
How it works
The server also does smart defaults (AOT → latest framework, auth → HTTPS stays on), parameter validation before writing files, constraint checking (OS, SDK, workload), interactive elicitation of missing required parameters, and auto-resolves templates from NuGet if they're not installed.
CPM & Latest Package Versions
When creating a project inside a solution that uses Central Package Management, the server automatically:
- Detects
Directory.Packages.propsby walking up the directory tree - Strips
Versionattributes from generated.csprojPackageReferences - Adds missing
<PackageVersion>entries toDirectory.Packages.props - Resolves latest stable NuGet versions — no more stale hardcoded versions from templates
Works for standalone projects too — versions are updated directly in the .csproj.
Multi-Template Composition
Chain multiple templates in one call with template_compose:
📖 Architecture & smart behaviors →
Tool Profiles (Lite vs Full)
By default, all 15 tools are available. If your agent works better with fewer tools, set the MCP_TEMPLATE_TOOL_PROFILE environment variable:
Lite profile tools: template_from_intent, template_instantiate, template_inspect, template_search, template_dry_run
Non-lite tools will return a helpful message explaining they're disabled and how to enable them.
Documentation
Building & Testing
CI runs on push/PR via GitHub Actions (Ubuntu + Windows).
Contributing
Contributions are welcome! Please open an issue to discuss proposed changes before submitting a PR.
Changelog
See CHANGELOG.md for release history.
License
来源:README.md,提交 a8a4980
工具
0版本历史
1- v2.0.0最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分