Skip to main content
Glama
stitch-mcp-stdio

stitch-mcp-stdio

stitch-mcp-stdio

Stable stdio MCP server for Google Stitch AI UI design tool.

Drop-in replacement for @_davideast/stitch-mcp that eliminates the proxy layer crash (libuv UV_HANDLE_CLOSING assertion failure on Windows and intermittent connection drops on other platforms).

Why this exists

The official @_davideast/stitch-mcp package runs a proxy subprocess that suffers from a libuv bug causing random crashes, especially on Windows. This package uses the same @google/stitch-sdk under the hood but connects via stdio transport directly -- no proxy process, no crash.

Related MCP server: Stitch MCP

Setup

1. Get a Stitch API key

Go to stitch.withgoogle.com -> Profile -> Settings -> API Key.

2. Configure your MCP client

Point any MCP-compatible client (Claude Code, Claude Desktop, Cursor, Gemini CLI, VS Code) at npx stitch-mcp-stdio:

{
  "mcpServers": {
    "stitch": {
      "command": "npx",
      "args": ["-y", "stitch-mcp-stdio"],
      "env": {
        "STITCH_API_KEY": "your-api-key"
      }
    }
  }
}

npx -y downloads + runs the latest version without a permanent install. To pin a version use stitch-mcp-stdio@1.0.0.

