Microsoft.FluentUI.AspNetCore.McpServer 5.0.0-rc.1-26049.2

Fluent UI Blazor MCP Server

A Model Context Protocol (MCP) server that provides documentation for the Fluent UI Blazor component library.

Overview

This MCP server enables AI assistants to access comprehensive documentation about Fluent UI Blazor components, including:

• Component listing - Browse all 142+ available components with descriptions
• Component details - Get complete documentation including parameters, events, and methods
• Search - Find components by name or description
• Enum information - Explore enum types and their values

Installation

Option 1: Install as dotnet tool based on NuGet.org (Recommended)

Install the MCP server as a global .NET tool:

dotnet tool install -g Microsoft.FluentUI.AspNetCore.McpServer

After installation, configure your MCP client to use the tool:

For Visual Studio Code (.vscode/mcp.json):

{
    "servers": {
        "fluent-ui-blazor": {
            "command": "fluentui-mcp"
        }
    }
}

For Visual Studio 2026 (.mcp.json at solution root):

{
    "servers": {
        "fluent-ui-blazor": {
            "command": "fluentui-mcp"
        }
    }
}

Option 2: Use dnx script tool based on NuGet.org

Use dnx to add the MCP server directly to your MCP client:

dnx Microsoft.FluentUI.AspNetCore.McpServer

Once added, configure your MCP client to use the tool:

For Visual Studio Code (.vscode/mcp.json):

{
    "servers": {
        "fluent-ui-blazor": {
            "command": "dnx",
            "args": [
                "Microsoft.FluentUI.AspNetCore.McpServer"
            ]
        }
    }
}

For Visual Studio 2026 (.mcp.json):

{
    "servers": {
        "fluent-ui-blazor": {
            "command": "dnx",
            "args": [
                "Microsoft.FluentUI.AspNetCore.McpServer"
            ]
        }
    }
}

This command will download from NuGet.org the latest version. You can specify the version number using the following command:

dnx Microsoft.FluentUI.AspNetCore.McpServer@5.0.1

Option 3: Build from Source

Prerequisites:

• .NET 9.0 SDK
• Build the FluentUI Blazor solution first

cd src/Tools/McpServer
dotnet build

Configure in your MCP client:

For Visual Studio Code (.vscode/mcp.json):

{
    "servers": {
        "fluent-ui-blazor": {
            "type": "stdio",
            "command": "dotnet",
            "args": [
                "run",
                "--project",
                "src/Tools/McpServer/Microsoft.FluentUI.AspNetCore.McpServer.csproj"
            ],
            "env": {
                "DOTNET_ENVIRONMENT": "Development"
            }
        }
    }
}

For Visual Studio 2026 (.mcp.json at solution root):

{
    "servers": {
        "fluent-ui-blazor": {
            "command": "dotnet",
            "args": [
                "run",
                "--project",
                "src/Tools/McpServer/Microsoft.FluentUI.AspNetCore.McpServer.csproj"
            ],
            "env": {
                "DOTNET_ENVIRONMENT": "Development"
            }
        }
    }
}

Architecture

The MCP server uses pre-generated JSON documentation to provide fast, dependency-free access to component information:

┌─────────────────────────────────────────────────┐
│ FluentUI.Demo.DocApiGen (Build Time)            │
│ ├── Uses LoxSmoke.DocXml                        │
│ └── Generates FluentUIComponentsDocumentation.json
└─────────────────────────────────────────────────┘
                    │
                    ▼ (PreBuild / EmbeddedResource)
┌─────────────────────────────────────────────────┐
│ McpServer (Runtime)                             │
│ └── Reads JSON from embedded resource           │
└─────────────────────────────────────────────────┘

This architecture provides:

• Faster startup - No XML parsing at runtime
• Consistent documentation - Generated once at build time

Available Features

Tools (Model-controlled)

Tools are invoked automatically by the LLM for dynamic queries.

Resources (User-controlled)

Resources provide static documentation that users can attach to conversations.

Usage Examples

# List all button components
ListComponents(category: "Button")

