Google Stitch MCP server
16 tools · Last check that passed 27 Oct 2026, 01:50 UTC
Google's own remote MCP server for Stitch gives an agent the projects, screens and design systems of the Stitch account its API key or sign-in reaches, and generates new screens. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 16 tools
| Tool | Counted as |
|---|---|
apply_design_system | Deletes |
create_design_system | Deletes |
create_design_system_from_design_md | Deletes |
create_project | Deletes |
delete_project | Deletes |
edit_screens | Deletes |
generate_screen_from_text | Deletes |
generate_variants | Deletes |
update_design_system | Deletes |
upload_design_md | Deletes |
download_file | Said to only read |
get_project | Said to only read |
get_screen | Said to only read |
list_design_systems | Said to only read |
list_projects | Said to only read |
list_screens | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
12 of the last 12 checks passed
A check passes when the server lists its tools. Checked at https://stitch.googleapis.com/mcp.
Recent changes
21 Oct 2026, 09:36 UTC, after a check on 20 Oct 2026, 09:45 UTC
1 tool added: download_file. Inputs or outputs changed on create_project, get_project, list_projects.
From the scan of 27 Oct 2026, 01:52 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when Google Stitch's tools change.
One email when Google Stitch's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- A Stitch API key, created in Stitch settings, lets the agent list and read the account's projects. Google's Stitch MCP codelab
- Its tools can create projects and generate screens from a text prompt. Google Labs' Stitch SDK README
- Generated screens and their HTML come back to the agent, and text an agent reads can carry instructions for it. OWASP, prompt injection
How to limit it
With Google Stitch's own settings, as its documentation describes them. Stackduke has not tested them.
- Copy the API key when it is created and store it securely, as Google's codelab advises. Google's Stitch MCP codelab
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.