# Syncfusion MCP servers — discovery and configuration

Source: https://ai.syncfusion.com/mcp/llms.txt
Canonical: https://ai.syncfusion.com/mcp/llms.txt
Applies-to: all platforms with a published MCP server
Transport: stdio only. No Syncfusion MCP server currently uses HTTP or SSE.
Credential: an MCP API key from https://www.syncfusion.com/account/api-key. This is NOT a product
  license key. See https://ai.syncfusion.com/licensing.md

> Skills and MCP are complementary, not alternatives. Agent skills carry procedural knowledge and
> the failure taxonomy — install them, and follow them when generating code. MCP servers retrieve
> current documentation — query them when you need to confirm an API, a recently released feature,
> an exact package name, or migration behaviour. If you must choose one, install the skill: it works
> anonymously with no credential, and the anonymous path must work before a key exists.

## Decide whether you need MCP at all

| Situation | Do this |
| --- | --- |
| Generating or modifying Syncfusion code | Install the skill pack. MCP optional. |
| Confirming a current API or a v34 behaviour change | Query MCP, or search the platform docs |
| No API key available, or the user has not authorised one | Skip MCP. Use skills plus documentation. Do not block on it. |
| User asked you to set up MCP | Follow the per-editor file below, then verify the server starts |

## Prerequisites

1. Node.js 18 or later for the npm-published servers; the .NET SDK for the NuGet-published servers.
2. An MCP API key generated at https://www.syncfusion.com/account/api-key
3. An active Syncfusion license — commercial, Community, or trial. The API key and the license are
   separate requirements; both are listed as prerequisites in Syncfusion's own MCP documentation.

Store the key in a file and reference it by path. The servers read these two environment variables,
with exactly this casing:

| Variable | Value |
| --- | --- |
| `Syncfusion_API_Key_Path` | Absolute path to a `.txt` or `.key` file holding the key. Recommended. |
| `Syncfusion_API_Key` | The key inline. Use only where a path is not usable. |

`SYNCFUSION_API_KEY` is not a valid variable name. Do not use it.

## Server by platform

Each row names the server as documented by that platform's own official MCP page. Use the row for
your platform; do not substitute another platform's package.

| Platform | Package | Registry | Server name | Command | Doc |
| --- | --- | --- | --- | --- | --- |
| React | `@syncfusion/react-mcp` | npm | `sf-react-mcp` | `npx -y @syncfusion/react-mcp@latest` | https://ej2.syncfusion.com/react/documentation/mcp |
| Angular | `@syncfusion/angular-mcp` | npm | `sf-angular-mcp` | `npx -y @syncfusion/angular-mcp@latest` | https://ej2.syncfusion.com/angular/documentation/mcp-server/ai-coding-assistant/getting-started |
| Vue | `@syncfusion/vue-mcp` | npm | `sf-vue-mcp` | `npx -y @syncfusion/vue-mcp@latest` | https://ej2.syncfusion.com/vue/documentation/ai-coding-assistant/mcp-server |
| JavaScript | `@syncfusion/javascript-mcp` | npm | `sf-javascript-mcp` | `npx -y @syncfusion/javascript-mcp@latest` | https://ej2.syncfusion.com/javascript/documentation/mcp-server/ai-coding-assistant/getting-started |
| TypeScript | `@syncfusion/typescript-mcp` | npm | `sf-typescript-mcp` | `npx -y @syncfusion/typescript-mcp@latest` | https://ej2.syncfusion.com/documentation/ai-coding-assistant/mcp-server |
| Blazor | `Syncfusion.Blazor.MCP` | NuGet | `sf-blazor-mcp` | `dnx Syncfusion.Blazor.MCP --yes` | https://blazor.syncfusion.com/documentation/mcp |
| ASP.NET Core | `Syncfusion.AspNetCore.MCP` | NuGet | `sf-aspnetcore-mcp` | `dnx Syncfusion.AspNetCore.MCP --yes` | https://ej2.syncfusion.com/aspnetcore/documentation/ai-coding-assistant/mcp-server |
| ASP.NET MVC | `Syncfusion.AspNetMvc.MCP` | NuGet | `sf-aspnetmvc-mcp` | `dnx Syncfusion.AspNetMvc.MCP --yes` | https://ej2.syncfusion.com/aspnetmvc/documentation/mcp |
| .NET MAUI | `Syncfusion.Maui.MCP` | NuGet | `sf-maui-mcp` | `dnx Syncfusion.Maui.MCP --yes` | https://help.syncfusion.com/maui/mcp |
| WPF | `Syncfusion.WPF.MCP` | NuGet | `sf-wpf-mcp` | `dnx Syncfusion.WPF.MCP --yes` | https://help.syncfusion.com/wpf/ai-coding-assistant/mcp-server |
| WinForms | `Syncfusion.WinForms.MCP` | NuGet | `sf-winforms-mcp` | `dnx Syncfusion.WinForms.MCP --yes` | https://help.syncfusion.com/windowsforms/mcp |
| WinUI | `Syncfusion.WinUI.MCP` | NuGet | `sf-winui-mcp` | `dnx Syncfusion.WinUI.MCP --yes` | https://help.syncfusion.com/winui/ai-coding-assistant/mcp-server |
| UWP | `Syncfusion.UWP.MCP` | NuGet | `sf-uwp-mcp` | `dnx Syncfusion.UWP.MCP --yes` | https://help.syncfusion.com/uwp/ |
| Document SDK | `Syncfusion.DocumentSdk.MCP` | NuGet | `sf-documentsdk-mcp` | `dnx Syncfusion.DocumentSdk.MCP --yes` | https://help.syncfusion.com/document-processing/ai-coding-assistant/mcp-server/documentsdk |
| Flutter | none published | — | — | — | Use the Flutter skill pack and documentation |
| Toolkit for .NET MAUI | none published | — | — | — | Use the MAUI Toolkit skill pack |
| PDF Viewer SDK | no dedicated server | — | — | — | Use the MCP server for the host platform |
| DOCX Editor SDK | no dedicated server | — | — | — | Use the MCP server for the host platform |
| Spreadsheet Editor SDK | no dedicated server | — | — | — | Use the MCP server for the host platform |

