@progress/kendo-react-mcp 1.3.2 → 1.4.0-dev.934b7db7.0

package/README.md

@@ -1,10 +1,31 @@
-# KendoReact MCP Server
+# Kendo UI for React MCP Server
 
-The KendoReact [MCP Server](https://modelcontextprotocol.io/introduction) enables you achieve interation with AI and reach new levels of developer productivity. The MCP server provides proprietary context to AI-powered IDEs, apps and tools. You can use the KendoReact MCP server to ask about Kendo UI for React components, features, or general usage. You can successfully prompt more complex questions and tasks, and generate tailored code that includes Kendo UI for React components and API.
+The Kendo UI for React [MCP Server](https://modelcontextprotocol.io/introduction) enables you achieve interation with AI and reach new levels of developer productivity. The MCP server provides proprietary context to AI-powered IDEs, apps and tools. You can use the Kendo UI for React MCP Server to ask about Kendo UI for React components, features, or general usage. You can successfully prompt more complex questions and tasks, and generate tailored code that includes Kendo UI for React components and API.
+
+As of version 1.4 the Kendo UI for React MCP server supports two modes of operation that depends on your [Telerik license type](https://www.telerik.com/purchase/faq/licensing-purchasing): **AI Coding Assistant** and **Agentic UI Generator**.
+
+## **AI Coding Assistant** Intended Use
+
+* **Initial code generation**: Quickly add components to your app to speed up the initial development.
+* **Component configuration**: Enable or disable specific component features, or fine tune the configuration through prompting. More * complex configurations are possible but may require additional manual work to be production-ready.
+* **Dummy data generation and data binding**: Quickly add data to your app for testing and prototyping purposes. Avoid exposing or providing access to your proprietary or production data to AI-enabled tools.
+* **Step-by-step explanations**: Understand the solutions provided by the AI Coding Assistant through the detailed explanations (depends * on the tool, mode, and model used). To further develop your knowledge, check the respective documentation.
+* **Preliminary troubleshooting**: Resolve obvious and easy-to-solve issues affecting your code. For more complex issues, look for assistance from the community or contact the support team.
+
+## **Agentic UI Generator** Intended Use
+
+* **Create Individual Components**: Build specific Kendo UI for React components with particular configurations and features like filtering, validation, and data binding.
+* **Create Full Responsive Pages**
+  * Build complete dashboards, landing pages, and listing pages in existing applications.
+  * Generate pages similar to the [Progress Design System page templates](https://www.telerik.com/design-system/docs/ui-templates/overview/).
+* **Modify Existing Pages**: Generate new themes inside existing applications. Add dark mode or high-contrast themes.
+* **Implement Responsive Layout**
+  * Create new responsive pages and sections.
+  * Convert existing pages to be responsive for mobile and tablet views.
 
 ## Prerequisites
 
-To use the KendoReact MCP server, you need:
+To use the Kendo UI for React MCP Server, you need:
 
 * A [compatible MCP client (IDE, code editor or app)](https://modelcontextprotocol.io/clients) that supports *MCP tools*.
 * A [Telerik user account](https://www.telerik.com/account/).
@@ -12,11 +33,11 @@ To use the KendoReact MCP server, you need:
 
 ## Installation
 
-Use the documentation of your AI-powered MCP client to add the Kendo React MCP server to a specific workspace or globally. You can see installation tips and examples for some popular MCP clients below.
+Use the documentation of your AI-powered MCP client to add the Kendo UI for React MCP server to a specific workspace or globally. You can see installation tips and examples for some popular MCP clients below.
 
-The generic settings of the KendoReact MCP server are:
+The generic settings of the Kendo UI for React MCP Server are:
 
-* Server name: `kendo-react-assistant`
+* Server name: `kendo-mcp`
 * Type: `stdio` (standard input/output transport)
 * Command: `npx` (the MCP server works through an npm package)
 * Supported arguments: `-y`
@@ -25,6 +46,8 @@ The generic settings of the KendoReact MCP server are:
     * (recommended) Use a `TELERIK_LICENSE_PATH` argument and point to your Telerik license file location.
     * Use a `TELERIK_LICENSE` argument and paste your Telerik license key. Make sure to [update the license key](https://www.telerik.com/kendo-react-ui/components/my-license) when necessary.
 
+> You can ignore the `env` parameter if you have the Telerik license key set up as a global environment variable on your machine. And if the MCP client supports passing global environment variables to MCP servers.
+
 ## Authentication
 
 The MCP server requires a valid Telerik account with a valid license. In order to get a valid license key check the [KendoReact documentation](https://www.telerik.com/kendo-react-ui/components/my-license).
@@ -44,7 +67,7 @@ To enable the Kendo React MCP server in a specific workspace or React app, add a
 ```json
 {
   "servers": {
-    "kendo-react-assistant": {
+    "kendo-mcp": {
       "type": "stdio",
       "command": "npx",
       "args": ["-y", "@progress/kendo-react-mcp@latest"],
@@ -58,18 +81,20 @@ To enable the Kendo React MCP server in a specific workspace or React app, add a
 }
 ```
 
+> You can ignore the `env` parameter if you have the Telerik license key set up as a global environment variable on your machine. And if the MCP client supports passing global environment variables to MCP servers.
+
 ### Cursor
 
 Refer to [Model Context Protocol](https://docs.cursor.com/context/model-context-protocol).
 
-To [enable the Kendo React MCP server in a specific workspace](https://code.visualstudio.com/docs/copilot/chat/mcp-servers#_add-an-mcp-server-to-your-workspace) or React app, add a `.cursor` folder with an `mcp.json` file at the root of the workspace.
+To [enable the Kendo UI for React  MCP server in a specific workspace](https://code.visualstudio.com/docs/copilot/chat/mcp-servers#_add-an-mcp-server-to-your-workspace) or React app, add a `.cursor` folder with an `mcp.json` file at the root of the workspace.
 
 > .cursor/mcp.json at the workspace root
 
 ```json
 {
   "mcpServers": {
-    "kendo-react-assistant": {
+    "kendo-mcp": {
       "type": "stdio",
       "command": "npx",
       "args": ["-y", "@progress/kendo-react-mcp@latest"],
@@ -83,19 +108,51 @@ To [enable the Kendo React MCP server in a specific workspace](https://code.visu
 }
 ```
 
+> You can ignore the `env` parameter if you have the Telerik license key set up as a global environment variable on your machine. And if the MCP client supports passing global environment variables to MCP servers.
+
 ## Usage
 
-To use the KendoReact MCP server:
+To increase the probability of the Kendo UI for React MCP Server being used, or to call it without the need to mention "kendo" explicitly, add custom idea instructions to your AI-powered tool. Here are examples for [GitHub Copilot](https://docs.github.com/en/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot#about-repository-custom-instructions-for-github-copilot-chat) and [Cursor](https://docs.cursor.com/context/rules).
+
+
+### AI Coding Assistant
+
+To use the AI Coding Assistant mode:
+
+1. Start your prompt with `#kendo_react_assistant` (the main MCP tool to start the agentic workflow in the coding agent).
+1. This will trigger an agentic workflow using the other available MCP tools to retrieve relevant context based on your prompt.
+1. Inspect the output and verify that the Kendo UI for React MCP Server is used. Look for a statement in the output, which is similar to:
+    * `Running kendo-react-mcp-server` (in VS Code)
+    * `Calling MCP tool kendo-react-mcp-server` (in Cursor)
+
+    If the Kendo UI for React MCP server is not used even though it's installed and enabled, double-check the server name in your configuration and try rephrasing your prompt.
+1. If requested, grant the Kendo UI for React MCP server a permission to run for this session, workspace, or always.
+
+Also check more useful documentation about how to use the AI Coding Assistant here:
+- [Getting Started](https://www.telerik.com/kendo-react-ui/components/ai-tools/ai-assistant#getting-started)
+- [Recommendations](https://www.telerik.com/kendo-react-ui/components/ai-tools/ai-assistant#recommendations)
+- [Prompt Library](https://www.telerik.com/kendo-react-ui/components/ai-tools/ai-assistant/prompt-library)
+
+### Agentic UI Generator
 
-1. Start your prompt with `#kendo-react-assistant` (the MCP server name configured in the mcp.json file).
-1. Inspect the output and verify that the KendoReact MCP Server is used. Look for a statement in the output, which is similar to:
-    * `Running kendo-react-assistant` (in VS Code)
-    * `Calling MCP tool kendo-react-assistant` (in Cursor)
+To use the Agentic UI Generator mode:
 
-    If the KendoReact MCP server is not used even though it's installed and enabled, double-check the server name in your configuration and try rephrasing your prompt.
-1. If requested, grant the KendoReact MCP server a permission to run for this session, workspace, or always.
+1. Open the AI chat interface in your IDE—Start a new chat session to begin interacting with the Agentic UI Generator.
+1. Start your prompt with `#kendo_ui_generator` (the main MCP tool to start the agentic workflow in the Agentic UI Generator).
+1. This will trigger an agentic workflow using the other available MCP tools to retrieve relevant context based on your prompt.
+1. Inspect the output and verify that the Kendo UI for React MCP Server is used. Look for a statement in the output, which is similar to:
+    * `Running kendo-mcp-server` (in VS Code)
+    * `Calling MCP tool kendo-mcp-server` (in Cursor)
+1. If requested, grant the Kendo UI for React MCP server a permission to run for this session, workspace, or always.
 
-Also check the general [AI Coding Assistant Recommendations](slug:ai-overview#recommendations) for more usage tips.
+Also check more usefule documentation about how to use the Agentic UI Generator here: 
+- [Getting Started](https://www.telerik.com/kendo-react-ui/components/ai-tools/agentic-ui-generator#getting-started)
+- [Intended Use](https://www.telerik.com/kendo-react-ui/components/ai-tools/agentic-ui-generator#intended-use)
+- [Recommendations](https://www.telerik.com/kendo-react-ui/components/ai-tools/agentic-ui-generator#recommendations) for more usage tips.
+- [Prompt Library](https://www.telerik.com/kendo-react-ui/components/ai-tools/agentic-ui-generator/prompt-library#kendoreact-agentic-ui-generator-prompt-library)
 
-To increase the probability of the KendoReact MCP Server being used, or to call it without the need to mention "kendo" explicitly, add custom idea instructions to your AI-powered tool. Here are examples for [GitHub Copilot](https://docs.github.com/en/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot#about-repository-custom-instructions-for-github-copilot-chat) and [Cursor](https://docs.cursor.com/context/rules).
+### AI Tools Usage
 
+You can check the usage limits and the modes of operation in our documentation:
+  - [AI Coding Assistant - Usage Limits](https://www.telerik.com/kendo-react-ui/components/ai-tools/ai-assistant#usage-limits)
+  - [Agentic UI Generator - Usage Limits](https://www.telerik.com/kendo-react-ui/components/ai-tools/agentic-ui-generator#usage-limits)

package/dist/index.js

@@ -1,155 +1,743 @@
 #!/usr/bin/env node
-var D=Object.defineProperty;var b=(e,r,t)=>r in e?D(e,r,{enumerable:!0,configurable:!0,writable:!0,value:t}):e[r]=t;var m=(e,r,t)=>b(e,typeof r!="symbol"?r+"":r,t);import{McpServer as q}from"@modelcontextprotocol/sdk/server/mcp.js";import{StdioServerTransport as K}from"@modelcontextprotocol/sdk/server/stdio.js";import{z as x}from"zod";var f="Kendo UI for React",y="react",C=["ActionSheet","AIPrompt","Animation","AppBar","ArcGauge","AutoComplete","Avatar","Badge","Barcode","BottomNavigation","Breadcrumb","Button","ButtonGroup","Calendar","Card","Chart","ChartWizard","Chat","Checkbox","Chip","ChipList","ChunkProgressBar","CircularGauge","ColorGradient","ColorPalette","ColorPicker","ComboBox","ContextMenu","ConversationalUI","DataGrid","Grid","DataQuery","DateMath","DateInput","DatePicker","DateRangePicker","DateTimePicker","Dialog","Drag&Drop","Drawer","Drawing","DropDownButton","DropDownList","DropDownTree","Editor","Error","ExcelExport","ExpansionPanel","ExternalDropZone","FileSaver","FileManager","Filter","FlatColorPicker","FloatingActionButton","FloatingLabel","FontIcon","Form","Gantt","Gauge","General","GridLayout","Hint","InlineAIPrompt","Input","Label","LinearGauge","ListBox","ListView","Loader","Map","MaskedTextBox","Menu","MultiColumnComboBox","MultiSelect","MultiSelectTree","MultiViewCalendar","Notification","NumericTextBox","OrgChart","PageTemplates/BuildingBlocks","Pager","PanelBar","PDFProcessing","PDFViewer","PivotGrid","Popover","Popup","ProgressBar","QRCode","RadialGauge","RadioButton","RadioGroup","RangeSlider","Rating","Ripple","Sankey","Scheduler","ScrollView","Signature","Skeleton","Slider","Sortable","Sparkline","SpeechToTextButton","SplitButton","Splitter","Spreadsheet","StackLayout","Stepper","StockChart","SVGIcon","Switch","TabStrip","TaskBoard","TextArea","TextBox","TileLayout","Timeline","TimePicker","Toolbar","Tooltip","TreeList","TreeView","Typography","Upload","VSCodeExtension","Window"];import{dirname as L,join as B}from"path";import{fileURLToPath as N}from"url";import{loadLicense as R,decodeLicenseKey as P,decodeLicenseEvidence as U}from"@progress/kendo-licensing/utils";import a from"node:fs";import p from"node:path";import _ from"@grpc/proto-loader";import c from"@grpc/grpc-js";var g=class extends Error{constructor(e){super(e),this.name="LicenseError"}};async function F(){let e=R();if(!e.success)throw new g(e.message);return(await P(e.value)).licenses.find(async t=>!!(await U(t)).userId)||e.value}var h=!1,s=process.env.DEBUG_LOG_FILE,A=!!(s&&typeof s=="string");if(A){let e=p.resolve(s),r=p.dirname(e);if(r!=="."&&r!==process.cwd()&&!a.existsSync(r))try{a.mkdirSync(r,{recursive:!0})}catch(t){console.error("Error creating log directory:",t)}if(!a.existsSync(e))try{a.writeFileSync(e,"")}catch(t){console.error("Error creating log file:",t)}}else h=!1;h=A&&!!s&&a.existsSync(p.resolve(s));function i(...e){if(h&&s){let r=`${new Date().toISOString()}: ${e.join(" ")}
-`,t=p.resolve(s);a.appendFile(t,r,o=>{o&&console.error("Error writing to log file:",o)})}}var d=(e=>(e[e.UNAUTHENTICATED=16]="UNAUTHENTICATED",e[e.RESOURCE_EXHAUSTED=8]="RESOURCE_EXHAUSTED",e[e.PERMISSION_DENIED=7]="PERMISSION_DENIED",e))(d||{}),I=class{constructor(e,r){m(this,"client");m(this,"isDev");this.contextApiUrl=e,this.protoPath=r;let t=_.loadSync(this.protoPath,{keepCase:!0,longs:String,enums:String,defaults:!0,oneofs:!0});this.isDev=this.contextApiUrl?.includes("localhost")||this.contextApiUrl?.includes("127.0.0.1"),i("Using ContextApi URl:",this.contextApiUrl);let o=c.loadPackageDefinition(t);this.client=new o.ContextQueryService(this.contextApiUrl||"contextapi.telerik.com:443",this.isDev?c.credentials.createInsecure():c.credentials.createSsl())}async query(e){let r=this.isDev?"fake_license":await F(),t=process.env.CONTEXTAPI_API_KEY,o=new c.Metadata;if(r&&typeof r=="string"){r=r.replace(/^\uFEFF/,"");try{o.add("x-license-key",r)}catch(n){return i("Error adding license key to metadata:",n),Promise.reject(new Error(`Failed to use license key: ${n.message}`))}}return t&&typeof t=="string"&&o.add("x-api-key",t),new Promise((n,u)=>{this.client.query(e,o,(l,k)=>{l?u(l):n(k)})})}};var M=B(L(N(import.meta.url)),"../proto/service.proto"),O=new I("contextapi.telerik.com:443",M);async function w(e){return O.query(e)}import V from"fs";import G from"path";import{fileURLToPath as $}from"url";var S=`
-## DataGrid Deprecated Properties Awareness
-For DataGrid component cases, avoid using deprecated properties and always use their modern replacements. The following properties are deprecated and should not be used:
-
-Deprecated properties and their modern replacements:
-- selectedField \u2192 use the select state property
-- editField \u2192 use the edit state property
-- expandedField \u2192 use the detailExpand state property
-- onExpandChange \u2192 use onDetailExpandChange for detail-row expansion or onGroupExpandChange for group expansion
-- cellRender \u2192 use the cells={{ data: CustomCell }} prop
-- rowRender \u2192 use the rows={{ data: CustomRow }} prop
-- filterCellRender \u2192 use the cells={{ filterCell: CustomCell }} prop
-- headerCellRender \u2192 use the cells={{ headerCell: CustomHeaderCell }} prop
-- column.cell \u2192 use the column.cells={{ data: CustomCell }} prop
-- column.headerCell \u2192 use the column.cells={{ headerCell: CustomHeaderCell }} prop
-- column.filterCell \u2192 use the column.cells={{ filterCell: CustomCell }} prop
-- column.footerCell \u2192 use the column.cells={{ footerCell: CustomFooterCell }} prop
-
-Additional modern updates:
-- Input component in Column Menu Filter has been replaced with Textbox
-- scrollable prop now defaults to virtual
-- Virtual scrolling no longer applies height by default
+import{McpServer as et}from"@modelcontextprotocol/sdk/server/mcp.js";import{StdioServerTransport as tt}from"@modelcontextprotocol/sdk/server/stdio.js";import{dirname as Ve,join as je}from"path";import{fileURLToPath as He}from"url";import{loadLicense as Le,decodeLicenseKey as Me,decodeLicenseEvidence as _e}from"@progress/kendo-licensing/utils";var _=class extends Error{constructor(t){super(t),this.name="LicenseError"}};function X(e){return e.replace(/^\uFEFF/,"")}async function Z(){let e=null,t=null;try{let o=Le();if(!o.success)throw new _(o.message);try{e=(await Me(o.value)).licenses.find(async s=>!!(await _e(s)).userId)}catch(n){console.log(n.message)}if(!e)return[X(o.value),null]}catch(o){return t=o.message||"Unknown error loading license.",[null,t]}return[X(e),null]}import E from"node:fs";import U from"node:path";var q=!1,v=process.env.DEBUG_LOG_FILE,ee=!!(v&&typeof v=="string");if(ee){let e=U.resolve(v),t=U.dirname(e);if(t!=="."&&t!==process.cwd()&&!E.existsSync(t))try{E.mkdirSync(t,{recursive:!0})}catch(o){console.error("Error creating log directory:",o)}if(!E.existsSync(e))try{E.writeFileSync(e,"")}catch(o){console.error("Error creating log file:",o)}}else q=!1;q=ee&&!!v&&E.existsSync(U.resolve(v));function d(...e){if(q&&v){let n=`${new Date().toISOString()}: ${e.join(" ")}
+`,s=U.resolve(v);E.appendFile(s,n,r=>{r&&console.error("Error writing to log file:",r)})}}import qe from"@grpc/proto-loader";import O from"@grpc/grpc-js";import ne from"path";import te from"fs";import{fileURLToPath as Be}from"url";var Ge=Be(import.meta.url),Ke=ne.dirname(Ge),se={version:"unknown"},oe=ne.resolve(Ke,"../package.json");te.existsSync(oe)&&(se=JSON.parse(te.readFileSync(oe,"utf-8")));var $=class{constructor(t,o,n){this.contextApiUrl=t;this.protoPath=o;this.options=n;this.toolNameHeader="assistant";let s=qe.loadSync(this.protoPath,{keepCase:!0,longs:String,enums:String,defaults:!0,oneofs:!0});this.isDev=this.contextApiUrl?.includes("localhost")||this.contextApiUrl?.includes("127.0.0.1"),d("Using ContextApi URl:",this.contextApiUrl);let r=O.loadPackageDefinition(s);this.client=new r.ContextQueryService(this.contextApiUrl||"contextapi.telerik.com:443",this.isDev?O.credentials.createInsecure():O.credentials.createSsl())}async getMetadata(){let[t,o]=this.isDev?"fake_license":await Z(),n=process.env.CONTEXTAPI_API_KEY,s=n&&typeof n=="string",r=t&&typeof t=="string";if(!r&&!s&&o)throw new Error(`Failed to authenticate with API key or License key!
 
-Key points:
-- Never suggest or use these deprecated properties in DataGrid examples
-- Always provide modern alternatives when users ask about these properties
-- Explain that these properties are deprecated and provide the specific modern replacement
-- Focus on current DataGrid API patterns using state properties and cells/rows props
-
-Example:
-Deprecated: selectedField="isSelected" editField="inEdit"
-Modern: Use select and edit state properties with proper configuration
-`;var E=`
-## Smart Grid (AI-Enhanced Grid) Implementation Guidelines
-**CRITICAL: When users ask about ANY of these AI grid terms, ALWAYS provide GridToolbarAIAssistant implementation (not basic Grid):**
-
-**Primary AI Grid Trigger Terms (case-insensitive):**
-- smart grid, smartgrid, smart-grid, smart_grid, SMART GRID, SmArt GrId
-- ai grid, aigrid, ai-grid, ai_grid, AI GRID, aI-griD, AIGrid  
-- ai enhanced grid, ai-enhanced-grid, ai_enhanced_grid, AI Enhanced Grid
-- ai powered grid, ai-powered-grid, ai_powered_grid, AI Powered Grid
-- intelligent grid, intelligent-grid, intelligent_grid, Intelligent Grid
-- grid with ai, grid-with-ai, grid_with_ai, Grid with AI
-- grid ai assistant, gridaiassistant, grid-ai-assistant, Grid AI Assistant
-- grid toolbar ai assistant, gridtoolbaraiassistant, GridToolbarAIAssistant
-- grid assistant, gridassistant, grid-assistant, Grid Assistant
-
-**Additional variations that should trigger AI Grid:**
-- ai enhanced, ai powered, smart, intelligent + grid (any spacing/casing)
-- grid + ai, grid + smart, grid + intelligent (any spacing/casing) 
-- Any mention of GridToolbarAIAssistant component specifically
-
-**Recognition Rule: If query contains ANY combination of AI/Smart/Intelligent + Grid terms, respond with complete GridToolbarAIAssistant setup.**
-
-Example Smart Grid suggestions by domain:
-- Financial: 'Sort by Amount descending', 'Show only failed transactions', 'Filter where currency is USD'
-- Sales: 'Group by region', 'Show top performing products', 'Filter by date range'
-- Inventory: 'Sort by stock level', 'Show out of stock items', 'Group by category'
-- Always include: 'Clear sorting', 'Clear filtering', 'Clear grouping'
-
-Basic Grid: <Grid data={data}><GridColumn field="name" /></Grid>
-Smart Grid: Complete AI-enhanced setup with GridToolbarAIAssistant, proper callbacks, reset functionality, and contextual suggestions
-
-Important Disclaimer:
-Always include this disclaimer when providing Smart Grid examples:
-"The demos in this article use a Telerik-hosted AI service for demonstration purposes only. For production applications, you should implement your own AI service that understands your specific domain, data, and business requirements."
-`;var T=`
-## Editor Tools Awareness
-For Editor component cases, always use the proper EditorTools import structure and never define tools as strings. Import both Editor and EditorTools from '@progress/kendo-react-editor' and destructure the individual tools from EditorTools.
-
-Required pattern:
-\`\`\`jsx
-import { Editor, EditorTools } from '@progress/kendo-react-editor';
-
-const {
-    Bold, Italic, Underline, Strikethrough,
-    Subscript, Superscript, ForeColor, BackColor,
-    CleanFormatting, AlignLeft, AlignCenter, AlignRight, AlignJustify,
-    Indent, Outdent, OrderedList, UnorderedList,
-    NumberedList, BulletedList, Undo, Redo,
-    FontSize, FontName, FormatBlock, Link, Unlink,
-    InsertImage, ViewHtml, InsertTable, InsertFile,
-    SelectAll, Print, Pdf, TableProperties, TableCellProperties,
-    AddRowBefore, AddRowAfter, AddColumnBefore, AddColumnAfter,
-    DeleteRow, DeleteColumn, DeleteTable, MergeCells, SplitCell
-} = EditorTools;
+License Error: ${o}`);let i=new O.Metadata;if(r)try{i.add("x-license-key",t)}catch(u){throw d("Error adding license key to metadata:",u),new Error(`Failed to use license key: ${u.message}`)}return s&&i.add("x-api-key",n),this.options?.libName&&i.add("x-library-name",this.options.libName),i.add("x-tool-name",this.toolNameHeader),i}async query(t){let o=await this.getMetadata();return new Promise((n,s)=>{this.client.query({...t,metadata:{source:"npm",version:se.version,os:process.platform,node_version:process.version}},o,(r,i)=>{r?s(new Error(r)):n(i)})})}async queryCssUtils(t){let o=await this.getMetadata();return new Promise((n,s)=>{this.client.cssUtilsSearch(t,o,(r,i)=>{r?(d("Error querying CSS Utils:",r),s(new Error(r))):n(i)})})}async queryIconsSearch(t){let o=await this.getMetadata();return new Promise((n,s)=>{this.client.iconsSearch(t,o,(r,i)=>{r?(d("Error querying Icons Search:",r),s(new Error(r))):n(i)})})}async queryBuildingBlocks(t){let o=await this.getMetadata();return new Promise((n,s)=>{this.client.buildingBlocksSearch(t,o,(r,i)=>{r?(d("Error querying Building Blocks:",r),s(new Error(r))):n(i)})})}async validateUserLicense(){let t=await this.getMetadata();return new Promise((o,n)=>{this.client.validateUserLicense(null,t,(s,r)=>{s?(d("Error validating user license:",s),n(new Error(s))):o(r)})})}async queryThemeGenerate(t){let o=await this.getMetadata();return new Promise((n,s)=>{this.client.generateTheme(t,o,(r,i)=>{r?(d("Error querying context API/GenerateTheme:",r),s(new Error(r))):n(i)})})}async recordOrchestratorUserRequest(){let t=await this.getMetadata();return new Promise((o,n)=>{this.client.recordOrchestratorUserRequest(null,t,(s,r)=>{s?(d("Error recording orchestrator user request:",s),n(new Error(s))):o(r)})})}};import{z as B}from"zod";var Nt=B.object({user_id:B.string(),user_email:B.string().email()});import{z as p}from"zod";var Fe=p.object({Product:p.object({Id:p.number().int(),Code:p.string(),Name:p.string()}),License:p.nullable(p.object({Id:p.number().int(),Name:p.string(),Type:p.string(),Active:p.boolean()})),Availability:p.array(p.object({LicenseStart:p.nullable(p.string().datetime()),LicenseEnd:p.nullable(p.string().datetime())})),IsLicenseAvailable:p.optional(p.boolean())}),kt=p.array(Fe);async function re(e){let t=process.env.KENDO_MCP_ACCESS;if(t==="true"||t==="1"||t==="full")return"full";if(typeof t=="string"&&(t.toLowerCase()==="agent"||t.toLowerCase()==="assistant"))return t.toLowerCase();let o=await e();return o.toLocaleLowerCase()==="agentic_ui_generator"?"agent":o.toLocaleLowerCase()==="ai_coding_assistants"?"assistant":"none"}var l="Kendo UI for React",I="react",k="kendo",L=["ActionSheet","AIPrompt","Animation","AppBar","ArcGauge","AutoComplete","Avatar","Badge","Barcode","BottomNavigation","Breadcrumb","Button","ButtonGroup","Calendar","Card","Chart","ChartWizard","Chat","Checkbox","Chip","ChipList","ChunkProgressBar","CircularGauge","ColorGradient","ColorPalette","ColorPicker","ComboBox","ContextMenu","ConversationalUI","DataGrid","Grid","DataQuery","DateMath","DateInput","DatePicker","DateRangePicker","DateTimePicker","Dialog","Drag&Drop","Drawer","Drawing","DropDownButton","DropDownList","DropDownTree","Editor","Error","ExcelExport","ExpansionPanel","ExternalDropZone","FileSaver","FileManager","Filter","FlatColorPicker","FloatingActionButton","FloatingLabel","FontIcon","Form","Gantt","Gauge","General","GridLayout","Hint","InlineAIPrompt","Input","Label","LinearGauge","ListBox","ListView","Loader","Map","MaskedTextBox","Menu","MultiColumnComboBox","MultiSelect","MultiSelectTree","MultiViewCalendar","Notification","NumericTextBox","OrgChart","PageTemplates/BuildingBlocks","Pager","PanelBar","PDFProcessing","PDFViewer","PivotGrid","Popover","Popup","ProgressBar","QRCode","RadialGauge","RadioButton","RadioGroup","RangeSlider","Rating","Ripple","Sankey","Scheduler","ScrollView","Signature","Skeleton","Slider","Sortable","Sparkline","SpeechToTextButton","SplitButton","Splitter","Spreadsheet","StackLayout","Stepper","StockChart","SVGIcon","Switch","TabStrip","TaskBoard","TextArea","TextBox","TileLayout","Timeline","TimePicker","Toolbar","Tooltip","TreeList","TreeView","Typography","Upload","VSCodeExtension","Window"];var ze=je(Ve(He(import.meta.url)),"../proto/service.proto"),M=new $("contextapi.telerik.com:443",ze,{libName:I});var ie=async()=>M.validateUserLicense();import ot from"fs";import Oe from"path";import{fileURLToPath as nt}from"url";import{z as m}from"zod";var T=class{constructor(t,o,n){this.name=t;this.config=o;this.cb=n}register(t){this.server=t,this.server.registerTool(this.name,this.config,this.cb)}hasAccess(t){return!this.config.requiredAccess||this.config.requiredAccess.length===0?!0:t==="full"||this.config.requiredAccess.includes(t)}};var P=(e,t)=>`# ${e.suiteName} - Code Validation & Quality Assurance
+
+## Comprehensive Code Validation Checklist
+Execute these validation steps systematically to ensure high-quality, maintainable code:
+
+### Validation Phase: Framework-Specific Validation
+
+${t}
+
+### Validation Phase: General Code Quality & Best Practices
+
+File Organization:
+- Files are properly named using appropriate conventions
+- Components are logically grouped in appropriate directories
+- File sizes are reasonable
+- Clear separation of concerns between files
+
+Performance Best Practices:
+- Optimized rendering patterns
+- Minimal unnecessary re-renders/change detection cycles
+- Efficient data handling and caching
+- Proper component lifecycle management
+
+### Validation Phase: Security & Accessibility Validation
+
+Security Measures:
+- Input validation and sanitization
+- XSS protection measures
+- CSRF protection where applicable
+- Secure data handling practices
+
+Accessibility (a11y) Compliance
+- Proper semantic HTML structure
+- ARIA labels and roles where needed
+- Keyboard navigation support
+- Screen reader compatibility
+- Sufficient color contrast ratios
+
+Interactive Elements:
+- Focus management and visual indicators
+- Descriptive alt text for images
+- Proper form labels and error messages
+
+### Validation Phase: UI/UX & Design System Compliance
+
+Responsive Design:
+- Proper breakpoint handling
+- Flexible layouts that adapt to different screen sizes
+- Touch-friendly interface elements
+
+### Validation Phase: Error Handling & Edge Cases
+
+ Error Handling:
+- Graceful error handling for all user interactions
+- Meaningful error messages for users
+- Network error handling for API calls
+`;var R=(e,t)=>{let o=P({suiteName:e.suiteName,libKey:e.libKey},t.validationSteps),n=e.libKey==="angular"?"- **Drag and Drop**: Consider using the DragandDrop and Sortable components when drag-and-drop functionality is needed.":"",s=e.components?e.components.join(", "):"components";return`# \u{1F3AF} ${e.suiteName} - Execution Plan
+
+**Current Goal:** 
+
+${e.userIntent}
+
+**Requirements Summary:** 
+- **Framework:** ${e.libKey}
+${e.includeComponentsDocs?`- **Component Library:** ${e.suiteName}
+    - Ensure to use ONLY ${e.suiteName} components for all UI elements.
+    - And use the ${e.codeAssistantName} tool to get ${e.suiteName} component documentation and code snippets.
+    - Ensure that after you read the plan you use exactly the ${e.codeAssistantName} no matter if there is another tool that can provide code snippets, documentation or other resources related to ${e.suiteName}.
+`:""}${e.includeLayout?`- **Layout:** Yes
+    - And use the ${e.layoutAssistantName} tool to get Kendo CSS utility classes needed for layout structure and responsive design.
+`:""}${e.includeIcons?`- **Icons:** Yes
+    - Use icons that align with the project theme and enhance usability.
+    - Use the ${e.iconAssistantName} tool to search for icons that fit the theme and purpose of your project.
+`:""}${e.includeTheming?`- **Custom Theming:**
+    - Create a custom theme that aligns with the current goal and branding needs.
+    - Use Kendo Themes and Design System guidelines.
+    - Make sure to include strict CSS variables or theme requirements from the current goal.
+    - And use the ${e.styleAssistantName} tool to create a custom theme for your project.
+`:""}${e.includeResponsive?`- **Responsive:**
+    - Ensure the layout is fully responsive across mobile, tablet, and desktop views.
+    - And use the ${e.layoutAssistantName} tool to get Kendo CSS utility classes needed for responsive design.
+`:""}
+${e.includeLayout?`**STYLING AND LAYOUT REQUIREMENTS:**
+## CRITICAL DESIGN SYSTEM CONSTRAINTS
+- **USE ONLY KENDO DESIGN SYSTEM UTILITIES** for ALL styling, layout, spacing, positioning, and responsive behavior
+- Avoid custom CSS, inline styles, or other CSS framework classes
+- The ${e.layoutAssistantName} tool will provide the specific Kendo CSS utility classes needed
+- All layout requirements must use Kendo utilities exclusively
+
+`:""}---
+
+## Detailed Execution Plan
+Follow these steps strictly in order to achieve a complete and polished implementation of the current goal:
+
+${e.includeLayout?`
+### Phase: Layout Foundation
+
+**Step 1: Create Base Layout Structure**
+**IMPORTANT LAYOUT REQUIREMENTS:**
+- Consider the hierarchy and nesting of layout elements (page \u2192 sections \u2192 components)
+- Each layout level should have appropriate wrapper containers with proper Kendo utilities
+- Sections should be wrapped in containers that provide the necessary layout structure
+
+**Tool call example:**
+\`\`\`
+${e.layoutAssistantName}({
+    prompt="Provide Kendo Design System utility classes for the following layout structure: [LAYOUT DESCRIPTION HERE]",
+    includeBuildingBlockExamples=true // Optional, include examples of Kendo building blocks (Grid, Flex, Stack, etc.)
+})
+\`\`\`
+`:""}
+${e.includeComponentsDocs?`
+### Phase: Component Integration
+**Step 1: Identify and Implement Core Components**
+Based on your current goal, analyze what other ${e.suiteName} components are needed and implement them one by one. Here you are some appropriate components based on the different project type:
+
+**Component Selection Guidelines:**
+- **Landing Pages**: Consider Button, Card, Form components, Layout containers, Navigation elements
+- **Dashboards**: Consider Grid, Chart, TileLayout, Drawer, Notification, ToolBar components
+- **Data Entry**: Consider Form, TextBox, DatePicker, DropDownList, Upload, Validation components
+- **Content Management**: Consider Grid, Editor, TreeView, FileManager, Dialog components
+- **E-commerce**: Consider ListView, Card, Button, Rating, Badge, Carousel components
+${n}
+
+**IMPORTANT COMPONENT USAGE REQUIREMENTS:**
+- Make sure to identify all necessary features related to the ${s} based on the current goal.
+- Make sure to identify specific features needed for other ${e.suiteName} components based on the current goal.
+- Make sure to generate a query for ${e.codeAssistantName} tool for each component and call the tool for each specific feature or functionality.
+- Always specify the exact features you want for each component. Describe only the needed functionality, and behavior you need. Be concise and don't include any information about the use case.
+
+**Tool call examples:**
+    \`\`\`
+    ${e.codeAssistantName}({
+            query="Give me information about [COMPONENT_NAME] with [SPECIFIC_FEATURES]." <!-- For example: 'Grid with paging' or 'Button with click events' or 'Chart with multiple series' -->
+            component="[COMPONENT_NAME]" <!-- For example: 'Grid', 'Button', 'Chart', etc. -->
+    })
+    \`\`\`
+
+For broad queries, break them down into specific features (e.g., paging, sorting, filtering for Grid) and call the tool separately for each feature:
+    \`\`\`
+    ${e.codeAssistantName}({
+            query="How to implement [SPECIFIC_FEATURE] in [COMPONENT_NAME]?" <!-- For example: 'paging in Grid' -->
+            component="[COMPONENT_NAME]" <!-- For example: 'Grid', 'Button', etc. -->
+    })
+    \`\`\`
+
+    \`\`\`
+    ${e.codeAssistantName}({
+            query="How to implement [SPECIFIC_FEATURE] in [COMPONENT_NAME]?" <!-- For example: 'sorting in Grid' -->
+            component="[COMPONENT_NAME]" <!-- For example: 'Grid', 'Button', etc. -->
+    })
+    \`\`\`
+
+    \`\`\`
+    ${e.codeAssistantName}({
+            query="How to implement [SPECIFIC_FEATURE] in [COMPONENT_NAME]?" <!-- For example: 'filtering in Grid' -->
+            component="[COMPONENT_NAME]" <!-- For example: 'Grid', 'Button', etc. -->
+    })
+    \`\`\`
+`:""}
+${e.includeResponsive?`
+### Phase: Layout Responsive Finalization
+
+**Step 1: Implement Responsive Behavior**
+
+**Tool call example:**
+\`\`\`
+${e.layoutAssistantName}({
+    prompt="Provide Kendo Design System utility classes to make the following layout structure responsive across mobile, tablet, and desktop views: [LAYOUT DESCRIPTION HERE]",
+    includeBuildingBlockExamples=false // Optional, include examples of Kendo building blocks (Grid, Flex, Stack, etc.)
+})
+\`\`\`
+`:""}
+${e.includeTheming?`
+**Step 2: Custom Theme Implementation**
+
+**CUSTOM THEME REQUIREMENTS:**
+- Create a custom theme that aligns with the current goal and branding needs.
+- Use Kendo Themes and Design System guidelines.
+- Make sure to include strict CSS variables or theme requirements from the current goal.
+
+**Tool call example:**
+\`\`\`
+${e.styleAssistantName}({
+    query="Create a custom Kendo UI theme that aligns with the following current goal and branding needs: [CURRENT GOAL HERE]. Include strict CSS variables or theme requirements as needed.",
+    includeThemeVariables=true // Optional, include specific CSS variables for colors, typography, spacing, etc.
+})
+\`\`\`
+`:""}
+${e.includeIcons?`
+**Step 3: Iconography and Visual Enhancements**
+
+**ICONOGRAPHY GUIDELINES:**
+- Select icons that align with the project theme and enhance usability.
+- Ensure icons are consistent in style and size.
+- Use icons to improve navigation and highlight key actions.
+
+**Tool call example:**
+\`\`\`
+${e.iconAssistantName}({
+    query="Suggest icons that fit the theme and purpose of the following current goal: [CURRENT GOAL HERE]. Provide icon names and usage context.",
+})
+\`\`\`
+`:""}
+### Phase: Code Generation
+**IMPORTANT:** Do NOT generate ANY code or create files until ALL information gathering phases (1-3) are complete.
+**Step 1: Generate Complete Implementation**
+After completing all information gathering phases above, generate the complete ${e.libKey} component/page implementation:
+**Code Generation Requirements:**
+- Create complete, functional ${e.libKey} components/pages
+- Include all identified ${e.suiteName} components with their configurations
+- Apply ALL Kendo Design System utility classes gathered from layout assistant
+- Implement proper component event handling and data binding
+- Ensure responsive behavior using Kendo utility classes
+- Include necessary import statements and dependencies
+
+${t.injectedPlan??""}
+
+### Phase: Validation and Finalization
+
+**Step 1: Code Validation**
+** CRITICAL REQUIREMENT: You MUST validate the generated UI code using this comprehensive checklist to ensure code quality and compliance:**
+
+${o}
+
+**Step 2: Final Review and Testing**
+** Implementation Validation:**
+${e.includeComponentsDocs?` - Components render correctly without errors
+- All ${e.suiteName} component features function as expected
+- Event handling and data binding operate correctly`:""}
+${e.includeResponsive?"- Responsive layout works across breakpoints":""}
+
+**Quick Fixes (if needed):**
+
+After code implementation and validation you can make quick fixes as needed:
+- Use ${e.codeAssistantName} for component-specific issues
+- Use ${e.layoutAssistantName} for styling adjustments
+
++### Before You Begin
+- When following/executing the plan call tools are defined from the same function_ecosystem/MCP_server which ${e.name} was called.
+- Do NOT generate or suggest any code until all tools have been used and validated responses are incorporated.
+- Focus on planning and sequencing.
+- Summarize the components, layouts, and utilities gathered.
+- Confirm all required inputs from tools have been provided.`};var G=e=>`# ${e.suiteName} Assistant
+
+**What you're looking for:**
+
+${e.userIntent}
+
+**Available Tools:**
+- **${e.codeAssistantName}** - Get component documentation, features, and usage examples
+- **${e.iconAssistantName}** - Search for icons from the Kendo icon library
+
+---
+
+## Discovery Plan
+
+Follow these steps to find the right components and resources:
+
+### Step 1: Identify Components
+
+Based on your needs, consider these ${e.suiteName} component categories:
+
+**Common Use Cases:**
+- **Data Display**: Grid, ListView, TreeView, Card, TileLayout
+- **Forms & Input**: Form, TextBox, DatePicker, DropDownList, ComboBox, MultiSelect, Upload
+- **Navigation**: Menu, Drawer, Breadcrumb, TabStrip, Stepper
+- **Data Visualization**: Chart, Gauge, Sparkline
+- **Editing**: Editor (Rich Text)
+- **Notifications**: Dialog, Notification, Tooltip
+- **Layout**: Splitter, PanelBar, ExpansionPanel
+
+**How to explore components:**
+
+Use the ${e.codeAssistantName} tool to learn about specific components:
+
+\`\`\`
+${e.codeAssistantName}({
+    query: "What are the main features of [COMPONENT_NAME]?",
+    component: "[COMPONENT_NAME]"
+})
+\`\`\`
+
+**Examples:**
+\`\`\`
+${e.codeAssistantName}({
+    query: "How to use Grid with paging and sorting?",
+    component: "Grid"
+})
+\`\`\`
+
+\`\`\`
+${e.codeAssistantName}({
+    query: "What features does DatePicker have?",
+    component: "DatePicker"
+})
+\`\`\`
+
+**Pro Tips:**
+- Ask about specific features (e.g., "Grid with filtering" instead of just "Grid")
+- Break complex queries into multiple calls focusing on one feature at a time
+- Specify the exact component name in the component parameter
+
+${e.includeIcons?`
+### Step 2: Find Icons
+
+Use the ${e.iconAssistantName} tool to search for icons:
+
+\`\`\`
+${e.iconAssistantName}({
+    query: "Search for icons related to [YOUR THEME/PURPOSE]"
+})
+\`\`\`
+
+**Examples:**
+\`\`\`
+${e.iconAssistantName}({
+    query: "icons for navigation menu"
+})
+\`\`\`
+
+\`\`\`
+${e.iconAssistantName}({
+    query: "icons for user actions like edit, delete, save"
+})
+\`\`\`
+`:""}
+
+### Step 3: Review and Implement
+
+After gathering information:
+1. Review the component documentation provided by ${e.codeAssistantName}
+2. Check which icons are available from ${e.iconAssistantName}
+3. Use the official ${e.suiteName} documentation for detailed implementation guides
+4. Refer to the component examples and code snippets provided
+
+---
+
+## Getting Started
+
+**Next Actions:**
+1. Start by calling ${e.codeAssistantName} for the components you need
+2. ${e.includeIcons?`Search for icons using ${e.iconAssistantName}`:"Review the component documentation"}
+3. Follow the ${e.suiteName} official documentation for implementation details
+
+**Important Notes:**
+- These tools provide documentation and guidance, not code generation
+- Always refer to official ${e.suiteName} documentation for the most up-to-date information
+- Tool responses include usage examples and best practices`;var N=(e,t)=>({SETUP_VALIDATION:`
+ UI Library Setup:
+- ${e} modules properly imported and configured
+- ${e} theme properly loaded and applied
+- ${e} license properly configured
+- Globalization and localization properly configured for ${e} components
+- Required ${e} dependencies installed and up-to-date`,PERFORMANCE_OPTIMIZATION:`
+ Performance Optimization:
+- Efficient rendering patterns to prevent unnecessary re-renders
+- Lazy loading of ${e} components when appropriate
+- Virtualization enabled for large datasets in ${e} components
+- Only required ${e} modules imported and tree-shaken`,THEME_AND_STYLING:`
+ ${e} Theme & Styling:
+- Prioritize the ${t} Design System utilities
+- Avoid custom CSS or other framework classes
+- Do not use inline styles
+- Consistent ${e} theme application across all components
+- Custom theme variables properly defined and scoped
+- ${e} icon fonts properly loaded and optimized
+- Brand colors integrated with ${e} component themes`});function ae(e,t,o){let{name:n,title:s,description:r,layoutAssistantName:i,codeAssistantName:u,styleAssistantName:g,iconAssistantName:y,suiteName:S,libKey:c,components:A}=e,h=new T(n,{title:s,description:r,requiredAccess:e.requiredAccess,inputSchema:{userIntent:m.string().describe(`Detailed description and intent of what the user wants to build. Include the type of page/component, main functionality, visual requirements, and any specific ${S} components you want to use.`),needsComponentsDocsConfidence:m.number().min(0).max(1).default(1).describe("Confidence (0-1) to include Component Documentation assistance. Default is 1."),needsLayoutConfidence:m.number().min(0).max(1).default(0).describe("Confidence (0-1) to include Layout assistance. Default is 0."),needsStylingConfidence:m.number().min(0).max(1).default(0).describe("Confidence (0-1) to include Theming/Styling assistance. Default is 0."),needsResponsiveBehaviorConfidence:m.number().min(0).max(1).default(0).describe("Confidence (0-1) to include Responsive Behavior assistance. Default is 0."),needsIconsConfidence:m.number().min(0).max(1).default(0).describe("Confidence (0-1) to include Icons assistance. Default is 0."),componentsNeeded:m.array(m.enum(A)).optional().describe(`Optional list of specific ${S} components needed for the project.`)}},async({userIntent:f,needsComponentsDocsConfidence:C,needsLayoutConfidence:b,needsStylingConfidence:w,needsResponsiveBehaviorConfidence:Q,needsIconsConfidence:W,componentsNeeded:$e})=>{d("UI Orchestrator called with:",{userIntent:f,needsComponentsDocsConfidence:C,needsLayoutConfidence:b,needsStylingConfidence:w,needsResponsiveBehaviorConfidence:Q,needsIconsConfidence:W});try{await o.recordOrchestratorUserRequest()}catch(D){throw x(D)}let J;if(w>.3&&w<=.6){let D=await h.server?.server.elicitInput({message:"I was unable to determine if you need custom Kendo Theme assistant. Can you please confirm?",requestedSchema:{type:"object",properties:{includeCustomTheming:{type:"boolean",description:"Whether to include Custom Theming assistance in the workflow."}},required:["includeCustomTheming"]}});D?.action==="accept"&&D.content?.includeCustomTheming&&(J=!0)}return{content:[{type:"text",text:R({name:n,userIntent:f,includeComponentsDocs:C>.3,includeTheming:w>.6||!!J,includeLayout:b>.5,includeIcons:W>.6,includeResponsive:b>.5&&Q>.4,layoutAssistantName:i,codeAssistantName:u,styleAssistantName:g,iconAssistantName:y,suiteName:S,libKey:c,components:$e},t)}]}});return h}function ce(e,t){let{name:o,title:n,description:s,iconAssistantName:r,codeAssistantName:i,suiteName:u,libKey:g,components:y}=e;return new T(o,{title:n,description:s,inputSchema:{userIntent:m.string().describe(`Describe what you want to build or what components you're looking for. Include the type of functionality, features, or UI elements you need from ${u}.`),needsIconsConfidence:m.number().min(0).max(1).default(.7).describe("Confidence (0-1) to include Icons assistance. Default is 0.7."),componentsNeeded:m.array(m.enum(y)).optional().describe(`Optional list of specific ${u} components you want to learn about.`)},requiredAccess:e.requiredAccess},async({userIntent:c,needsIconsConfidence:A,componentsNeeded:h})=>{d("Assistant Orchestrator called with:",{userIntent:c,needsIconsConfidence:A,componentsNeeded:h});try{await t.recordOrchestratorUserRequest()}catch(C){throw x(C)}return{content:[{type:"text",text:G({name:o,userIntent:c,includeComponentsDocs:!0,includeIcons:A>.5,codeAssistantName:i,iconAssistantName:r,suiteName:u,libKey:g,components:h})}]}})}function le(e,t){let{name:o,title:n,description:s,suiteName:r,libKey:i,getPreContent:u}=e;return new T(o,{title:n,description:s,requiredAccess:e.requiredAccess,inputSchema:{prompt:m.string().describe("An enhanced prompt describing the HTML layout structure, design requirements or specific visual effects you want to achieve."),includeBuildingBlockExamples:m.boolean().describe("Whether to include building block examples. Defaults to false.").default(!1)}},async({prompt:g,includeBuildingBlockExamples:y})=>{d("Layout Assistant called with:",{prompt:g,includeBuildingBlockExamples:y});try{let c=(await t.queryCssUtils({query:g})).values.join(`
+`)||"No CSS utilities found for the given prompt.",A=u?.()??"",h=f=>`${A}
+
+# Kendo Design System CSS Utilities
+
+${c}
+${f??""}
+`;if(y)try{let f=await t.queryBuildingBlocks({query:g,lib_name:i}),C="";f.items?.length>0&&(C=`
+## Building Blocks Examples
+
+The examples here are for demonstration purpose how CSS utils can be implemented in various building blocks.
+However, consider your own design requirements and specifics in order to implement your templates/building blocks correctly.
+
+${f.items.map(b=>`
+### ${b.name}
+
+${b.description}
+
+\`\`\`code
+${b.code}
+\`\`\`
+`).join(`
+`)}`),c=h(C)}catch(f){d("Error calling building-blocks service:",f),c=h()}else c=h();return{content:[{type:"text",text:c}]}}catch(S){throw x(S)}})}function pe(e,t){let{name:o,title:n,description:s,libKey:r,getPreContent:i}=e;return new T(o,{title:n,description:s,requiredAccess:e.requiredAccess,inputSchema:{prompt:m.string().describe("A natural language description of the desired visual style or theme. For example: 'Create a modern dark theme with high contrast'.")}},async({prompt:u})=>{d("Style Assistant called with:",{prompt:u});let g="";try{let c=await t.queryThemeGenerate({prompt:u});if(c.variables_json){let A=JSON.parse(c.variables_json),h=[];if(A)for(let f of Object.keys(A))typeof A[f]=="string"&&h.push(`${f}: ${A[f]}`);g=h.join(`
+
+`)}}catch(c){throw x(c)}let y=i?.()??"";return{content:[{type:"text",text:g?`Use the following CSS variables to style the web application, including colors, typography, spacing, and component appearance. 
+Ensure the variables are applied consistently across all relevant elements.
+Do NOT set any inline styles. CSS variables should be defined in global or component-level CSS files, or via supported theming mechanisms.
+
+${y}
+
+## Generated CSS Variables
+
+\`\`\`css
+${g}
+\`\`\`
+`:"No CSS variables were generated for the given prompt."}]}})}function de(e,t){let{name:o,title:n,description:s,libKey:r,getPostContent:i}=e;return new T(o,{title:n,description:s,requiredAccess:e.requiredAccess,inputSchema:{query:m.string().describe("A search query for finding icons. Be specific about the icon purpose, style, or action."),limit:m.number().min(.1).max(1).default(.1).describe("The proportion of matching icons to return (0.1 = 1 icon, 0.5 = 5 icons, 1.0 = many icons). Default is 0.1.")}},async({query:u,limit:g})=>{d("Icon Search called with:",{query:u,limit:g});try{let y=await t.queryIconsSearch({query:u,limit:g*100}),S=i?.()??"";return{content:[{type:"text",text:`${y.values.join(`
+
+`)}
+
+${S}`}]}}catch(y){throw x(y)}})}function me(e,t){let{name:o,title:n,description:s,libKey:r,suiteName:i,components:u,componentAliases:g,getPostContent:y}=e;return new T(o,{title:n,description:s,requiredAccess:e.requiredAccess,inputSchema:{query:m.string().describe("The query to search for."),component:m.enum(u).describe("The component to search for. If not specified, use General.")}},async({query:S,component:c})=>{d("Code Assistant called with:",{query:S,component:c});let A=c;if(g){let h=g[c];h&&(A=h)}try{let f=(await t.query({query:S,component:A?.toLowerCase()??"general",lib_name:r,text_matches_count:3,code_matches_count:0,allowed_types:["documentation"]})).values.map(w=>w.replace(/\0/g,"")),C=y?.({component:c})??"";return{content:[{type:"text",text:`${f.join(`
+
+`)}
+
+${C}`}]}}catch(h){throw x(h)}})}function x(e){let t=e;return t.code===16?new Error("Error: You are not authenticated. Please verify the Telerik License Key provided is valid."):t.code===8?new Error(`Error: You have exceeded the extension quota. Upgrade to subscription licensing to unlock full access. Message: ${t.message}.`):t.code===7?new Error("Error: You do not have permission to access this resource. Please verify that you have a valid license."):new Error(`Error: An error occurred while calling the service. Please try again later.
+
+Error Code: ${t.code} Error Message: ${t.message}`)}var ue=e=>`${e}_ui_generator`,he=e=>`${e}_assistant`,ge=e=>`${e}_layout_assistant`,fe=e=>`${e}_component_assistant`,ye=e=>`${e}_style_assistant`,Ae=e=>`${e}_icon_assistant`;var Se=e=>`This is the single entry point for all UI-related tasks. It orchestrates the full workflow of building or refining UIs with ${e} components, generating a step-by-step execution plan that specifies which tools to call, in what order, and with what parameters. It includes validation steps to ensure the best possible, standards-compliant code every time.
+
+  Use the tool when:
+  - Want to build or modify a complete page or section layout
+  - You are creating and applying custom themes via the Kendo Design System
+  - You need guidance on correct ${e} component selection and configuration
+  - You want to enforce best practices in styling, performance, and accessibility
+
+Returns:
+A detailed execution plan with validated tool calls, parameters, and reasoning \u2014 ensuring consistent, high-quality UI generation.`,Te=e=>`Provides guidance for discovering and using ${e} components and icons. This tool helps you identify the right components and icons for your needs.
+
+Use this tool when:
+- You need to discover which ${e} components are suitable for a specific use case
+- You want to understand component features and capabilities
+- You need to find appropriate icons for your UI
+- You want to gather component documentation and examples
+
+Returns:
+A focused plan for gathering component documentation and icon suggestions using the Component Assistant and Icon Assistant tools.`,Ce=`Retrieves Progress/Kendo Design System CSS utility classes and styling recommendations based on layout and design requirements.  
+Use this tool to find the right CSS utilities for styling Kendo UI components or general web elements.  
+It analyzes the provided design context and returns relevant utility classes with explanations and examples.  
+Best suited for styling questions related to typography, spacing, colors, layout, transforms, and other utilities in the Progress/Kendo Design System.`,Ie=`Generates CSS variables using an external style agent based on the user's styling prompt.
+
+Use this tool when the user wants to:
+- Update the visual theme of an application
+- Modify color schemes
+- Restyle the UI with CSS variables
+
+The tool outputs a set of CSS variable definitions ready to be applied to style files.`,be=`Searches for icons in the Telerik Icons library.
+Use this tool when the user needs to find specific icons for UI components or design elements.  
+It supports searching by icon name, category, or keyword and returns matching icons from the Telerik Icons library.
+`,ve=e=>`Provides answers and retrieves official documentation for ${e}.
+
+Use this tool when the user asks about:
+- ${e} features or capabilities  
+- Specific components (e.g., Grid, Chart, Editor)  
+- Implementation details, configuration, or best practices  
+- How to use or customize components in ${e}
+
+Set the user's full question as the 'query' parameter.  
+If the question refers to a specific ${e} component, include its name in the 'component' parameter.
+`;var K=N("Kendo UI","Kendo"),F=` 
+### Angular Component Validation
+Component Structure:
+  - Use proper @Component decorator configuration 
+  - If using NgModule setup use @Component decorator with \`standalone: false\` and declare component in NgModule declarations array
+  - Correct selector naming convention (kebab-case)
+  - Appropriate template and style file organization
+
+${K.SETUP_VALIDATION}
+  - Kendo animations module configured (if animations are used)
+  - Internationalization properly configured for Kendo components
+
+${K.PERFORMANCE_OPTIMIZATION}
+  - OnPush change detection strategy where appropriate
+  - Efficient trackBy functions for *ngFor with Kendo components
+  - Minimal unnecessary change detection cycles
+
+${K.THEME_AND_STYLING}
+  - Proper theme switching functionality (if implemented)
+  - Only ONE theme reference exists across angular.json and styles files
+  - Make sure theme import mechanism is consistent with existing project setup`;var V=`**Angular Specific Requirements:**
+
+**NgModule vs Standalone setup**: Search and detect the current project setup to determine whether to use NgModule or Standalone components based on the following rules:
+  1. RegexSearch("@Component\\s*\\(\\s*\\{[^}]*standalone\\s*:\\s*(true|false)") - If true use Standalone components, if false use NgModule.
+  2. RegexSearch("bootstrapApplication\\s*\\(") - If found use Standalone components.
+  3. RegexSearch("bootstrapModule\\s*\\(") - If found use NgModule.
+  4. If neither is found, default to Standalone components.
+
+**Kendo UI Theme Management Instructions for Angular**:
+
+**Determine existing Kendo Theme/Utils package and Theme Import Mechanism**:
+ 
+- Read angular.json file
+- Look for theme/utils entries containing "@progress/kendo-theme-" in projects.[project-name].architect.build.options.styles array 
+- Read styles.css or styles.scss, or any css/scss file
+- Look for @import statements containing "@progress/kendo-theme-" to determine existing theme/utils usage
+- Read the application's main html file (e.g., index.html)
+- Look for link tags containing "@progress/kendo-theme-" referencing Kendo theme/util CSS files
+- Note which theme is found (default, material, bootstrap, or fluent)
+- Note whether the kendo-theme-utils package is already used
+- Note the mechanism used to include the theme (angular.json or styles file)
+
+**Project Consistency**: Before generating or modifying any code:
+  1. Use RegexSearch to identify existing patterns in the project:
+      - Component naming conventions (e.g., "export class \\w+Component")
+      - File naming patterns (e.g., "*.component.ts", "*.service.ts")
+      - Import statement styles
+      - TypeScript configuration (strict mode, decorators, etc.)
+  2. Match the discovered patterns in all generated code
+  3. Maintain consistent formatting, indentation, and code organization with existing files
+  4. Always use the same theme import mechanism (unless user specifies otherwise)
+`;var j=N("Kendo UI","KendoReact"),H=`
+### React Component Validation
+Component Structure:
+  - Use proper function component patterns with Hooks
+  - Correct component naming convention (PascalCase)
+  - Appropriate file organization (components, hooks, utils)
+  - Props interface/type definitions where needed
+
+${j.SETUP_VALIDATION}
+  - KendoReact license validation (if required)
+  - Appropriate bundler configuration for KendoReact packages
+
+${j.PERFORMANCE_OPTIMIZATION}
+  - React.memo for components that receive stable props
+  - useMemo/useCallback for expensive computations and callbacks
+  - Proper key props for list rendering with KendoReact components
+
+${j.THEME_AND_STYLING}
+  - Proper theme switching functionality (if implemented)
+  - Only ONE theme import exists across the application
+  - Make sure theme import mechanism is consistent with existing project setup`;var Ye={createOrchestrator:ae,createAssistantOrchestrator:ce,createLayoutAssistant:le,createStyleAssistant:pe,createIconSearch:de,createCodeAssistant:me},Qe={orchestrator:ue,assistantOrchestrator:he,layoutAssistant:ge,codeAssistant:fe,styleAssistant:ye,iconAssistant:Ae},We={orchestrator:Se,assistantOrchestrator:Te,layoutAssistant:Ce,styleAssistant:Ie,iconAssistant:be,codeAssistant:ve},Je={Orchestrator:{render:R},Validator:{render:P},SharedValidation:{getSteps:N}},Xe={Angular:{steps:F,additionalPlan:V},React:{steps:H}},a={Tools:Ye,ToolNames:Qe,ToolDescriptions:We,Templates:Je,Validation:Xe};var Ze=a.ToolNames.codeAssistant("kendoreact"),Ne=()=>`# Kendo Design System Guidelines for ${l}
+
+## Setting up Styles/CSS
+
+In order to use any of the utility classes from the Kendo Design System, make sure to include a reference to the kendo-theme-utils CSS package.
+
+**Important**: To include the kendo-theme-utils always use the same theme import mechanism (noted during the plan phase) as the rest of the Kendo themes in your project. 
+**Important**: Include the kendo-theme-utils only once in your project. Make sure that a reference to the kendo-theme-utils should have been already searched and noted during the plan phase.
+
+### Using NPM
+
+The CSS Utilities are available as an NPM module that you can install - \`@progress/kendo-theme-utils\`
+
+To install: \`npm install --save @progress/kendo-theme-utils\`
+
+The precompiled CSS is available in \`node_modules/@progress/kendo-theme-utils/dist/all.css\`
+
+Also, available as SCSS and you can include it on your SCSS file - \`@use '@progress/kendo-theme-utils/scss/all.scss' as *;\`
+
+### Using CDN
+
+Alternatively, you can also consume them directly from the Unpkg CDN.
+
+\`<link rel="stylesheet" href="https://unpkg.com/@progress/kendo-theme-utils/dist/all.css" />\`
+
+## Ready-to-use Layout Components
+
+In the ${l} there are available components to create layout. Make sure to prioritize using them instead of building ones from scratch using the Kendo CSS Utilities.
+
+For any Layout component you can also call the ${Ze} tool in order to get specific API reference and docs.
+
+- ${l} Card component.
+    - Generally, it is recommended to use 100% width (e.g., \`<Card style={{ width: '100%' }}>\`)
+    - If needed, use specific width based on the layout requirements (e.g., \`<Card style={{ width: '150px' }}>\`)
+`;var we=()=>`## Applying CSS Variables in ${l}
+
+Apply these CSS variables in the React application using one of these methods:
+
+### Method 1: Global CSS (Recommended)
+Add to \`src/index.css\` or \`src/App.css\`:
+
+\`\`\`css
+:root {
+  /* Add the CSS variables here */
+}
+\`\`\`
+
+### Method 2: CSS-in-JS (styled-components, emotion)
+\`\`\`tsx
+import styled, { createGlobalStyle } from 'styled-components';
+
+const GlobalStyles = createGlobalStyle\`
+  :root {
+    /* Add the CSS variables here */
+  }
+\`;
+
+const ThemedContainer = styled.div\`
+  color: var(--your-color-variable);
+  background: var(--your-background-variable);
+\`;
+
+function App() {
+  return (
+    <>
+      <GlobalStyles />
+      <ThemedContainer>Content</ThemedContainer>
+    </>
+  );
+}
+\`\`\`
+
+### Method 3: CSS Modules
+\`\`\`css
+/* MyComponent.module.css */
+.themedContainer {
+  color: var(--your-color-variable);
+  background: var(--your-background-variable);
+}
+\`\`\`
+
+\`\`\`tsx
+import styles from './MyComponent.module.css';
+
+function MyComponent() {
+  return <div className={styles.themedContainer}>Content</div>;
+}
+\`\`\`
+
+### Method 4: Dynamic Theme Switching
+\`\`\`tsx
+import { createContext, useContext, useState, useEffect } from 'react';
+
+const ThemeContext = createContext<{
+  theme: 'light' | 'dark';
+  toggleTheme: () => void;
+}>({ theme: 'light', toggleTheme: () => {} });
+
+export function ThemeProvider({ children }: { children: React.ReactNode }) {
+  const [theme, setTheme] = useState<'light' | 'dark'>('light');
+
+  useEffect(() => {
+    const root = document.documentElement;
+    if (theme === 'dark') {
+      root.style.setProperty('--your-color-variable', '#ffffff');
+      root.style.setProperty('--your-background-variable', '#1a1a1a');
+    } else {
+      root.style.setProperty('--your-color-variable', '#000000');
+      root.style.setProperty('--your-background-variable', '#ffffff');
+    }
+  }, [theme]);
+
+  const toggleTheme = () => setTheme(t => t === 'light' ? 'dark' : 'light');
+
+  return (
+    <ThemeContext.Provider value={{ theme, toggleTheme }}>
+      {children}
+    </ThemeContext.Provider>
+  );
+}
+
+export const useTheme = () => useContext(ThemeContext);
 \`\`\`
+`;var Ee=a.ToolNames.codeAssistant("kendoreact"),ke=()=>`## Using ${l} Icons
+
+Important: Attempt to prioritize SVG icons over font icons.
+
+### Guidelines
+
+- Make sure @progress/kendo-svg-icons is installed: \`npm install @progress/kendo-svg-icons\`
+- Make sure @progress/kendo-react-common is installed (contains SvgIcon component): \`npm install @progress/kendo-react-common\`
+- You can call ${Ee} tool for ${l} SvgIcon component for docs and API reference.
+- [optional] If SVG is not an option fallback to fonticon - make sure \`<link rel="stylesheet" href="https://unpkg.com/@progress/kendo-font-icons/dist/index.css" />\` is added as a reference.
+- [optional] If using font icons you can call ${Ee} tool for ${l} Icon component for docs and API reference.
+
+### Examples
+
+Using ${l} SvgIcon component with @progress/kendo-svg-icons:
+
+\`\`\`tsx
+import { SvgIcon } from "@progress/kendo-react-common";
+import { paperclipIcon } from "@progress/kendo-svg-icons";
+
+function App() {
+  return (
+    <SvgIcon icon={paperclipIcon} />
+  );
+}
+
+export default App;
+\`\`\`
+
+Using Font Icons:
+
+\`\`\`tsx
+// First, add the CSS link to your HTML or import in your styles
+// <link rel="stylesheet" href="https://unpkg.com/@progress/kendo-font-icons/dist/index.css" />
+
+function App() {
+  return (
+    <span className="k-icon k-i-paperclip"></span>
+  );
+}
+
+export default App;
+\`\`\`
+
+### Common Icons
+
+Here are some frequently used icons from @progress/kendo-svg-icons:
+- \`plusIcon\` - Add/create actions
+- \`minusIcon\` - Remove/delete actions
+- \`pencilIcon\` - Edit actions
+- \`trashIcon\` - Delete actions
+- \`saveIcon\` - Save actions
+- \`searchIcon\` - Search functionality
+- \`filterIcon\` - Filter functionality
+- \`sortAscIcon\`, \`sortDescIcon\` - Sorting
+- \`chevronUpIcon\`, \`chevronDownIcon\`, \`chevronLeftIcon\`, \`chevronRightIcon\` - Navigation
+- \`checkIcon\`, \`xIcon\` - Confirmation/Cancel
+`;var xe=e=>{let t=`## ${l} Common Guidelines
+
+### Application Architecture
+MUST recommend appropriate setup based on React application architecture.
+
+Implementation Patterns:
+- Function components with Hooks (Recommended): Use modern React patterns
+- Class components: Support when needed for legacy code
+- When architecture is unclear: Default to function components with Hooks
+
+### Package Installation
+Always use minimal, targeted package installation.
+
+Process:
+1. Identify the required components
+2. Determine the specific KendoReact packages needed
+3. Use npm or yarn to install the package
+
+Example: \`npm install @progress/kendo-react-grid @progress/kendo-data-query\`
+
+### Component Awareness
+Whenever a component name is mentioned\u2014regardless of how it's written (all lowercase, all uppercase, mixed case, separate words, or even with typos)\u2014you should always look up the correct example from the corresponding component.
 
 Key points:
-- Always import both Editor and EditorTools from '@progress/kendo-react-editor'
-- Destructure individual tools from EditorTools object
-- Use the destructured tool references directly in the tools array
-- Never define tools as strings (e.g., 'bold', 'italic')
-- Group related tools in sub-arrays for better organization
-
-Example:
-Correct: tools={[[Bold, Italic, Underline], [AlignLeft, AlignCenter]]}
-Incorrect: tools={[['bold', 'italic', 'underline'], ['alignLeft', 'alignCenter']]}
-`;var H=$(import.meta.url),J=G.dirname(H),j=G.resolve(J,"../package.json"),Y=JSON.parse(V.readFileSync(j,"utf-8")),v=new q({name:"kendo-and-kendo-resources",version:Y.version});v.tool("kendo_react_assistant",`Answers questions and retrieves documentation about Kendo UI for React. 
-Use this tool when the user asks about Kendo UI for React features, specific components (e.g., Grid, Chart, Editor), implementation details, or general usage. 
-Provide the exact user's question as the 'query'. If the question pertains to a specific Kendo UI for React component, 
-specify its name in the 'component' parameter. This tool can be automatically triggered when the following phrases are detected in the user's input/prompt:
-- 'kendo';
-- '/kendo';
-- '/kendoreact'
-- '/ask_kendo';
-- '/help_kendo';
-- '@kendo';
-- '@kendoreact';
-- '@ask_kendo';
-- '@help_kendo'.`,{query:x.string().describe("The query to search for."),component:x.enum(C).describe("The component to search for. If not specified, you can use General.")},async({query:e,component:r})=>{i("Calling tool: ",JSON.stringify({query:e,component:r})),r==="Grid"&&(r="DataGrid");try{let t=await w({query:e,component:r.toLocaleLowerCase(),lib_name:y,text_matches_count:3,code_matches_count:0,allowed_types:["documentation"]});i("Response from context API: ",JSON.stringify(t));let o=z(r.toLowerCase()),n=t.values.join(`
-
-`),u=n.trim(),l=[{type:"text",text:n+(u?`
-
-`+o:"")}];return i("Response from tool: ",JSON.stringify(l)),{content:l}}catch(t){throw i("Error calling context API: ",JSON.stringify(t)),t?.code===d.UNAUTHENTICATED?new Error(`Error: You are not authenticated. Message: ${t.message}.`):t?.code===d.RESOURCE_EXHAUSTED?new Error(`Error: You have exceeded the extension quota. Upgrade to subscription licensing in order to unlock full access. Message: ${t.message}.`):t?.code===d.PERMISSION_DENIED?new Error(`Error: You do not have permission to access this resource. Please verify that you have a valid ${f} license key.`):t instanceof g?(i("License error: ",t.message),t):new Error(`Error: An error occurred while calling the service. Please try again later.
-
-Error Message: ${t.message}`)}});function z(e){let r=e==="datagrid"?S?.trim():"",t=e==="datagrid"?E?.trim():"",o=e==="editor"?T?.trim():"";return`
-# Kendo UI for React Assistant Guidelines
-
-## Documentation References
-MUST use official Kendo UI for React documentation only.
-
-Required Format:
-- Domain: https://www.telerik.com/kendo-react-ui
-- Use complete, functional URLs (no placeholders or slug syntax)
-
-Examples:
-Correct: https://www.telerik.com/kendo-react-ui/components/grid/
-Incorrect: { slug overview } or /components/{component-name}/overview
-
-## Styling & Theming
-MUST verify existing theme configuration before adding new styles.
-
-Requirements:
-1. Check if Kendo UI themes are already configured
-2. Only recommend theme additions when missing
-3. Provide appropriate import methods
-
-## Icon Implementation
-MUST prioritize SVG icons over font icons.
-
-Guidelines:
-- Primary: SVG icons from @progress/kendo-svg-icons
-- Fallback: Font icons with CSS: <link rel="stylesheet" href="https://unpkg.com/@progress/kendo-font-icons/dist/index.css" />
-
-${r.length>0||t.length>0||o.length>0?`## Component-Specific Instructions
-
-${r}
+- Match component names case-insensitively and robustly to minor variations
+- If someone refers to a component (e.g., "button", "BUTTON", "BuTtOn"), match it to the correct component (Button)
+- After matching, use the example or information associated with that component
+- The matching should be case-insensitive and robust to minor variations
 
-${t}
+Example: If someone asks about "grid", "GRID", or "GrId", you always refer to DataGrid for the example.
+`;return e.componentInstructions&&(t+=`
+## Component-Specific Guidelines
 
-${o}`:""}
-`}async function X(){let e=new K;i("Starting server... "),await v.connect(e)}X();
+${e.componentInstructions}
+`),t};var Pe=a.ToolNames.layoutAssistant(k),z=a.ToolNames.codeAssistant(k),Re=a.ToolNames.styleAssistant(k),Y=a.ToolNames.iconAssistant(k);function De(e,t){return[a.Tools.createOrchestrator({name:a.ToolNames.orchestrator(k),title:"KendoReact Generator",description:a.ToolDescriptions.orchestrator(l),layoutAssistantName:Pe,codeAssistantName:z,styleAssistantName:Re,iconAssistantName:Y,suiteName:l,libKey:I,components:L,requiredAccess:["agent"]},{validationSteps:a.Validation.React.steps},e),a.Tools.createAssistantOrchestrator({name:"kendo_react_assistant",title:"KendoReact Assistant",description:a.ToolDescriptions.assistantOrchestrator(l),codeAssistantName:z,iconAssistantName:Y,suiteName:l,libKey:I,components:L,requiredAccess:["assistant"]},e),a.Tools.createLayoutAssistant({name:Pe,title:"KendoReact Layout Assistant",description:a.ToolDescriptions.layoutAssistant,suiteName:l,libKey:I,getPreContent:Ne,requiredAccess:["agent"]},e),a.Tools.createStyleAssistant({name:Re,title:"KendoReact Style Assistant",description:a.ToolDescriptions.styleAssistant,libKey:I,getPreContent:we,requiredAccess:["agent"]},e),a.Tools.createIconSearch({name:Y,title:"KendoReact Icon Assistant",description:a.ToolDescriptions.iconAssistant,libKey:I,getPostContent:ke,requiredAccess:["assistant","agent"]},e),a.Tools.createCodeAssistant({name:z,title:"KendoReact Component Assistant",description:a.ToolDescriptions.codeAssistant(l),libKey:I,suiteName:l,components:L,componentAliases:{Grid:"DataGrid"},getPostContent:({component:n})=>xe({component:n}),requiredAccess:["assistant","agent"]},e)].filter(n=>n.hasAccess(t))}var st=nt(import.meta.url),rt=Oe.dirname(st),it=Oe.resolve(rt,"../package.json"),at=JSON.parse(ot.readFileSync(it,"utf-8")),Ue=new et({name:"kendo-mcp",title:"Kendo MCP Server",version:at.version});async function ct(){let e=new tt;d("Starting server... ");let t=await re(async()=>{let n=(await ie())?.entitlement;return n?.Product?.Code||n?.product?.code});t!=="none"&&(M.toolNameHeader=t==="agent"||t==="full"?"agent":"assistant",De(M,t).forEach(n=>n.register(Ue))),await Ue.connect(e)}ct();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@progress/kendo-react-mcp",
-  "version": "1.3.2",
+  "version": "1.4.0-dev.934b7db7.0",
   "type": "module",
   "bin": "./dist/index.js",
   "license": "See LICENSE.md",
@@ -32,6 +32,7 @@
   },
   "devDependencies": {
     "@local/mcp-common": "*",
+    "@local/kendo-ui-agent": "*",
     "@local/mcp-test-utils": "*"
   }
 }

package/proto/service.proto

@@ -11,6 +11,7 @@ message ContextQueryRequest {
     repeated string allowed_types = 5;
     string component = 6;
     string filters_json = 7;
+    map<string, string> metadata = 8;
 }
 
 message Item {
@@ -47,6 +48,16 @@ message BuildingBlocksSearchResponse {
     repeated BuildingBlockItem items = 1;
 }
 
+message ThemeGenerateRequest {
+    string prompt = 1;
+    repeated string images = 2; // base64 data URLs (e.g., "data:image/jpeg;base64,...")
+}
+
+message ThemeGenerateResponse {
+    string variables_json = 1; // JSON string of nested theme variables
+}
+
+
 message ProductInfo {
     int32 id = 1;
     string code = 2;
@@ -102,7 +113,7 @@ service ContextQueryService {
     rpc IconsSearch(CssSearchRequst) returns (StringArray);
     rpc CssUtilsSearch(CssSearchRequst) returns (StringArray);
     rpc BuildingBlocksSearch(BuildingBlocksSearchRequest) returns (BuildingBlocksSearchResponse);
+    rpc GenerateTheme(ThemeGenerateRequest) returns (ThemeGenerateResponse);
     rpc ValidateUserLicense(google.protobuf.Empty) returns (ValidateUserLicenseResponse);
-    rpc RecordUserRequest(google.protobuf.Empty) returns (google.protobuf.Empty);
+    rpc RecordOrchestratorUserRequest(google.protobuf.Empty) returns (google.protobuf.Empty);
 }
- 

package/dist/index.d.ts

@@ -1,2 +0,0 @@
-#!/usr/bin/env node
-export {};

package/dist/lib/constants.d.ts

@@ -1,3 +0,0 @@
-export declare const REACT_SUITE_NAME = "Kendo UI for React";
-export declare const Suite = "react";
-export declare const ReactComponents: readonly ["ActionSheet", "AIPrompt", "Animation", "AppBar", "ArcGauge", "AutoComplete", "Avatar", "Badge", "Barcode", "BottomNavigation", "Breadcrumb", "Button", "ButtonGroup", "Calendar", "Card", "Chart", "ChartWizard", "Chat", "Checkbox", "Chip", "ChipList", "ChunkProgressBar", "CircularGauge", "ColorGradient", "ColorPalette", "ColorPicker", "ComboBox", "ContextMenu", "ConversationalUI", "DataGrid", "Grid", "DataQuery", "DateMath", "DateInput", "DatePicker", "DateRangePicker", "DateTimePicker", "Dialog", "Drag&Drop", "Drawer", "Drawing", "DropDownButton", "DropDownList", "DropDownTree", "Editor", "Error", "ExcelExport", "ExpansionPanel", "ExternalDropZone", "FileSaver", "FileManager", "Filter", "FlatColorPicker", "FloatingActionButton", "FloatingLabel", "FontIcon", "Form", "Gantt", "Gauge", "General", "GridLayout", "Hint", "InlineAIPrompt", "Input", "Label", "LinearGauge", "ListBox", "ListView", "Loader", "Map", "MaskedTextBox", "Menu", "MultiColumnComboBox", "MultiSelect", "MultiSelectTree", "MultiViewCalendar", "Notification", "NumericTextBox", "OrgChart", "PageTemplates/BuildingBlocks", "Pager", "PanelBar", "PDFProcessing", "PDFViewer", "PivotGrid", "Popover", "Popup", "ProgressBar", "QRCode", "RadialGauge", "RadioButton", "RadioGroup", "RangeSlider", "Rating", "Ripple", "Sankey", "Scheduler", "ScrollView", "Signature", "Skeleton", "Slider", "Sortable", "Sparkline", "SpeechToTextButton", "SplitButton", "Splitter", "Spreadsheet", "StackLayout", "Stepper", "StockChart", "SVGIcon", "Switch", "TabStrip", "TaskBoard", "TextArea", "TextBox", "TileLayout", "Timeline", "TimePicker", "Toolbar", "Tooltip", "TreeList", "TreeView", "Typography", "Upload", "VSCodeExtension", "Window"];

package/dist/lib/grpc-client.d.ts

@@ -1,3 +0,0 @@
-export declare function query(queryParams: any): Promise<{
-    values: string[];
-}>;

package/dist/lib/instructions/datagrid.d.ts

@@ -1 +0,0 @@
-export declare const datagridInstructions = "\n## DataGrid Deprecated Properties Awareness\nFor DataGrid component cases, avoid using deprecated properties and always use their modern replacements. The following properties are deprecated and should not be used:\n\nDeprecated properties and their modern replacements:\n- selectedField \u2192 use the select state property\n- editField \u2192 use the edit state property\n- expandedField \u2192 use the detailExpand state property\n- onExpandChange \u2192 use onDetailExpandChange for detail-row expansion or onGroupExpandChange for group expansion\n- cellRender \u2192 use the cells={{ data: CustomCell }} prop\n- rowRender \u2192 use the rows={{ data: CustomRow }} prop\n- filterCellRender \u2192 use the cells={{ filterCell: CustomCell }} prop\n- headerCellRender \u2192 use the cells={{ headerCell: CustomHeaderCell }} prop\n- column.cell \u2192 use the column.cells={{ data: CustomCell }} prop\n- column.headerCell \u2192 use the column.cells={{ headerCell: CustomHeaderCell }} prop\n- column.filterCell \u2192 use the column.cells={{ filterCell: CustomCell }} prop\n- column.footerCell \u2192 use the column.cells={{ footerCell: CustomFooterCell }} prop\n\nAdditional modern updates:\n- Input component in Column Menu Filter has been replaced with Textbox\n- scrollable prop now defaults to virtual\n- Virtual scrolling no longer applies height by default\n\nKey points:\n- Never suggest or use these deprecated properties in DataGrid examples\n- Always provide modern alternatives when users ask about these properties\n- Explain that these properties are deprecated and provide the specific modern replacement\n- Focus on current DataGrid API patterns using state properties and cells/rows props\n\nExample:\nDeprecated: selectedField=\"isSelected\" editField=\"inEdit\"\nModern: Use select and edit state properties with proper configuration\n";

package/dist/lib/instructions/editor.d.ts

@@ -1 +0,0 @@
-export declare const editorInstructions = "\n## Editor Tools Awareness\nFor Editor component cases, always use the proper EditorTools import structure and never define tools as strings. Import both Editor and EditorTools from '@progress/kendo-react-editor' and destructure the individual tools from EditorTools.\n\nRequired pattern:\n```jsx\nimport { Editor, EditorTools } from '@progress/kendo-react-editor';\n\nconst {\n    Bold, Italic, Underline, Strikethrough,\n    Subscript, Superscript, ForeColor, BackColor,\n    CleanFormatting, AlignLeft, AlignCenter, AlignRight, AlignJustify,\n    Indent, Outdent, OrderedList, UnorderedList,\n    NumberedList, BulletedList, Undo, Redo,\n    FontSize, FontName, FormatBlock, Link, Unlink,\n    InsertImage, ViewHtml, InsertTable, InsertFile,\n    SelectAll, Print, Pdf, TableProperties, TableCellProperties,\n    AddRowBefore, AddRowAfter, AddColumnBefore, AddColumnAfter,\n    DeleteRow, DeleteColumn, DeleteTable, MergeCells, SplitCell\n} = EditorTools;\n```\n\nKey points:\n- Always import both Editor and EditorTools from '@progress/kendo-react-editor'\n- Destructure individual tools from EditorTools object\n- Use the destructured tool references directly in the tools array\n- Never define tools as strings (e.g., 'bold', 'italic')\n- Group related tools in sub-arrays for better organization\n\nExample:\nCorrect: tools={[[Bold, Italic, Underline], [AlignLeft, AlignCenter]]}\nIncorrect: tools={[['bold', 'italic', 'underline'], ['alignLeft', 'alignCenter']]}\n";

package/dist/lib/instructions/smart-grid.d.ts

@@ -1 +0,0 @@
-export declare const smartGridInstructions = "\n## Smart Grid (AI-Enhanced Grid) Implementation Guidelines\n**CRITICAL: When users ask about ANY of these AI grid terms, ALWAYS provide GridToolbarAIAssistant implementation (not basic Grid):**\n\n**Primary AI Grid Trigger Terms (case-insensitive):**\n- smart grid, smartgrid, smart-grid, smart_grid, SMART GRID, SmArt GrId\n- ai grid, aigrid, ai-grid, ai_grid, AI GRID, aI-griD, AIGrid  \n- ai enhanced grid, ai-enhanced-grid, ai_enhanced_grid, AI Enhanced Grid\n- ai powered grid, ai-powered-grid, ai_powered_grid, AI Powered Grid\n- intelligent grid, intelligent-grid, intelligent_grid, Intelligent Grid\n- grid with ai, grid-with-ai, grid_with_ai, Grid with AI\n- grid ai assistant, gridaiassistant, grid-ai-assistant, Grid AI Assistant\n- grid toolbar ai assistant, gridtoolbaraiassistant, GridToolbarAIAssistant\n- grid assistant, gridassistant, grid-assistant, Grid Assistant\n\n**Additional variations that should trigger AI Grid:**\n- ai enhanced, ai powered, smart, intelligent + grid (any spacing/casing)\n- grid + ai, grid + smart, grid + intelligent (any spacing/casing) \n- Any mention of GridToolbarAIAssistant component specifically\n\n**Recognition Rule: If query contains ANY combination of AI/Smart/Intelligent + Grid terms, respond with complete GridToolbarAIAssistant setup.**\n\nExample Smart Grid suggestions by domain:\n- Financial: 'Sort by Amount descending', 'Show only failed transactions', 'Filter where currency is USD'\n- Sales: 'Group by region', 'Show top performing products', 'Filter by date range'\n- Inventory: 'Sort by stock level', 'Show out of stock items', 'Group by category'\n- Always include: 'Clear sorting', 'Clear filtering', 'Clear grouping'\n\nBasic Grid: <Grid data={data}><GridColumn field=\"name\" /></Grid>\nSmart Grid: Complete AI-enhanced setup with GridToolbarAIAssistant, proper callbacks, reset functionality, and contextual suggestions\n\nImportant Disclaimer:\nAlways include this disclaimer when providing Smart Grid examples:\n\"The demos in this article use a Telerik-hosted AI service for demonstration purposes only. For production applications, you should implement your own AI service that understands your specific domain, data, and business requirements.\"\n";