Syncfusion.WinUI.MCP 2.0.0

Prefix Reserved
{
  "servers": {
    "Syncfusion.WinUI.MCP": {
      "type": "stdio",
      "command": "dnx",
      "args": ["Syncfusion.WinUI.MCP@2.0.0", "--yes"]
    }
  }
}
                    
This package contains an MCP Server. The server can be used in VS Code by copying the generated JSON to your VS Code workspace's .vscode/mcp.json settings file.
dotnet tool install --global Syncfusion.WinUI.MCP --version 2.0.0
                    
This package contains a .NET tool you can call from the shell/command line.
dotnet new tool-manifest
                    
if you are setting up this repo
dotnet tool install --local Syncfusion.WinUI.MCP --version 2.0.0
                    
This package contains a .NET tool you can call from the shell/command line.
#tool dotnet:?package=Syncfusion.WinUI.MCP&version=2.0.0
                    
nuke :add-package Syncfusion.WinUI.MCP --version 2.0.0
                    

Syncfusion WinUI MCP Server

Overview

Transform your development experience with intelligent AI assistance powered by the Syncfusion WinUI MCP Server. Built on the Model Context Protocol, this tool bridges your development environment with Syncfusion's comprehensive WinUI component ecosystem, delivering contextual intelligence directly into your AI-powered workflow.

Key Features

  • Expert Component Knowledge - Deep understanding of Syncfusion WinUI components and their implementation patterns.
  • Unlimited Usage - No request limits, time restrictions, or query caps.
  • Privacy-Focused - Your data remains secure. The tools do not access files, store data, or use your prompts for training purposes.

Prerequisites

Before using the Syncfusion WinUI MCP Server, ensure you have:

Unlimited Access

Syncfusion® offers unlimited access to the WinUI MCP server with no restrictions on:

  • Number of requests and application generations
  • Component usage across all Syncfusion® WinUI libraries
  • Query complexity and length
  • Usage duration and session time

This ensures you can fully leverage AI-powered development without limitations.

Installation and Setup

Configure your MCP client with the following core settings. The configuration depends on your installed .NET SDK version — choose the option below that matches your environment.

Generic MCP Server Settings

For .NET 10 (using dnx)

The dnx tool downloads and runs the Syncfusion WinUI MCP package on demand — no local install required.

  • Type: stdio (standard input/output transport)
  • Command: dnx
  • Arguments: ["Syncfusion.WinUI.MCP", "--yes"]
  • Server name: sf-winui-mcp
  • NuGet package: Syncfusion.WinUI.MCP
{
  "servers": {
    "sf-winui-mcp": {
      "type": "stdio",
      "command": "dnx",
      "args": ["Syncfusion.WinUI.MCP", "--yes"],
      "env": {
        "Syncfusion_API_Key_Path": "YOUR_API_KEY_FILE_PATH"
        // or
        // "Syncfusion_API_Key": "YOUR_API_KEY"
      }
    }
  }
}
For .NET 8 / .NET 9 (local tool)

Users can install the Syncfusion WinUI MCP server as a local tool without global installation. For guidance on installing and managing local .NET tools, refer here.

Install the Syncfusion WinUI MCP tool locally:

dotnet tool install Syncfusion.WinUI.MCP

Then use these settings in your MCP client:

  • Type: stdio (standard input/output transport)
  • Command: dotnet
  • Arguments: ["tool", "run", "syncfusion-winui-mcp"]
  • Server name: sf-winui-mcp
  • NuGet package: Syncfusion.WinUI.MCP (restored automatically by the local manifest)
{
  "servers": {
    "sf-winui-mcp": {
      "type": "stdio",
      "command": "dotnet",
      "args": ["tool", "run", "syncfusion-winui-mcp"],
      "env": {
        "Syncfusion_API_Key_Path": "YOUR_API_KEY_FILE_PATH"
        // or
        // "Syncfusion_API_Key": "YOUR_API_KEY"
      }
    }
  }
}

API Key Configuration

Log in to your Syncfusion account and generate an API key from the API Key page. You have two secure options for providing your API key:

Store your API key in a separate file and reference its path in the Syncfusion_API_Key_Path environment parameter. This approach is more secure as it doesn't expose the key directly in configuration files.

Supported file formats: .txt or .key file

"env": {
  "Syncfusion_API_Key_Path": "YOUR_API_KEY_FILE_PATH" // "D:\\syncfusion-key.txt" (or) "D:\\syncfusion-key.key"
}
Option 2: Direct API Key

