Dotnet Template Mcp

io.github.YuliiaKovalovaPublished by GitHub account YuliiaKovalovav2.0.0Updated Oct 24, 2026

MCP server for dotnet new: discover, inspect, preview and create .NET projects from templates.

VerifiedSTDIODesktop onlyFiles & StorageDeveloper Tools

Overview

AI-generated overview

An MCP server for dotnet new that lets an assistant search, inspect, preview and scaffold .NET projects and templates from natural language.

What you can do
  • Search and list templates locally and on NuGet.org, and inspect their parameters and constraints
  • Create projects from a described intent, preview generated files without writing, and compose several templates in one workflow
  • Install, uninstall and inventory template packages, resolving missing ones from NuGet
  • Validate and compare templates, and generate a reusable template from an existing project
  • Analyze solutions and scan for outdated NuGet versions, reporting or applying upgrades
When to use it
Useful when you want an assistant to scaffold .NET projects, pick the right template and parameters, or check a custom template before publishing, without memorizing dotnet new flags. Also handy for auditing solution structure and package versions.
Requirements
Runs locally over stdio as a .NET tool (global install, .NET 8+) or zero-install via dnx (.NET 10+); the .NET SDK and network access to NuGet are needed. An optional HTTP mode requires a shared token in MCP_TEMPLATE_HTTP_TOKEN or explicit anonymous opt-in.
Before you install
Tools write files and install NuGet packages, so the server itself notes an open HTTP endpoint would be a remote code execution surface; keep the token set and avoid exposing one instance to untrusting users, since it is not multi-tenant. Project creation and package upgrades modify files on disk, and template search contacts NuGet.org.

Installation

In SourceWeft

  1. Open Dotnet Template Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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.

[DotnetTemplateMCP MCP server]

Instead of this:

bash
dotnet new list --language C#dotnet new webapi --helpdotnet new webapi --auth Individual --use-controllers --name MyApi --output ./MyApi

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:

Agent calls: template_validate("./my-template")
← Returns:{  "valid": false,  "summary": "2 error(s), 1 warning(s), 3 suggestion(s)",  "errors": [    "Missing required field 'shortName'.",    "Parameter 'Framework': default value 'net7.0' is not in the choices list."  ],  "warnings": [    "Missing 'sourceName'. Without it, the generated project name won't be customizable via --name."  ],  "suggestions": [    "Consider adding a 'description' field to help users understand what this template creates.",    "Consider adding 'language' tag (e.g., 'C#') for better discoverability.",    "Consider adding 'type' tag (e.g., 'project', 'item') for filtering."  ]}

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:

Official toolWhat it gives you
Microsoft.TemplateEngine.Authoring.CLIdotnet template-authoring validate — the reference validator
Microsoft.TemplateEngine.Authoring.TasksValidation at build time, as an MSBuild task
Microsoft.TemplateEngine.Authoring.TemplateVerifierSnapshot testing of template output

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

ToolWhat it does
template_searchSearch locally and on NuGet.org — one call, ranked results
template_listList what's installed, filter by language/type/classification
template_inspectParameters, constraints, post-actions — all in one shot
template_instantiateCreate a project. Not installed? Auto-resolves from NuGet. Elicits missing params interactively
template_dry_runPreview files without touching disk
template_installInstall a package (idempotent — skips if already there)
template_uninstallRemove a template package
templates_installedInventory of everything installed
template_from_intent"web API with auth" → webapi + auth=Individual — no LLM needed
template_create_from_existingAnalyze a .csproj → generate a reusable template matching repo conventions
template_composeExecute a sequence of templates (project + items) in one workflow
template_suggest_parametersSuggest parameter values with rationale based on cross-parameter relationships
template_validateValidate a local template directory for authoring issues before publishing
template_compareCompare 2+ templates side by side — parameters, features, frameworks
solution_analyzeAnalyze a solution/workspace — project structure, frameworks, CPM status
packages_upgradeScan a project/solution/folder for outdated NuGet versions and report or apply upgrades (CPM-aware)

📖 Full tool reference →

Hosted deployment

A hosted deployment is available on Fronteir AI.

Quick Start

Global tool (.NET 8+)

bash
dotnet tool install --global DotnetTemplateMCP --version 2.0.0

Zero-install with dnx (.NET 10+)

bash
dnx -y DotnetTemplateMCP --version 2.0.0

