stitch-mcp-stdio

create_project

Destructive

Create a new Stitch project to organize your UI designs and frontend code in one container, enabling structured workflow from design to development.

Instructions

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

Input Schema

TableJSON Schema

Name	Required	Description	Default
`title`	No	Optional. The title of the project.

Output Schema

TableJSON Schema

Name	Required	Description
`name`	No	Identifier. The resource name of the project. Format: projects/{project}
`title`	No	Optional. The title of the project.
`origin`	No	Output only. The origin of the project.
`metadata`	No	Metadata of the project.
`readTime`	No	Output only. The time the project was last read. Populated only when listing recently viewed projects.
`createTime`	No	Output only. The time when the project was created.
`deviceType`	No	Optional. The device type of the project.
`updateTime`	No	Output only. The time when the project was last updated.
`visibility`	No	Optional. The visibility setting of the project.
`designTheme`	No	Output only. The theme used to generate the first design in the project.
`projectType`	No	Optional. The type of the project. If not specified, the project is a text to UI project.
`backgroundTheme`	No	Optional. The background theme of the project.
`screenInstances`	No	Output only. The screen instances on this project.
`thumbnailScreenshot`	No	Optional. The screenshot to be used as the thumbnail for the project. Same as normal design screenshots, this contains the FIFE serving_base_url which requires additional FIFE URL options to be set for sizing.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 20, 2026

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, so the agent knows this is a mutating operation. The description adds the context that a project is a container for UI designs and frontend code, which helps set expectations. It does not disclose side effects, permissions, or what happens to existing data, but the annotation covers the destructive nature.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no wasted words. The core action is front-loaded, and the clarifying definition of a project is concise and useful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple creation tool with one optional parameter and an output schema, the description is nearly complete. It explains what a project is, which is the main contextual gap. It does not mention return values, but the output schema exists, so that is not required.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents the 'title' parameter as optional. The description does not add any additional meaning about the parameter beyond what the schema provides, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Creates') and resource ('a new Stitch project'), and adds a clarifying definition of what a project is ('a container for UI designs and frontend code'). It is clear and distinguishes the tool from siblings like create_design_system, though it does not explicitly name any sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for creating a project, and the definition of a project gives some context for when to use it. However, it does not explicitly state when to use this tool versus alternatives like create_design_system or apply_design_system, nor does it mention any prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server