# Get details about FluentDataGrid
GetComponentDetails(componentName: "FluentDataGrid")

# Search for input components
SearchComponents(searchTerm: "input")

# Get enum values for Appearance
GetEnumValues(enumName: "Appearance")

List all documentation topics

ListDocumentation()

Get the installation guide

GetDocumentationTopic(topicName: "Installation")

Search for migration-related documentation

SearchDocumentation(searchTerm: "migrate")

Get the complete migration guide to v5

GetMigrationGuide()

## Debugging


### Visual Studio Code

1. Configure the MCP server in `.vscode/mcp.json`:

```json
{
    "servers": {
        "fluent-ui-blazor": {
            "type": "stdio",
            "command": "dotnet",
            "args": [
                "run",
                "--project",
                "src/Tools/McpServer/Microsoft.FluentUI.AspNetCore.McpServer.csproj"
            ],
            "env": {
                "DOTNET_ENVIRONMENT": "Development"
            }
        }
    }
}

2. Set breakpoints in your code
3. Use Debug > Attach to Process and select the dotnet process running the MCP server

MCP Inspector

1. Launch the MCP Inspector with the server:

npx @modelcontextprotocol/inspector dotnet run --project src/Tools/McpServer/Microsoft.FluentUI.AspNetCore.McpServer.csproj

2. Open VS Code and use the "Attach MCP" task from the Run and Debug panel to attach the debugger to the running process

The MCP Inspector provides a web-based interface to:

• Test MCP tools interactively
• View requests/responses in real-time
• Inspect exposed resources
• Debug protocol interactions

Development

Regenerating Documentation

The MCP documentation JSON is automatically regenerated during build. To force regeneration:

dotnet build -p:ForceGenerateMcpDocs=true

Adding New Tools

1. Add a new class in the Tools/ folder with [McpServerToolType] attribute
2. Add methods with [McpServerTool] and [Description] attributes
3. Use [Description] on parameters for better AI understanding

Adding New Resources

1. Add a new class in the Resources/ folder with [McpServerResourceType] attribute
2. Add methods with [McpServerResource] attribute specifying UriTemplate, Name, and MimeType
3. Register in ServiceCollectionExtensions.cs with .WithResources<YourResourceClass>()

Adding New Prompts

1. Add a new class in the Prompts/ folder with [McpServerPromptType] attribute
2. Add methods with [McpServerPrompt] and [Description] attributes
3. Return ChatMessage with the prompt content
4. Register in ServiceCollectionExtensions.cs with .WithPrompts<YourPromptClass>()

Security

The Fluent UI Blazor MCP Server is designed with security as a priority:

Security Features

• ✅ Read-only operations - No file system modifications
• ✅ No network access - Runs entirely offline
• ✅ Pre-generated documentation - No runtime code execution
• ✅ Sandboxed execution - Runs as a child process of your IDE
• ✅ No sensitive data - Only serves public API documentation
• ✅ Open source - All code is publicly auditable

What the MCP Server CANNOT Do

• ❌ Execute arbitrary code
• ❌ Access your source code or files
• ❌ Make network requests
• ❌ Modify system state
• ❌ Access environment variables or credentials
• ❌ Launch other processes

For SecOps Teams

For comprehensive security information including:

• Architecture and isolation details
• Threat model analysis
• Compliance considerations
• Audit procedures
• Security best practices

See the Security & Compliance Documentation in the demo site.

Reporting Security Issues

To report security vulnerabilities:

• Microsoft Security Response Center: secure@microsoft.com
• GitHub Security Advisories: https://github.com/microsoft/fluentui-blazor/security

Troubleshooting

Documentation Not Loading

If component descriptions are missing:

1. Force regeneration with dotnet build -p:ForceGenerateMcpDocs=true
2. Ensure the FluentUI Components project builds successfully

Server Not Responding

Check that:

1. The solution builds successfully
2. .NET 9.0 SDK is installed
3. The path in your MCP configuration is correct

License

This project is licensed under the MIT License - see the LICENSE file for details.