Loading ToolBench
Google Stitch MCP server + CLI: export UI designs to React, Vue, Svelte, Next.js and 5+ frameworks, with auto-config for Cursor, Claude Code, OpenCode, Antigravity, Zed and VS Code.
Server has 13 tools with explicit schemas and descriptions. Naming follows verb_noun convention (list_, generate_, sync_, export_, create_, upload_, apply_, cache_). Descriptions are present (avg ~120 chars) but lack LLM-optimized guidance on WHEN to use each tool vs alternatives. Schemas are well-structured with enums and type constraints, but output schemas are not documented. Error handling is minimal, no recovery guidance or actionable error messages. Missing idempotency hints on write operations. Tool composition is reasonable but some tools combine multiple concerns (e.g., stitch_upload_image handles both PNG/JPG and HTML with different semantics).
Apply a design system to selected screen instances in a Stitch project.
Clear all cached data.
Get the status of the local cache for offline access.
Sync a project to the local cache for offline access.
Create a design system for a Stitch project with theme configuration, design tokens, and style guidelines.
Create a new Google Stitch project.
Output schemas not documented. Tools return data but LLMs cannot plan downstream calls without knowing response structure. E.g., stitch_list_projects returns projects but response fields are undocumented.
Error handling lacks recovery guidance. No actionable error messages or categorization (retryable vs user-fixable vs fatal). E.g., 'StitchError' is caught but LLM receives no hint on next steps.
Descriptions lack WHEN-to-use guidance. E.g., stitch_sync_screen vs stitch_export_framework both export designs but distinction is unclear. LLMs cannot disambiguate without explicit guidance.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2025-06-18+ | v2 |
Export Stitch screens to code in various frameworks (React, Vue, Svelte, Next.js, Nuxt, Solid, Angular, Vanilla).
Generate a new screen from a design prompt using Google Stitch AI generation capabilities.
List all design systems in a Stitch project.
List all Google Stitch projects accessible with the configured credentials. Supports filtering by search term and offline mode.
Sync screen designs to local files in HTML format.
Update an existing design system in a Stitch project.
Upload an image or HTML file to a Stitch project to create screens.
stitch_upload_image combines multiple concerns: PNG/JPG image upload vs HTML file upload have different semantics and success criteria. Should split into separate tools.
Destructive operations (stitch_cache_clear) lack confirmation/dry-run pattern. No guard against accidental cache wipe. Description is minimal (50 chars).