VS Code / GitHub Copilot

Add to mcp.json:

json
{  "servers": {    "dotnet-templates": {      "type": "stdio",      "command": "dnx",      "args": ["-y", "DotnetTemplateMCP", "--version", "2.0.0"]    }  }}

📖 Claude Desktop, Cursor, and more →

Transport Modes

Stdio (default)

Standard I/O transport for local CLI and tool usage:

bash
template-engine-mcp                     # stdio is the defaulttemplate-engine-mcp --transport stdio   # explicit

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:

bash
# RecommendedMCP_TEMPLATE_HTTP_TOKEN=<shared-secret> template-engine-mcp --transport http
# Only for a trusted, isolated networkMCP_TEMPLATE_HTTP_ALLOW_ANONYMOUS=true template-engine-mcp --transport http

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. TemplateEngineService is a process-wide singleton with virtualizeSettings: 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.

bash
template-engine-mcp --transport http# or via environment variable:MCP_TEMPLATE_TRANSPORT=http template-engine-mcp

The HTTP server exposes:

  • /mcp — MCP streamable HTTP endpoint (bearer token required)
  • /health — Health check endpoint (anonymous)

Configure the listen URL:

bash
MCP_TEMPLATE_HTTP_URL=http://0.0.0.0:8080 template-engine-mcp --transport http

Connect your MCP client:

json
{  "servers": {    "dotnet-templates": {      "type": "http",      "url": "http://localhost:5005/mcp"    }  }}

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:

Template ParameterElicitation Field
stringText input
bool / booleanCheckbox
int / numberNumber input
Choice parameterSingle-select dropdown

Disable with MCP_TEMPLATE_ELICITATION=false.

How it works

You: "I need a web API with authentication, controllers, and Docker support"
→ template_from_intent extracts keywords: web api, authentication, controllers, docker→ Matches: webapi (confidence: 0.85)→ Resolves: auth=Individual, UseControllers=true, EnableDocker=true→ template_instantiate creates the project

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:

  1. Detects Directory.Packages.props by walking up the directory tree
  2. Strips Version attributes from generated .csproj PackageReferences
  3. Adds missing <PackageVersion> entries to Directory.Packages.props
  4. Resolves latest stable NuGet versions — no more stale hardcoded versions from templates
Before (what dotnet new generates):  <PackageReference Include="Serilog" Version="3.1.0" />    ← stale, breaks CPM
After (what template_instantiate produces):  .csproj:                    <PackageReference Include="Serilog" />  Directory.Packages.props:   <PackageVersion Include="Serilog" Version="4.2.0" />

Works for standalone projects too — versions are updated directly in the .csproj.

Multi-Template Composition

Chain multiple templates in one call with template_compose:

json
[  {"templateName": "webapi", "name": "MyApi", "parametersJson": "{\"auth\": \"Individual\"}"},  {"templateName": "gitignore", "target": "."}]

📖 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:

ProfileToolsWhen to use
full (default)All 15 toolsFull control — advanced workflows, composition, custom templates
lite5 core toolsSimpler agents that just need to find and create projects

Lite profile tools: template_from_intent, template_instantiate, template_inspect, template_search, template_dry_run

json
{  "servers": {    "dotnet-template-mcp": {      "command": "dotnet-template-mcp",      "env": {        "MCP_TEMPLATE_TOOL_PROFILE": "lite"      }    }  }}

Non-lite tools will return a helpful message explaining they're disabled and how to enable them.

Documentation

DocWhat's in it
ConfigurationVS Code, Claude Desktop, Cursor setup + troubleshooting
Tool ReferenceEvery tool's parameters, types, and examples
ArchitectureTemplate cache, smart behaviors, telemetry, project structure
MCP vs SkillsWhy MCP over Copilot Skills — benefits and downsides
Plain LLM vs MCPSide-by-side: what a plain LLM does vs. the MCP tool (4 scenarios)
Skills EquivalentWhat it'd take to cover this with Skills instead

Building & Testing

bash
dotnet builddotnet test    # 185+ tests — unit, integration, and E2E

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.

bash
# Setupdotnet restoredotnet build
# Run testsdotnet test
# Pack locallydotnet pack src/DotnetTemplateMcp -o nupkg/

Changelog

See CHANGELOG.md for release history.

License

MIT

Source: README.md at commit a8a4980

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts