1. Conduid
  2. Commerce
  3. AIGuiders dotnet MCP templates
MCP server · Commerce

AIGuiders dotnet MCP templates

· github.com/KarataevDmitry/dotnet-mcp-templates

Templates for building Model Context Protocol (MCP) servers on .NET (tool catalog + handlers + publish/deploy + manifest/docs automation).

Unclaimed commerce
InstallView source
34Low

Scored 5 months ago · breakdown

About AIGuiders dotnet MCP templates

AIGuiders dotnet MCP templates is an MCP server in the Commerce category: templates for building Model Context Protocol (MCP) servers on .NET (tool catalog + handlers + publish/deploy + manifest/docs automation).

Install

From source
git clone https://github.com/KarataevDmitry/dotnet-mcp-templates

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about AIGuiders dotnet MCP templates

Powered by Claude · Grounded in docs

I know everything about AIGuiders dotnet MCP templates. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.

5 checks have not been run yet.

README

AIGuiders.DotnetMcp.Templates

Template pack for dotnet new to bootstrap MCP servers on .NET.

Release notes: see docs/release.md.

Why the template looks “heavy”

The mcp template is intentionally aligned with our MCP repos (for example hybrid-codebase-index, agent-notes-mcp, git-mcp):

  • ToolCatalog is the source of truth: tool names + descriptions + input schemas live in code.
  • mcp-tools.manifest.json is generated from ToolCatalog.Build() using tools/ExportMcpManifest.
    • This keeps the manifest and the docs consistent with the runtime contract.
  • docs/MCP-TOOLS.md is generated from the same catalog, so humans see the same descriptions the host sees.
  • Tests validate consistency: *.Tests compares manifest tool names/descriptions against ToolCatalog.

Why tools/McpToolManifest exists (instead of “just DTOs”)

In the mcp template we include a tiny library tools/McpToolManifest that defines:

  • the canonical JSON shape (schema_version, mcp_id, title, tools[])
  • a reader/validator (McpToolManifestReader)
  • a name comparer (ToolCatalogNameComparer)

This gives a stable, reusable contract in every generated MCP repo and matches how the rest of our MCP repos are automated.

Why there are two readmes

  • README-NUGET.md is the public package readme shown on nuget.org (install + usage only).
  • README.md is the repo readme (may include maintainer notes and links to docs/).

Install

dotnet new install AIGuiders.DotnetMcp.Templates

Create a new MCP server (full pattern)

dotnet new mcp -n MyCompany.MyMcp --mcp-id my-mcp

Create a minimal MCP server

dotnet new mcp-min -n MyCompany.MyMcp --mcp-id my-mcp

Uninstall

dotnet new uninstall AIGuiders.DotnetMcp.Templates

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About AIGuiders dotnet MCP templates

How do I install AIGuiders dotnet MCP templates?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is AIGuiders dotnet MCP templates safe to use with an AI agent?

Its trust score is 34 out of 100 (low). It passes 1 of the 1 static security checks run so far. It has no ConduID identity yet, so agent calls to it are not receipted.

Is AIGuiders dotnet MCP templates still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.