← All agents / Gemini CLI
Gemini CLI + Syncfusion
Terminal-based coding agent that works with your repository and development tools.
Quick start
Open Gemini CLI in your project and send one prompt. It handles the setup from there.
Paste the setup prompt
This is the only setup instruction you need to provide. Gemini CLI may ask you to approve commands before running them.
No license, API key, or account is needed to read the setup instructions or install the skills. Using Syncfusion libraries in an application requires a commercial, Community, or trial license.
What Gemini CLI does
- Fetches the official setup instructions.
- Installs the Syncfusion onboarding skill.
- Detects the project platform from its manifest.
- Finds and installs the appropriate Syncfusion skills.
- Reads the applicable licensing guidance.
- Checks whether MCP is configured and reports any action you need to take.
What the setup provides
Agent skills
Component-aware instructions cover setup, packages, imports, modules and services, properties, events, theming, accessibility, and common failure modes.
Read from .agents/skills/ in the project or
~/.gemini/skills/ globally.
Optional MCP documentation retrieval
MCP retrieves current Syncfusion documentation using a separate MCP API key. It is not required for public documentation or installed skills.
Agent-readable documentation
/llms.txt — routing · /llms-full.txt — full documentation · /agent-setup/prompt.md — setup instructions
Advanced manual setup
The quick-start prompt is sufficient for normal setup. Use this section only when you want to configure optional live documentation retrieval yourself.
Configure MCP — optional
MCP gives Gemini CLI live Syncfusion documentation retrieval. It requires an API key from your Syncfusion account. This is not a product license key.
MCP location: ~/.gemini/settings.json
Follow the exact Gemini CLI MCP configuration guide.
Variable casing is exact. Use Syncfusion_API_Key_Path. Never put the API key value in a file that could be committed.
Example prompts
After setup, give Gemini CLI a normal development request without naming a package or platform.
Verify it worked
In a fresh session, ask Gemini CLI to add a Syncfusion component. Confirm three signals.
| 1 | It identifies the platform from the project manifest before writing code. |
| 2 | It reads the installed skill rather than producing a remembered snippet. |
| 3 | It mentions license registration and does not emit a key. |
If it writes Syncfusion code from memory, the onboarding setup did not complete or the installed skill was not loaded. Restart Gemini CLI and run the setup prompt again.
Frequently asked
- Do I need a Syncfusion license to use the setup instructions?
- No. Reading the instructions and installing supported skills requires no license, key, or account. Using Syncfusion libraries requires a commercial, Community, or trial license.
- Is MCP required?
- No. MCP retrieves current documentation and requires an API key. Public routing and platform documentation work without it.
- Is the MCP API key the same as my license key?
- No. The MCP API key authenticates documentation retrieval. A product license key covers your use of Syncfusion libraries.