Alternative: local clone (if you'd rather not use npx)

git clone https://github.com/bluedevilcollectibles/stitch-mcp-stdio.git
cd stitch-mcp-stdio
npm install

Then point the client at node /path/to/stitch-mcp-stdio/server.js instead of npx.

Available tools

All 12 tools from the Stitch SDK are exposed:

Tool

Description

create_project

Create a new Stitch project

get_project

Get project details

list_projects

List all projects

list_screens

List screens in a project

get_screen

Get screen details

generate_screen_from_text

Generate a screen from a text prompt

edit_screens

Edit an existing screen

generate_variants

Generate design variants

create_design_system

Create a design system

update_design_system

Update a design system

list_design_systems

List design systems

apply_design_system

Apply a design system to screens

How it works

MCP Client (Claude, Cursor, etc.)
    |
    | stdio (stdin/stdout)
    |
stitch-mcp-stdio (this package)
    |
    | HTTPS (API key auth)
    |
stitch.googleapis.com/mcp

No proxy subprocess. No libuv handle management. Just stdio in, API calls out.

Built by

Blue Devil Collectibles -- makers of LiveSeller Pro, inventory and live selling tools for comic shops, card shops, and collectibles dealers.

We built this MCP server to power our AI design pipeline. If you sell on WhatNot, manage pull lists, or run a brick-and-mortar shop, check out what we're building.

License

MIT

Available Tools

16 tools
apply_design_systemA
Destructive

Applies a design system to a list of screens. Use this tool when the user wants to update one or more screens to match the style of a design system. This tool applies the selected design system's foundational design tokens (colors, fonts, shapes, etc.) to the chosen screens, modifying their appearance to align with the design system.

Inputs: assetId (required), projectId (required), selectedScreenInstances (required). Returns: The output design generated by the agent.

create_design_systemA
Destructive

Creates a new design system for a project. Use this tool when the user wants to set or update the overall visual theme, style, or branding of the application. This includes configuring:

  • Color Palette: Presets, custom primary colors, and saturation levels.

  • Typography: Font families (e.g., Inter, Roboto, etc.).

  • Shape: Corner roundness for UI elements.

  • Appearance: Light and dark mode background colors.

  • Design MD: Free-form design instructions in markdown. This tool establishes the foundational design tokens that apply across all screens in the project.

Instructions for Tool Call:

  • Call update_design_system tool immediately after this tool to apply the design system to the project, and display the design system in the UI.

Inputs: designSystem (required), projectId. Returns: An Asset resource.

create_design_system_from_design_mdA
Destructive

Creates a design system for a project, with user uploaded DESIGN.md file, and displays the design system in the UI.

Instructions for Tool Call:

  • Should call upload_design_md tool first to upload DESIGN.md to a Stitch project.

Inputs: projectId (required), selectedScreenInstance (required), deviceType. Returns: Response message for CreateDesignSystemFromDesignMd.

create_projectA
Destructive

Creates a new Stitch project. A project is a container for UI designs and frontend code.

Inputs: title. Returns: A project is a single app.

delete_projectA
Destructive

Deletes a specific Stitch project using its project name.

Instructions for Tool Call:

  • This action cannot be undone. Please confirm with "yes" or "no" to proceed.

Inputs: name (required). Returns: Response message for DeleteProject.

download_assetsC

Download screens and assets to a local directory

Inputs: outputDir (required), projectId (required).

edit_screensA
Destructive

Edits existing screens within a project using a text prompt.

Instructions for Tool Call:

  • This action can take a few minutes to complete. Please be patient. DO NOT RETRY.

  • If the tool call fails due to connection error, the process may still succeed.

Inputs: prompt (required), projectId (required), selectedScreenIds (required), modelId, +1 more. Returns: The output design generated by the agent.

generate_screen_from_textA
Destructive

Generates a new screen within a project from a text prompt.

Instructions for Tool Call:

  • This action can take a few minutes to complete. Please be patient. DO NOT RETRY.

  • If the tool fails with a timeout, don't retry. Instead, try to get the screen with get_screen method every 30 seconds for up to 10 times before giving up.

  • If the tool call fails due to connection error, the generation process may still succeed. Please try to get the screen with get_screen method later.

Output:

  • output_components: If output_components contains text, return it to the user. If output_components contains suggestions (e.g. "Yes, make them all"), present these suggestions to the user. If the user accepts one of the suggestions, call generate_screen_from_text again with prompt set to the accepted suggestion.

Inputs: prompt (required), projectId (required), modelId, deviceType, +1 more. Returns: Response message for GenerateScreenFromText.

generate_variantsA
Destructive

Generates variants of existing screens within a project using a text prompt.

Instructions for Tool Call:

  • If the tool fails with a timeout, don't retry. Instead, try to get the screen with get_screen method every 30 seconds for up to 10 times before giving up.

Inputs: prompt (required), projectId (required), variantOptions (required), selectedScreenIds (required), +2 more. Returns: The output design generated by the agent.

get_projectA
Read-only

Retrieves the details of a specific Stitch project using its project name.

Inputs: name (required). Returns: A project is a single app.

get_screenA
Read-only

Retrieves the details of a specific screen within a project.

Inputs: name (required). Returns: A screen generated by the agent.

list_design_systemsA
Read-only

Lists all design systems for a given project.

Inputs: projectId. Returns: Response message for ListDesignSystems.

list_projectsA
Read-only

Lists all Stitch projects accessible to the user. By default, it lists projects owned by the user.

Inputs: filter. Returns: Response message for ListProjects.

list_screensA
Read-only

Lists all screens within a given Stitch project.

Inputs: projectId (required). Returns: Response message for ListScreens.

update_design_systemA
Destructive

Updates a design system for a project. Use this tool when the user wants to change the overall visual theme, style, or branding of the application. This includes configuring:

  • Color Palette: Presets, custom primary colors, and saturation levels.

  • Typography: Font families (e.g., Inter, Roboto, etc.).

  • Shape: Corner roundness for UI elements.

  • Appearance: Light and dark mode background colors.

  • Design MD: Free-form design instructions in markdown. This tool establishes the foundational design tokens that apply across all screens in the project.

Inputs: name (required), projectId (required), designSystem (required). Returns: An Asset resource.

upload_design_mdA
Destructive

Uploads DESIGN.md to a Stitch project. Use this tool when the user wants to create a design system from a DESIGN.md file.

Instructions for Tool Call:

  • Call create_design_system_from_design_md tool immediately after this tool to create the design system from the uploaded DESIGN.md, and display the design system in the UI.

Inputs: projectId (required), designMdBase64 (required). Returns: An instance of a screen on the project. Next ID: 18

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools target distinct resources and actions (projects, screens, design systems, assets), making selection relatively straightforward. However, create_design_system and create_design_system_from_design_md overlap in purpose, and edit_screens vs generate_variants could be confused since both modify existing screens.

    Naming Consistency5/5

    Tool names consistently follow a verb_noun pattern (create_project, get_screen, list_design_systems, apply_design_system, etc.). Even longer names like create_design_system_from_design_md and generate_screen_from_text follow the same predictable structure.

    Tool Count4/5

    At 16 tools, the server is slightly large but still well-scoped across four coherent areas: projects, screens, design systems, and assets. A few tools could be consolidated (e.g., upload_design_md and create_design_system_from_design_md are tightly coupled), but the count is reasonable for the domain.

    Completeness4/5

    The core workflows are covered: project CRUD, screen listing/retrieval/generation/editing, and design system create/update/list/apply. Minor gaps include no delete for screens or design systems and no project update tool, but these are workable and not likely to cause major agent failures.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An automated MCP server for Google Stitch that enables AI-driven UI design generation, accessibility audits, and design system management. It streamlines workflows for creating responsive screens, extracting design tokens, and maintaining visual consistency across professional web projects.
      44 npm
      31
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      A universal MCP server for Google Stitch that enables AI-powered UI/UX design generation by extracting design context and metadata from existing screens. It allows users to fetch screen code and images to create consistent, styled UI components across multiple projects.
      1,160 npm
      122
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that exposes Google Stitch's AI-powered UI design capabilities as local tools. It enables project management, screen generation/editing, and design system operations by forwarding requests to Google's Stitch API.
      2
      -
    • A
      license
      A
      quality
      D
      maintenance
      An intelligent MCP server for Google Stitch that generates production-ready UI from text prompts, with auto-orchestration of design systems, WCAG accessibility, responsive breakpoints, and framework conversion (React, Vue, Svelte).
      17
      14 npm
      9
      MIT