@idealyst/mcp-server 1.2.104 → 1.2.105

package/dist/index.js

@@ -7,7 +7,7 @@ import {
   storageGuides,
   toolDefinitions,
   translateGuides
-} from "./chunk-ZDB2NURA.js";
+} from "./chunk-NRM3KHHB.js";
 
 // src/index.ts
 import { Server } from "@modelcontextprotocol/sdk/server/index.js";

package/dist/tools/index.cjs

@@ -168,13 +168,13 @@ var searchComponentsDefinition = {
 };
 var getComponentTypesDefinition = {
   name: "get_component_types",
-  description: "Get TypeScript type definitions for a specific component directly from the source. Returns the actual TypeScript interface and/or JSON schema. Supports comma-separated names to batch multiple components in one call (e.g., 'Button,Card,Text').",
+  description: "Get TypeScript type definitions for a specific component directly from the source. Returns the actual TypeScript interface and/or JSON schema.",
   inputSchema: {
     type: "object",
     properties: {
       component: {
         type: "string",
-        description: "The name of the component (e.g., 'Button', 'Card', 'Input'). Supports comma-separated names for batch lookup: 'Button,Card,Text,Icon'"
+        description: "The name of the component (e.g., 'Button', 'Card', 'Input')"
       },
       format: {
         type: "string",
@@ -11406,7 +11406,7 @@ This server has tools for every aspect of the framework. **Always look up the AP
 ### Workflow (be efficient \u2014 minimize tool calls)
 
 1. **Start here** \u2014 this intro covers conventions and gotchas
-2. **Look up components** \u2014 call \`get_component_types\` for EVERY component you plan to use. **Batch them in one call**: \`get_component_types({ component: "Button,Card,Text,View" })\` returns all types at once. (Card has NO compound components \u2014 no Card.Content/Card.Header)
+2. **Look up components** \u2014 call \`get_component_types\` for EVERY component you plan to use. Call it for each component you need. (Card has NO compound components \u2014 no Card.Content/Card.Header)
 3. **Look up packages** \u2014 call the dedicated \`get_*_guide\` tool with topic \`api\` for each \`@idealyst/*\` package
 4. **Check recipes** \u2014 call \`search_recipes\` to find ready-made patterns for common screens
 5. **Search icons ONCE** \u2014 combine all needed icon terms into ONE \`search_icons\` call (e.g., \`"home settings check timer calendar"\`)
@@ -11415,7 +11415,7 @@ This server has tools for every aspect of the framework. **Always look up the AP
 ### Component Tools
 - \`list_components\` / \`search_components\` \u2014 Discover available components
 - \`get_component_docs\` \u2014 Component features and best practices
-- \`get_component_types\` \u2014 **TypeScript prop interfaces** (supports batch: \`"Button,Card,Text"\`)
+- \`get_component_types\` \u2014 **TypeScript prop interfaces** for a component
 - \`get_component_examples_ts\` \u2014 Type-checked code examples
 - \`search_icons\` \u2014 Find Material Design icon names (7,447 available). **Batch your needs**: search once with multiple terms like \`"home settings user check"\` rather than making separate calls per icon