Provide your API key directly in the configuration:

"env": {
  "Syncfusion_API_Key": "YOUR_API_KEY"
}

Below are setup instructions for popular MCP clients:

Syncfusion® Code Studio

  • To configure an MCP server for a specific workspace, create a .codestudio/mcp.json file in your workspace folder.
{
  "servers": {
    "sf-winui-mcp": {
      "type": "stdio",
      "command": "dnx",
      "args": ["Syncfusion.WinUI.MCP", "--yes"],
      "env": {
        "Syncfusion_API_Key_Path": "YOUR_API_KEY_FILE_PATH"
        // or
        // "Syncfusion_API_Key": "YOUR_API_KEY"
      }
    }
  }
}

VS Code

  • To configure an MCP server for a specific workspace, create a .vscode/mcp.json file in your workspace folder.
{
  "servers": {
    "sf-winui-mcp": {
      "type": "stdio",
      "command": "dnx",
      "args": ["Syncfusion.WinUI.MCP", "--yes"],
      "env": {
        "Syncfusion_API_Key_Path": "YOUR_API_KEY_FILE_PATH"
        // or
        // "Syncfusion_API_Key": "YOUR_API_KEY"
      }
    }
  }
}
  • After updating mcp.json, you'll notice a "Start" option at the top of the config to launch the server. Check for a confirmation message like Syncfusion WinUI MCP server is running... in the output.
  • For additional guidance, refer to the VS Code documentation.

Cursor

To configure an MCP server for a specific workspace, you can create a .cursor/mcp.json file in your workspace folder.

{
  "mcpServers": {
    "sf-winui-mcp": {
      "command": "dnx",
      "args": ["Syncfusion.WinUI.MCP", "--yes"],
      "env": {
        "Syncfusion_API_Key_Path": "YOUR_API_KEY_FILE_PATH"
        // or
        // "Syncfusion_API_Key": "YOUR_API_KEY"
      }
    }
  }
}

For more details, refer to the Cursor documentation.

JetBrains IDEs

  1. Navigate to Settings → Tools → AI Assistant → Model Context Protocol (MCP)
  2. Click + Add to create a new MCP server configuration
  3. In the New MCP Server dialog, switch to As JSON and add:
{
  "mcpServers": {
    "sf-winui-mcp": {
      "command": "dnx",
      "args": ["Syncfusion.WinUI.MCP", "--yes"],
      "env": {
        "Syncfusion_API_Key_Path": "YOUR_API_KEY_FILE_PATH"
        // or
        // "Syncfusion_API_Key": "YOUR_API_KEY"
      }
    }
  }
}
  1. Click OK and Apply

See JetBrains documentation for further assistance.

Note: For other MCP clients like Windsurf, refer to their official documentation for MCP server configuration. The core configuration remains the same across all clients.

Usage

The Syncfusion WinUI MCP Server provides the search_docs tool to search Syncfusion WinUI documentation. Use it with a query parameter to find relevant information. For example, call search_docs with the query "DataGrid sorting" to get documentation on sorting functionality.

Example Prompt

#search_docs Create a Syncfusion WinUI Grid with paging, sorting, and filtering enabled.

Best Practices

For optimal results, use advanced AI models such as the latest-generation Claude, GPT, or Gemini models. These models better understand complex component relationships and generate more accurate WinUI code.

Always review AI-generated code before using in production.

Privacy & Security

The Syncfusion WinUI MCP Server is designed with privacy considerations:

  • The server does not access project files or workspace contents directly.
  • User prompts are not stored or used for other purposes.
  • Prompts are not used to train Syncfusion models.
  • The assistant provides context; the final output is produced by the selected AI model.

The MCP server acts purely as a knowledge bridge, connecting your AI model with Syncfusion-specific expertise while respecting your privacy and maintaining security.

Support

Product support is available through the following media:

License

This is a commercial product and requires a paid license for possession or use. Syncfusion® licensed software, including this component, is subject to the terms and conditions of Syncfusion's EULA. To acquire a license, you can purchase here or start a free 30-day trial here.

A free community license is also available for companies and individuals whose organizations have less than $1 million USD in annual gross revenue and five or fewer developers.

© Copyright 2026 Syncfusion® Inc. All Rights Reserved. The Syncfusion® Essential Studio® license and copyright applies to this distribution.

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 is compatible.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

Version Downloads Last Updated
2.0.0 105 9/7/2026
1.0.0 132 8/3/2026