@idealyst/mcp-server 1.2.104 → 1.2.106

package/dist/index.js

@@ -7,7 +7,7 @@ import {
   storageGuides,
   toolDefinitions,
   translateGuides
-} from "./chunk-ZDB2NURA.js";
+} from "./chunk-NX77GGPR.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",
@@ -3667,7 +3667,7 @@ function VideoRecordingScreen() {
       )}
       <Button
         onPress={handleToggleRecording}
-        intent={camera.isRecording ? 'error' : 'primary'}
+        intent={camera.isRecording ? 'danger' : 'primary'}
       >
         {camera.isRecording ? 'Stop Recording' : 'Record Video'}
       </Button>
@@ -6151,6 +6151,10 @@ function ArticleView({ content }: { content: string }) {
 
 ## Custom Link Handling
 
+**IMPORTANT**: Do NOT import \`Linking\` from \`react-native\` for opening URLs. The Markdown component has built-in cross-platform link handling via \`linkHandler\`:
+- \`openExternalLinks: true\` \u2014 opens external URLs in the system browser (cross-platform, no imports needed)
+- \`onLinkPress\` \u2014 intercept link taps for internal navigation
+
 \`\`\`tsx
 import React from 'react';
 import { Markdown } from '@idealyst/markdown';
@@ -6165,11 +6169,11 @@ function DocumentView({ markdown }: { markdown: string }) {
         onLinkPress: (url) => {
           if (url.startsWith('/')) {
             navigate({ path: url });
-            return true; // Prevent default browser behavior
+            return true; // Handled \u2014 prevent default
           }
-          return false; // Allow external links to open normally
+          return false; // Not handled \u2014 openExternalLinks takes over
         },
-        openExternalLinks: true,
+        openExternalLinks: true, // Opens external URLs cross-platform (no Linking import needed!)
       }}
     >
       {markdown}
@@ -11406,7 +11410,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 +11419,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
 
@@ -11512,13 +11516,23 @@ These are mistakes agents make repeatedly. Each one causes TypeScript compilatio
 15. \`useParams()\` does NOT accept generic type arguments. It returns \`Record<string, string>\`. Do NOT write \`useParams<{ id: string }>()\` \u2014 that causes TS2558.
 
 ### Imports & Styling
-16. **Never** import from \`react-native\` for UI \u2014 no \`TouchableOpacity\`, \`FlatList\`, \`ScrollView\`, \`Animated\`, \`Dimensions\`.
+16. **Never** import from \`react-native\` \u2014 no \`TouchableOpacity\`, \`FlatList\`, \`ScrollView\`, \`Animated\`, \`Dimensions\`, \`Linking\`, \`Platform\`. Idealyst provides cross-platform alternatives for all of these (e.g., \`openExternalLinks\` on Markdown, \`Pressable\` from \`@idealyst/components\`).
 17. **Never** import from \`react-native-unistyles\` \u2014 use \`@idealyst/theme\` (\`configureThemes\`, \`ThemeSettings\`, \`useTheme\`).
-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 }}\`.
+18. **useTheme()** returns the Theme object **directly** (NOT wrapped): \`const theme = useTheme();\`. Do NOT destructure: \`const { theme } = useTheme()\` \u2014 causes TS2339.
+19. **Spacing & Layout**: Use component shorthand props for spacing \u2014 NOT \`theme.spacing\` (which does NOT exist). The correct patterns:
+   - \`<View padding="md" gap="md">\` \u2014 shorthand props on View/Card
+   - \`<View paddingHorizontal="lg" marginVertical="sm">\` \u2014 directional shorthands
+   - \`style={{ backgroundColor: theme.colors.surface.primary }}\` \u2014 inline styles for colors only
+   - \`theme.radii.md\` \u2014 border radius values (this DOES exist)
+   - **WRONG**: \`theme.spacing.md\` \u2014 does NOT exist, causes TS2339
+   - **WRONG**: \`theme.colors.intent.danger\` \u2014 does NOT exist; intents are at \`theme.intents.danger\`
+
+### Cross-Platform (CRITICAL)
+20. **Never use raw HTML/SVG elements** (\`<svg>\`, \`<circle>\`, \`<canvas>\`, \`<div>\`, \`<span>\`, \`<input>\`) \u2014 they are web-only and will crash on React Native, just like react-native primitives crash on web. Also never use CSS \`transition\` or \`animation\` properties in styles \u2014 they don't exist on native. If you need custom drawing or circular progress, use \`@idealyst/animate\` hooks or \`@idealyst/charts\` \u2014 never raw SVG.
+21. **Avoid web-only CSS** like \`cursor: 'pointer'\` in shared styles \u2014 not valid on native. Use \`Pressable\` or \`Button\` for interactive elements (they handle cursor automatically on web).
 
 ### 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[]>([])\`.
-- **Avoid web-only CSS** like \`cursor: 'pointer'\` in shared styles \u2014 not valid on native. Use \`Pressable\` or \`Button\` for interactive elements (they handle cursor automatically on web).
 
 ### Scaffolded Project Layout
 When working in a CLI-scaffolded workspace (created with \`idealyst init\` + \`idealyst create\`), files go in specific locations:
@@ -19855,7 +19869,7 @@ function getThemeTypes2(args = {}) {
   try {
     const result = getThemeTypes(format);
     if (typeof result === "object" && result !== null) {
-      result.useThemeNote = "IMPORTANT: useTheme() returns Theme directly \u2014 NOT wrapped in an object. Correct: `const theme = useTheme();` WRONG: `const { theme } = useTheme();` (causes TS2339). Then use inline styles: `style={{ padding: theme.spacing.md, backgroundColor: theme.colors.surface.primary }}`";
+      result.useThemeNote = 'IMPORTANT: useTheme() returns Theme directly \u2014 NOT wrapped in an object. Correct: `const theme = useTheme();` WRONG: `const { theme } = useTheme();` (causes TS2339). Theme top-level keys: intents, radii, shadows, colors, sizes, interaction, breakpoints. For spacing, use component props (padding="md", gap="md") \u2014 NOT theme.spacing (does NOT exist). For colors: `style={{ backgroundColor: theme.colors.surface.primary }}`. For radii: `style={{ borderRadius: theme.radii.md }}`. For intents: `theme.intents.primary` (NOT theme.colors.intent).';
     }
     return jsonResponse(result);
   } catch (error) {