Stitch MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STITCH_API_KEY | Yes | Your Stitch 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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_projectB | Create a new Stitch project |
| list_projectsA | List all available Stitch projects |
| generate_screenB | Generate a UI screen from a text prompt within a project |
| edit_screenB | Edit an existing screen using a text prompt |
| generate_variantsB | Generate design variants of an existing screen |
| get_screen_codeA | Retrieve the HTML code download URL (and extract full HTML if possible) for a generated screen |
| get_screen_imageA | Retrieve the base64 screenshot image download URL for a generated screen. |
| generate_and_fetch_codeA | One-step tool to generate a UI screen and immediately retrieve its HTML code |
| scaffold_project_filesB | Maps a specific screen from a project to a local file path. Use this to save UI designs directly into the user's workspace. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create_web_app |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| projects |
TDQS
Scored across 9 tools
Most tools have distinct purposes (list vs create, generate vs edit vs variants, code vs image retrieval). However, `generate_and_fetch_code` overlaps with the combination of `generate_screen` and `get_screen_code`, creating minor ambiguity about which to use for a one-step workflow.
All tool names consistently follow a snake_case verb_noun pattern. Verbs are clear and specific (list, create, generate, edit, get, scaffold). Even the compound `generate_and_fetch_code` follows the same style, making the naming predictable.
Nine tools is well-scoped for the Stitch UI generation domain. Each tool covers a distinct step in the workflow without unnecessary redundancy, and the count feels appropriate for the server's purpose.
Core lifecycle is covered: project creation, screen generation/editing/variants, and retrieval of code and images. However, there is no explicit way to list or delete screens, and no project update/delete endpoints, which are minor gaps for a complete surface.