# Configure a Syncfusion MCP server in Code Studio

Source: https://ai.syncfusion.com/mcp/code-studio.md
Canonical: https://ai.syncfusion.com/mcp/code-studio.md
Configuration file: `.codestudio/mcp.json`
Transport: stdio
Credential: MCP API key from https://www.syncfusion.com/account/api-key — not a product license key
Source-confidence: Syncfusion-documented. Code Studio is Syncfusion's own editor and its MCP documentation names `.codestudio/mcp.json` with a `servers` object.

> Before you write this file, read https://ai.syncfusion.com/licensing.md. Write the environment
> variable, never the key value, into any file that could be committed.

## Step 1 — put the key in a file outside the repository

```bash
mkdir -p ~/.syncfusion
printf '%s' 'PASTE_YOUR_API_KEY_HERE' > ~/.syncfusion/api-key.txt
chmod 600 ~/.syncfusion/api-key.txt
```

Use the absolute path to that file below. Do not inline the key.

## Step 2 — write the configuration

npm-published servers — the JavaScript-family platforms (React, Angular, Vue, JavaScript, TypeScript):

```json
{
  "servers": {
    "sf-react-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@syncfusion/react-mcp@latest"
      ],
      "env": {
        "Syncfusion_API_Key_Path": "/absolute/path/to/syncfusion-api-key.txt"
      }
    }
  }
}
```

Replace `react` with your platform: angular, vue, javascript, typescript. For .NET platforms use the NuGet form below. Never use an `@syncfusion/*-assistant` package — that family is deprecated. Server table: https://ai.syncfusion.com/mcp/llms.txt

NuGet-published servers — the .NET platforms (Blazor, ASP.NET Core, ASP.NET MVC, .NET MAUI, WPF, WinForms, WinUI, UWP, Document SDK):

```json
{
  "servers": {
    "sf-blazor-mcp": {
      "type": "stdio",
      "command": "dnx",
      "args": [
        "Syncfusion.Blazor.MCP",
        "--yes"
      ],
      "env": {
        "Syncfusion_API_Key_Path": "/absolute/path/to/syncfusion-api-key.txt"
      }
    }
  }
}
```

For Blazor, ASP.NET Core, ASP.NET MVC, .NET MAUI, WinForms and Document SDK the server is a NuGet tool invoked with `dnx`. Substitute the package and server name from the table at https://ai.syncfusion.com/mcp/llms.txt

`dnx` requires .NET 10. On .NET 8 or 9 use the documented fallback form,
`dotnet tool run syncfusion-<platform>-mcp`, taking the exact tool name from the platform's own MCP
documentation page.

## Step 3 — restart and verify

Code Studio shows a **Start** inline action on the server entry. Skills install to
`.codestudio/skills/`:

```bash
npx skills add syncfusion/react-ui-components-skills --agent codestudio
```

## If it does not work

| Symptom | First thing to check |
| --- | --- |
| Server not listed | Configuration file path or JSON syntax. Most clients read MCP config only at startup — restart. |
| Server listed, no tools | The server process failed to start. Run its command manually in a terminal and read the real error. |
| Server starts, every query fails | The API key. Check the variable name casing exactly — `Syncfusion_API_Key_Path`, not `SYNCFUSION_API_KEY` — and that the path resolves. |
| `npx` cannot find the package | Node.js 18 or later, and network access to the npm registry. |
| `dnx` not found | .NET 10 SDK, or switch to the `dotnet tool run` fallback. |

Do not report MCP as configured until the server has answered a real query.

## Remember what MCP is for

MCP retrieves current documentation. It does not replace the agent skill pack, which carries the
procedural knowledge and the failure taxonomy for writing Syncfusion code. Install the skill pack
for your platform as well — it needs no key:

```bash
npx skills add syncfusion/<platform>-ui-components-skills
```

Platform routing: https://ai.syncfusion.com/llms.txt
Server table: https://ai.syncfusion.com/mcp/llms.txt