Stitch · Bridgehead
BridgeheadGoogle Stitch × Claude · ChatGPT
Google Stitch, right in your chat.
Design, see, keep, clone.
Design · Edit · Variants · Design systems · Kept · Suggest · Compare · Clone
Stitch designs app screens from a sentence. Its own MCP server wants your key in a header, or a Google Cloud project with gcloud signed in: claude.ai, ChatGPT, the phone and voice can do neither. And the screens it makes stay inside Stitch, where your chat can't see them. Stitch · Bridge is a connector you add once: sign in, your Stitch key goes into Bridgehead's vault, and Stitch's tools are in every app you work in. Every screen it makes lands in your Bridgehead gallery as a picture and its code, and shows right in the chat. On top: suggestions for any screen, two screens judged side by side, and any UI cloned from a screenshot into an editable Stitch screen.
What it can do
Copy. Paste. Connected.
How to connect it
MCP server
The address to paste into each app, or its one-line command. It's the same connector everywhere.
Claude
claude.ai, the desktop app or the phone: Customize → Connectors → Add → Custom connector, then paste this.
https://stitchbridge.fyi/mcpClaude Code
One line in your terminal.
claude mcp add --transport http stitchbridge https://stitchbridge.fyi/mcpChatGPT
In settings, turn on developer mode and add a custom app with this address.
https://stitchbridge.fyi/mcpCodex
One line in your terminal; it asks you to sign in.
codex mcp add stitchbridge --url https://stitchbridge.fyi/mcpAny other MCP app
Cursor, VS Code, Windsurf, Zed, n8n and more: add this address as a remote MCP server and sign in when asked.
https://stitchbridge.fyi/mcpYour Stitch key
Sign in when your chat asks, then add a key made in Stitch's own settings (API keys). No Google Cloud project. Screens use your Stitch allowance.
Keys it uses: your Google Stitch key; your Gemini key, to describe, critique and clone screens; your OpenAI key, to judge screens; your Jev key, to judge screens. A key already in your Bridgehead vault is used as it is: one tap, nothing to paste twice.
Add your Stitch keyQuestions
What can I do with Stitch · Bridge?
Everything Stitch's own tools do, from any chat: make projects, design screens from a sentence for a phone or the desktop, edit them in words, ask for variants, and set design systems. Every screen lands in your Bridgehead gallery as a picture and its code, and shows in the chat, where the assistant can see it. On top: pull any project's screens into the gallery, have Gemini suggest improvements with the edit that applies them, have Decisions or Jev judge two screens side by side, and clone any UI from a screenshot into an editable Stitch screen.
Why not add Google Stitch's own MCP server?
It wants your Stitch key in a header, or a Google Cloud project with gcloud signed in; claude.ai, ChatGPT, the phone and voice can do neither, and its screens stay inside Stitch. Stitch · Bridge keeps your key, signs your chat in the usual way, and brings every screen back to you.
Do I need a Google Cloud project?
No. Make a key in Stitch's own settings, under API keys, and add it on your key page. That's all.
A screen takes minutes. What happens if my chat stops waiting?
Bridgehead finishes it anyway: the first answer may say it's still being made, and asking again brings the finished screen. It is never made twice, and it lands in your gallery either way.
Is my Stitch key safe?
It's checked with Stitch first, kept encrypted in Bridgehead's vault and used only to call Stitch for you. Remove it at any time at stitchbridge.fyi/key.