MCP Serverlink

Radzen Blazor Studio includes a built-in Model Context Protocol (MCP) server. Any MCP-capable AI coding agent can connect to it and work on the application you have open in Radzen Blazor Studio — scaffolding pages and applications, editing components, and managing themes and data sources for you.

Using an AI agent inside Radzen Blazor Studio? You're already set up. When you chat with an agent through the AI panel (which uses the Agent Client Protocol), Radzen Blazor Studio configures this MCP server for the agent automatically — there is nothing to do. Follow the steps on this page only to connect an agent you run outside Radzen Blazor Studio, such as a terminal CLI or another editor.

This is different from Radzen Blazor MCP, the hosted server that gives agents Radzen Blazor component documentation, examples, and API references. This page is about the local server bundled with Radzen Blazor Studio that builds and edits your project. You can use both at the same time.

What the agent can dolink

Once connected, the agent can ask Radzen Blazor Studio to:

• Scaffold applications from templates (web, CRM, healthcare, and more).
• Add pages — CRUD, master/detail, data grid with a form, inline-edit grid, and pivot grid — and layouts (empty, menu, sidebar, login).
• Edit components — insert, move, and delete components, set their properties, and insert markup or ready-made UI blocks.
• Manage themes — switch the active theme and set or reset theme variables.
• Set up data sources — infer a data model from an existing database, import an OpenAPI (Swagger) or OData service, or add a REST service.
• Add features — authentication (ASP.NET Core Identity, Azure AD, Windows) and localization.
• Explore the solution — list projects, entities, and database connections.

Some capabilities (such as premium UI blocks and theme customization) require a license.

Before you startlink

• Open your application in Radzen Blazor Studio and keep it running. The agent connects to the project you currently have open.
• Install the .NET 10 runtime and make sure dotnet is on your PATH. Radzen Blazor Studio already needs it, so this is usually the case. If not, get it from the .NET download page.

How it workslink

Your agent launches the bundled server in MCP mode, and it automatically connects to the application you have open in Radzen Blazor Studio — there is no port, key, or other configuration to set up. The commands and configuration files below do exactly that. When you close Radzen Blazor Studio the connection simply goes away.

The server is Radzen.Server.dll, which ships inside Radzen Blazor Studio. Every example below is already filled in with its location — just pick the tab for your operating system:

• Windows: c:\Program Files\Radzen Blazor Studio\resources\Radzen.Server\Radzen.Server.dll
• macOS: /Applications/Radzen Blazor Studio.app/Contents/Resources/Radzen.Server/Radzen.Server.dll

Configure your agentlink

Pick your tool below. Every example registers the server under the name radzen-blazor-studio.

Cursorlink

Create or edit .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "radzen-blazor-studio": {
      "command": "dotnet",
      "args": ["c:\\Program Files\\Radzen Blazor Studio\\resources\\Radzen.Server\\Radzen.Server.dll", "--mcp"]
    }
  }
}

Tips:

• Use Agent mode (not Ask mode) so Cursor can call MCP tools. Switch modes in the chat panel dropdown.
• .cursor/mcp.json is project-level; ~/.cursor/mcp.json applies to every project.

Verify: Open Cursor Settings > MCP. You should see radzen-blazor-studio with a green status indicator.

Claude Codelink

Run this command — no file editing needed:

claude mcp add radzen-blazor-studio -- dotnet "c:\Program Files\Radzen Blazor Studio\resources\Radzen.Server\Radzen.Server.dll" --mcp

Everything after -- is the command Claude Code runs, so the trailing --mcp is passed to the server.

Tips:

• To scope the server to one project, add a .mcp.json file in the project directory instead.
• If you added the server while Claude Code was running, type /mcp to refresh the server list.

Verify: Run claude mcp list. You should see radzen-blazor-studio.

GitHub Copilotlink

VS Code

Create or edit .vscode/mcp.json in your project root:

{
  "servers": {
    "radzen-blazor-studio": {
      "type": "stdio",
      "command": "dotnet",
      "args": ["c:\\Program Files\\Radzen Blazor Studio\\resources\\Radzen.Server\\Radzen.Server.dll", "--mcp"]
    }
  }
}

Tips:

• MCP support requires VS Code 1.99 or later.
• After saving, VS Code shows a Start button above the server entry in mcp.json. Click it to connect.
• Use Agent mode in the Copilot Chat panel for MCP tool access.

Verify: Click Start next to the server entry. The status should change to "Running".

Visual Studio

Create or edit .mcp.json in your solution directory:

{
  "servers": {
    "radzen-blazor-studio": {
      "type": "stdio",
      "command": "dotnet",
      "args": ["c:\\Program Files\\Radzen Blazor Studio\\resources\\Radzen.Server\\Radzen.Server.dll", "--mcp"]
    }
  }
}

Tips:

• MCP support requires Visual Studio 2022 17.14 or later.
• Visual Studio scans for .mcp.json at the solution root on startup. If you added it while VS was open, close and reopen the solution.

Verify: Open the Copilot Chat panel and confirm the Radzen tools appear under the tools icon.

Gemini CLIlink

Run this command — no file editing needed:

gemini mcp add radzen-blazor-studio dotnet "c:\Program Files\Radzen Blazor Studio\resources\Radzen.Server\Radzen.Server.dll" --mcp

Verify: Run gemini mcp list. You should see radzen-blazor-studio connected.

OpenCodelink

Create or edit opencode.json in your project root:

{
  "mcp": {
    "radzen-blazor-studio": {
      "type": "local",
      "command": ["dotnet", "c:\\Program Files\\Radzen Blazor Studio\\resources\\Radzen.Server\\Radzen.Server.dll", "--mcp"],
      "enabled": true
    }
  }
}

Verify: Start OpenCode and confirm the server connects.

Codexlink

Create or edit ~/.codex/config.toml:

[mcp_servers.radzen-blazor-studio]
command = "dotnet"
args = ["c:\\Program Files\\Radzen Blazor Studio\\resources\\Radzen.Server\\Radzen.Server.dll", "--mcp"]

Verify: Start Codex and confirm the server is listed in the active connections.

Other MCP clientslink

Any MCP-compatible client can connect. Configure it with transport stdio, command dotnet, and the arguments Radzen.Server.dll (the full path for your operating system) followed by --mcp. Refer to your client's documentation for the exact configuration format.

Verify the connectionlink

1. Open your application in Radzen Blazor Studio.
2. Confirm your agent lists radzen-blazor-studio (for example, claude mcp list, or the MCP panel in Cursor or VS Code).
3. Ask the agent something like "list the projects in my solution". A successful answer means the agent reached Radzen Blazor Studio.

If the agent can't connect, make sure Radzen Blazor Studio is running with your project open, that dotnet is on your PATH, and that the path to Radzen.Server.dll is correct for your operating system.

See alsolink

• Radzen Blazor MCP — the hosted server with Radzen Blazor documentation, examples, and API references.
• AI Agents in Radzen Blazor Studio — chat with an AI agent inside Radzen Blazor Studio.