Radzen.Mcp 0.0.3 cannot be restored or used as tool/library (NU1202, NU1204, NU1212 with .NET 9 and .NET 8 console app)

Radzen.Blazor Components
1

Hi Radzen team,

I am trying to use the Radzen.Mcp NuGet package as described in your AI/MCP documentation, but I am unable to restore or run it in any realistic setup. I see multiple NuGet errors (NU1202, NU1204, NU1212) both in my main .NET 9 solution and even in a fresh console app created only to host the MCP server.

Environment

  • OS: Windows 10/11 (please replace with your actual OS)

  • Visual Studio 2022 (latest) and .NET SDKs installed

  • .NET 9 SDK and .NET 8 SDK installed

  • NuGet package: Radzen.Mcp 0.0.3

What I want to do

I want to use Radzen MCP as an MCP server for Radzen.Blazor in Visual Studio / VS Code. The plan was:

  1. Create a small host console project (preferably net8.0) to run the MCP server.

  2. Add Radzen.Mcp as a package to that project.

  3. Configure Copilot/MCP to start that project via dotnet run --project … as a “Command (stdio)” server.

Steps to reproduce

  1. Create a fresh console project:
bash

dotnet new console -n RadzenMcpHost -f net8.0 cd RadzenMcpHost dotnet add package Radzen.Mcp -Version 0.0.3

  1. Restore packages (this happens automatically after dotnet add package).

Actual result

The restore fails with:

  • NU1212: Invalid project-package combination for Radzen.Mcp 0.0.3. DotnetToolReference project style can only contain references of the DotnetTool type

  • Package 'Radzen.Mcp' is incompatible with 'all' frameworks in project '...\RadzenMcpHost.csproj'.

When I try to reference Radzen.Mcp from my existing .NET 9 project (where I actually use Radzen.Blazor), I see:

  • NU1202: Package Radzen.Mcp 0.0.3 is not compatible with net9.0 (.NETCoreApp,Version=v9.0). Package Radzen.Mcp 0.0.3 supports: net8.0 / any

  • NU1204: Invalid tools package Radzen.Mcp 0.0.3. Tools packages cannot contain more than one PackageType.

  • NU1212: Invalid project-package combination for Radzen.Mcp 0.0.3. DotnetToolReference project style can only contain references of the DotnetTool type.

  • Package 'Radzen.Mcp 0.0.3' has multiple package types, which is not supported.

So:

  • It cannot be used as a normal <PackageReference> in a net9.0 project.

  • It also cannot be added as a reference to a plain net8.0 console app.

  • It also does not behave as a clean dotnet tool that I can install with dotnet tool install -g Radzen.Mcp.

Expected behavior

  • Either:

    • Radzen.Mcp should be a standard library / server package targeting net8.0 (or net8.0 + net9.0) that I can reference from a console host project, and then start via dotnet run as an MCP server,

    or

    • Radzen.Mcp should be a proper dotnet tool with a single DotnetTool package type and a documented command (e.g. dotnet radzen-mcp) that I can install with dotnet tool install -g Radzen.Mcp and use directly as the MCP server command.

Right now the package metadata seems to declare multiple package types, which causes NuGet to reject it as both a normal package and a tool, making it impossible to use in the way your MCP documentation suggests.

Request

  • Could you please:

    • Confirm the intended usage pattern for Radzen.Mcp (library vs dotnet tool vs something else)?

    • Fix the NuGet package so that it has a single, correct package type, and is restorable in at least a simple net8.0 console project?

    • Provide a short “Getting Started with Radzen.Mcp” snippet that shows:

      • The recommended dotnet new project template and TargetFramework,

      • The exact dotnet add package or dotnet tool install command,

      • The command line to start the MCP server (what should I put as the command in VS / VS Code MCP configuration)?

I am happy to test a new version (e.g. 0.0.4) or a prerelease and report back if it resolves NU1202/NU1204/NU1212 and allows me to run Radzen.Mcp as an MCP server alongside my .NET 9 Radzen.Blazor project.

Thank you!

2

Did you check the readme?

You need to run dotnet tool install --global Radzen.Mcp which works as intended.