@idealyst/mcp-server 1.2.103 → 1.2.105

package/dist/index.cjs

@@ -9351,13 +9351,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",
@@ -15828,7 +15828,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"\`)
@@ -15837,7 +15837,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
 
@@ -15936,7 +15936,7 @@ These are mistakes agents make repeatedly. Each one causes TypeScript compilatio
 ### Imports & Styling
 16. **Never** import from \`react-native\` for UI \u2014 no \`TouchableOpacity\`, \`FlatList\`, \`ScrollView\`, \`Animated\`, \`Dimensions\`.
 17. **Never** import from \`react-native-unistyles\` \u2014 use \`@idealyst/theme\` (\`configureThemes\`, \`ThemeSettings\`, \`useTheme\`).
-18. **Custom styles**: Use \`useTheme()\` for theme tokens \u2014 it returns the Theme object **directly** (NOT wrapped): \`const theme = useTheme();\` then apply inline: \`style={{ padding: theme.spacing.md, backgroundColor: theme.colors.surface.primary }}\`. Do NOT use \`const { theme } = useTheme()\` \u2014 that causes TS2339. Do NOT use \`StyleSheet.create\` from react-native \u2014 use inline styles with theme tokens instead.
+18. **useTheme()** returns the Theme object **directly** (NOT wrapped): \`const theme = useTheme();\`. Do NOT destructure: \`const { theme } = useTheme()\` causes TS2339. Use theme tokens for colors and spacing: \`style={{ padding: theme.spacing.md, backgroundColor: theme.colors.surface.primary }}\`.
 
 ### React 19 TypeScript
 - **useRef** requires an initial argument: \`useRef<T>(null)\` \u2014 NOT \`useRef<T>()\`. Omitting the argument causes TS2554. For non-null refs use: \`useRef<number>(0)\`, \`useRef<string[]>([])\`.
@@ -24016,13 +24016,6 @@ function postProcessComponentTypes(componentName, result) {
       result.usageNote = 'Card is a SIMPLE CONTAINER \u2014 there are NO compound components. Do NOT use Card.Content, Card.Header, Card.Body, Card.Footer, Card.Title \u2014 they do NOT exist and will cause TS2339. Just put children directly inside <Card>...</Card>. Example: <Card padding="md"><Text>Title</Text><Text>Body</Text></Card>';
     }
   }
-  const resultStr = JSON.stringify(result);
-  if (resultStr.includes("IconName") || resultStr.includes("mdi:")) {
-    const iconNote = "\n\nICON NAME FORMAT: The `name` prop type shows `IconName | \"mdi:...\"` variants. Both formats work in JSX props. However, when you store icon names in variables, type them as `IconName` and use BARE names (without 'mdi:' prefix):\n```tsx\nimport type { IconName } from '@idealyst/components';\nconst icon: IconName = 'home';        // CORRECT\nconst icon: IconName = 'mdi:home';    // WRONG \u2014 TS error\nconst icon: string = 'home';          // WRONG \u2014 won't match IconName props\n```\nAlways use bare names like 'home', 'check-circle', 'arrow-left' \u2014 never 'mdi:home'.";
-    if (typeof result === "object" && result !== null) {
-      result.iconNameNote = iconNote;
-    }
-  }
   return result;
 }
 function getComponentExamplesTs(args) {