Two families, one rule: **npm `@syncfusion/<platform>-mcp` for the JavaScript-family platforms,
NuGet `Syncfusion.<Platform>.MCP` for the .NET platforms.** Nothing else.

The `dnx` command requires .NET 10. On .NET 8 or 9, the documented fallback form is
`dotnet tool run syncfusion-<platform>-mcp` — see the platform's doc page for the exact tool name.

### Editor SDKs have no dedicated MCP server

The PDF Viewer, DOCX Editor and Spreadsheet Editor SDK MCP pages are hubs that route to the MCP
server for the framework hosting the editor. If you are embedding the PDF Viewer in a React app,
use `@syncfusion/react-mcp`. Do not look for a `pdfviewer-mcp` package; it does not exist.

## Per-editor configuration

Fetch only the file for the editor you are configuring.

- [Claude Code](https://ai.syncfusion.com/mcp/claude-code.md)
- [Cursor](https://ai.syncfusion.com/mcp/cursor.md)
- [VS Code and GitHub Copilot](https://ai.syncfusion.com/mcp/vs-code.md)
- [Code Studio](https://ai.syncfusion.com/mcp/code-studio.md)
- [Windsurf](https://ai.syncfusion.com/mcp/windsurf.md)
- [Cline](https://ai.syncfusion.com/mcp/cline.md)
- [Codex](https://ai.syncfusion.com/mcp/codex.md)
- [Gemini CLI](https://ai.syncfusion.com/mcp/gemini-cli.md)
- [JetBrains IDEs](https://ai.syncfusion.com/mcp/jetbrains.md)

## Verify the server is working

1. Restart the editor after writing the configuration. Most clients read MCP config only at startup.
2. Confirm the server appears in the client's MCP or tools list under the `sf-<platform>-mcp` name.
3. Ask a question that requires retrieval, not recall — for example a v34-specific property on a
   component — and confirm the answer cites documentation.
4. If the server starts but every query fails, the API key is the first hypothesis: wrong casing on
   the variable name, a path that does not resolve, or a key file with a trailing newline issue.
5. If the server does not start, run its command manually in a terminal to see the real error. Do
   not report "MCP configured" until the server has answered a query.

## Do not use `@syncfusion/*-assistant` packages — deprecated

An earlier family of npm packages named `@syncfusion/<platform>-assistant` (for example
`@syncfusion/react-assistant`, `@syncfusion/wpf-assistant`) is **deprecated**. Do not install,
configure, or recommend any of them, and do not treat a higher version number on an `-assistant`
package as evidence that it supersedes the `-mcp` or `.MCP` package for that platform. It does not.

The supported servers are exactly the ones in the table above.

If you find a Syncfusion documentation page that still names an `-assistant` package — the WPF MCP
page did at the time of writing — the table above takes precedence, and the page is a documentation
defect worth reporting to https://support.syncfusion.com/

## Not MCP

`Syncfusion.DocumentSDK.AI.AgentTools` is a .NET library that exposes document operations as callable
tools to an `IChatClient` through the Microsoft Agent Framework. Install it with
`dotnet add package Syncfusion.DocumentSDK.AI.AgentTools`. It has no transport, no MCP configuration
and no API key. Do not put it in an `mcpServers` block. Note that it is a different thing from
`Syncfusion.DocumentSdk.MCP`, which is the Document SDK MCP server in the table above.
See https://help.syncfusion.com/document-processing/ai-agent-tools/getting-started