Set Up An AI Coding Agent For Syncfusion

How an agent configures Syncfusion

The setup instruction establishes the platform, skill, documentation, and licensing context before the agent writes code.

1. Read the canonical instructions Fetch https://ai.syncfusion.com/llms.txt and follow its routing rules.
2. Install and read the onboarding skill Run npx skills add syncfusion/agent-onboarding-skill.
3. Detect the project platform Inspect repository manifests such as package.json, *.csproj, or pubspec.yaml. Do not infer the platform only from the user’s wording.
4. Read the platform index Fetch https://ai.syncfusion.com/<platform-slug>/llms.txt. All 18 platform indexes are listed below.
5. Install the required skills Install only the skills identified by the onboarding flow and inventory before generating Syncfusion code.
6. Read the licensing boundary Read https://ai.syncfusion.com/licensing.md before requesting, handling, or registering any credential.
7. Report the result Tell the user which platform was detected, which skills were installed, whether an MCP server is available, and whether any human action is required.

Set up your coding agent

Choose an agent to see where it reads project skills, where its MCP configuration belongs, and how to confirm the setup.

Most agents read project skills from the shared .agents/skills/ directory; Claude Code, Windsurf and Syncfusion Code Studio use a vendor-specific directory. Any agent that can fetch a URL can be set up the same way by pointing it at /agent-setup/prompt.md.

Platforms

Platform and SDK skill packs

After detecting the repository platform, read its llms.txt index. Each index names the official skill pack, required product packages, licensing requirements, a working example, known failure modes, and setup checks.

18 packs, 775 skills, 9,400+ reference documents. Platforms marked None published have no dedicated MCP server — Use the required skills and the documentation. MIT marks a package that requires no product license key.

Browse the skill catalog

MCP servers

Current documentation through MCP

Syncfusion MCP servers give compatible coding agents access to current documentation and API details. MCP is optional and complements the official skills; it does not replace them.

An MCP API key is not a Syncfusion product license key and does not grant product rights.

• Flutter and Syncfusion Toolkit for .NET MAUI do not have dedicated MCP servers. Use the skill pack and the documentation.
• PDF Viewer, DOCX Editor, and Spreadsheet Editor SDKs use the MCP server for the framework that hosts them.
• All servers use stdio transport and read the same two environment variables. Casing is exact: Syncfusion_API_Key_Path or Syncfusion_API_Key.

Read the MCP server index and editor configuration

Component registry

Named variants. Complete source. One fetch.

Every variant has a permanent name that resolves in two places — the machine twin in /gallery/ and the registry JSON in /r/. Fetch the JSON and you have the whole file, the exact dependencies, and the licensing position. No second request.

# Step 1: Discover available items for any platform
GET https://ai.syncfusion.com/r/{platform-slug}/registry.json
# Supported slugs: angular, blazor, react, vue, javascript, aspnet-core, aspnet-mvc, maui, winforms, wpf, winui

# Step 2: Fetch a specific component variant

# All platforms (direct access):
GET https://ai.syncfusion.com/r/{platform-slug}/{registry-item}.json
# Examples:
GET https://ai.syncfusion.com/r/blazor/grid-default.json
GET https://ai.syncfusion.com/r/angular/chart-line.json

# React only (available in ts and js variants):
GET https://ai.syncfusion.com/r/react/{ts|js}/{registry-item}.json
# Examples:
GET https://ai.syncfusion.com/r/react/ts/chart-line.json
GET https://ai.syncfusion.com/r/react/js/chart-line.json

# source inlined · deps pinned · no auth · CORS open

Selected variants