Syncfusion ASP.NET Core MCP Server

29 Jul 202614 minutes to read

Syncfusion^® MCP Server accelerate ASP.NET Core application development by providing deep knowledge directly in your AI-powered IDE. Model Context Protocol (MCP) integration enables quick access to documentation, API references, and code-generation features from within the development environment.

These tools speed up development and reinforce best practices for Syncfusion component integration.

Key Benefits

Expert Component Knowledge - Deep understanding of 145+ ASP.NET Core components and their implementation patterns.
Unlimited Usage - No request limits, time restrictions, or query caps.
Privacy-Focused - The tools operate based on the user’s query and do not store any content, data, or prompts.

Installation

Prerequisites

Before beginning, ensure the following prerequisites are met:

Microsoft .NET SDK 8.0 or later
A compatible MCP client (VS Code, Syncfusion^® Code Studio, Cursor, JetBrains, etc.)
An active Syncfusion^® API key
An ASP.NET Core application (existing or new); see Quick Start
An active Syncfusion^® license (any of the following):

Getting Your API Key

Generate the Syncfusion^® API key from the API Key page and store it in a .txt or .key file. The saved file will be referenced in the MCP configuration:

"env": {
  "Syncfusion_API_Key_Path": "D:\\syncfusion-key.txt"
}

Alternatively, the API key can also be set directly using "Syncfusion_API_Key": "YOUR_API_KEY" in the env configuration. Using a file path is recommended to keep the key out of source control.

Setting Up in MCP Clients

Create a configuration file in your project folder to install the server for your workspace. Replace YOUR_API_KEY_FILE_PATH with the path to your API key file. The tabs below show a working configuration for each supported MCP client.

For .NET 10 :

VS Code
Code Studio
Cursor
JetBrains
// Create a `.vscode/mcp.json` file in your workspace:

{
  "servers": {
    "sf-aspnetcore-mcp": {
      "type": "stdio",
      "command": "dnx",
      "args": ["Syncfusion.AspNetCore.MCP", "--yes"],
      "env": {
        "Syncfusion_API_Key_Path": "YOUR_API_KEY_FILE_PATH"
        // or
        // "Syncfusion_API_Key": "YOUR_API_KEY"
      }
    }
  }
}
// Create a `.codestudio/mcp.json` file in your workspace:

{
  "servers": {
    "sf-aspnetcore-mcp": {
      "type": "stdio",
      "command": "dnx",
      "args": ["Syncfusion.AspNetCore.MCP", "--yes"],
      "env": {
        "Syncfusion_API_Key_Path": "YOUR_API_KEY_FILE_PATH"
        // or
        // "Syncfusion_API_Key": "YOUR_API_KEY"
      }
    }
  }
}

// After creating the file, click Start in the inline action to install the server.
// Create a `.cursor/mcp.json` file in your workspace:

{
  "mcpServers": {
    "sf-aspnetcore-mcp": {
      "command": "dnx",
      "args": ["Syncfusion.AspNetCore.MCP", "--yes"],
      "env": {
        "Syncfusion_API_Key_Path": "YOUR_API_KEY_FILE_PATH"
        // or
        // "Syncfusion_API_Key": "YOUR_API_KEY"
      }
    }
  }
}
// Open AI Assistant chat, type /, and select Add Command.
// Click ➕ Add on the MCP settings page.
// Choose STDIO and select JSON configuration:

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

// Click OK, then click Apply. The server starts and shows Connected status.

For .NET 8 / .NET 9 (using a local tool):

You can install the Syncfusion ASP.NET Core MCP server as a local tool without a global installation. For guidance on installing and managing local .NET tools, refer to the official documentation.

Install the Syncfusion ASP.NET Core MCP tool locally:
```
 dotnet tool install Syncfusion.AspNetCore.MCP
```
If the project does not already have a tool manifest, create one first by running dotnet new tool-manifest in the project root. This generates a shared .config/dotnet-tools.json file that tracks local tools, then re-run the install command above.

In your MCP client config (for example, .vscode/mcp.json), replace the server entry with:

 {
   "servers": {
     "sf-aspnetcore-mcp": {
       "type": "stdio",
       "command": "dotnet",
       "args": ["tool", "run", "syncfusion-aspnetcore-mcp"],
       "env": {
         "Syncfusion_API_Key_Path": "YOUR_API_KEY_FILE_PATH"
         // or
         // "Syncfusion_API_Key": "YOUR_API_KEY"
       }
     }
   }
 }

Verifying Installation Check your editor’s MCP Server list for sf-aspnetcore-mcp with a Connected status to confirm a successful installation.

Common use cases

The examples below showcase how the search_docs tool handles real-world ASP.NET Core development scenarios. The tool can be invoked directly, as shown in the examples below, for specific needs. Alternatively, an AI assistant can automatically invoke it based on the request.

Get Started

Use search_docs to get contextual guidance, code snippets, and configuration examples for any component.

Grid with Paging & Sorting

#search_docs Create a Syncfusion ASP.NET Core Grid with paging, sorting, and filtering enabled.

RichTextEditor Setup

#search_docs How do I set up the Syncfusion ASP.NET Core RichTextEditor with a custom toolbar and form integration?

Implement Features

Get step-by-step help for adding specific features to components that are already in the project.

Grid Export

#search_docs How can I add PDF and Excel export options to my existing Grid’s toolbar?

Kanban Features

#search_docs How do I enable drag-and-drop and swimlane grouping in the Kanban component?

Troubleshooting

Describe the problem in plain language, and let search_docs help resolve it.

Grid Issues

#search_docs Why isn’t my Grid loading or rendering data correctly?

Schedule Issues

#search_docs Why aren’t my Schedule events displaying or saving correctly?

Best Practices

To get the most out of the Syncfusion^® ASP.NET Core MCP Servers:

Be Specific - Include the platform and component in your queries (for example, “Create a Syncfusion ASP.NET Core Grid with paging and filtering”).
Provide Context - Include applicable versions, expected outcomes, and any requirements or limitations that may affect the request.
Use Descriptive Queries - Avoid overly brief or ambiguous requests. Providing sufficient detail helps improve the accuracy and relevance of the response.
Stay Consistent - Keep file organization, naming conventions, and coding standards consistent throughout your ASP.NET Core project.
Start Fresh for New Topics - Begin a new chat when switching to a different component or task to maintain clean context.
Use Advanced AI Models - For the best results, use advanced AI models such as the latest-generation Claude, GPT, or Gemini models.
For Troubleshooting - Use AI suggestions for common issues; consult the official documentation or support for complex problems.
Minimize Active Tools - Limit the number of active MCP tools in your IDE to prevent tool-selection ambiguity and improve response accuracy.

Always review AI-generated code before using it in production.

Troubleshooting

The table below lists frequently encountered issues and suggested resolutions to help diagnose and address common setup or usage challenges.

Issue	Solution
Server failed to start	Update to .NET 8 SDK or higher, verify JSON syntax in the config file, and restart your IDE.
Invalid API key	Verify your key is active at the Syncfusion Account Page.
Incorrect API key config	For the file path: verify file location and content. For inline key: check the key is correctly updated.
Wrong config file location	VS Code: `.vscode/mcp.json` • Code Studio: `.codestudio/mcp.json` • Cursor: `.cursor/mcp.json` in the workspace root.
Check IDE logs	VS Code / Code Studio: Output panel → “MCP” • Cursor: Developer Console for MCP errors.

Privacy & Security

The Syncfusion^® MCP Servers are designed with privacy considerations:

The tools process requests according to the user’s query without storing any content or prompts.
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.

Search docs

Ask Syncfusion AI Assistant