Skip to main content
Glama
bluedevilcollectibles

stitch-mcp-stdio

by bluedevilcollectibles
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
STITCH_API_KEYYesYour Stitch API key. Get it from stitch.withgoogle.com -> Profile -> Settings -> API Key.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_projectA

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

get_projectA

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

delete_projectA

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.

list_projectsA

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

list_screensA

Lists all screens within a given Stitch project.

get_screenA

Retrieves the details of a specific screen within a project.

generate_screen_from_textA

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.

edit_screensA

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.

generate_variantsA

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.

upload_design_mdA

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.

create_design_systemA

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.

create_design_system_from_design_mdA

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.

update_design_systemA

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.

list_design_systemsA

Lists all design systems for a given project.

apply_design_systemA

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.

download_assetsC

Download screens and assets to a local directory

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

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
ResponsivenessNo issues

Resources