Skip to content
Jervis Stitch MCP
PRIVATE MCP INTEGRATION · GOOGLE STITCH

From conversation to real UI design.

Create and refine real Google Stitch screens from ChatGPT and compatible MCP clients. Your keys stay server-side. You approve the changes.

Private beta · Public listing pending
Example workflow
Active MCP Session
U

CLIENT PROMPT

Create a desktop landing screen for our project with clear sections and clean spacing.

shield_lock Action: stitch_generate_screen | Target: project_alpha
Always ask

Requires confirmation before creating screen backend

check Allow once
preview Landing · Revision 1
Preview
Hero
Grid
Footer
sync_saved_locally

FOLLOW-UP REVISION

project: alpha

Refine the hero card to show an updated layout.

construction

8 focused tools

4 read tools · 4 write tools

hub

2 MCP transports

stdio · local Streamable HTTP

translate

Arabic + English

Prompt-level direction across languages

contrast

Light + Dark

Design prompts for light & dark palettes

INTEGRATION CAPABILITIES

Direct integration for modern model workflows.

Built specifically for the Model Context Protocol to bridge natural-language briefs with Google Stitch.

verified

Official Google Stitch SDK

Built directly on the official SDK and backend provider, creating authentic Stitch artifacts.

Target: Official Stitch API
draw

Create, generate, refine

Start new projects, orchestrate initial high-fidelity screens, and request iterative revisions directly from chat.

Flow: Project to screen iterations
sync_alt

Project and screen IDs

Tools return explicit project and screen identifiers. Edits may generate a new screen revision.

Tracking: Project and screen ID references
lock

Server-side keys & private tunnel

Runs inside your owner-scoped private tunnel with server-side keys. No credential exposure to client chat prompts.

Boundary: Owner-scoped tunnel
approval_delegation

Always ask & duplicate protection

Enforces confirmation before write actions, with duplicate and unknown-write safeguards.

Policy: Human-in-the-loop approval
restart_alt

Windows sign-in startup

Windows sign-in startup with durable new-project edit access.

Platform: Windows scheduled task
WORKFLOW

4-step workflow

A clear lifecycle from client connection to finalized screen designs.

01

Connect private tunnel

Pair your MCP host via standard stdio or local Streamable HTTP to your private tunnel.

02

Choose or create your project

Read existing workspace projects or initialize a new dedicated project container.

03

Approve generation or edit

Review the prompt and approve each write action before the tool mutates design assets.

04

Review returned screen links

Inspect generated layouts, preview returned screen links, and iterate with follow-up prompts.

Compact 8-Tool MCP Catalog

Exposed over standard JSON-RPC 2.0. All tools require user confirmation in current setup.

schema JSON-RPC 2.0
READ TOOLS (4 tools) Always ask enforced

stitch_list_projects

Query available user projects in workspace

Always ask

stitch_get_project

Retrieve project details, screen count, and configuration

Always ask

stitch_list_screens

List screens and current revisions within a project

Always ask

stitch_get_screen

Inspect screen layout structure and design properties

Always ask
WRITE TOOLS (4 tools) Always ask enforced

stitch_create_project

Initialize a new project container

confirm

stitch_generate_screen

Generate an initial screen layout from a user brief

confirm

stitch_edit_screen

Apply revisions to existing components or layout

confirm

stitch_generate_variants

Beta · live acceptance pending

Explore alternative layout or style directions

confirm
security SECURITY & CONTROL

Your designs. Your credentials. Your approval.

Built with defense-in-depth principles for secure AI model environments.

key

Keys remain server-side

API credentials and provider bearer tokens stay server-side and never appear in client chat prompts.

folder_managed

Existing projects protected

Safe write mode prevents unintended mutation of pre-existing designs. Only verified newly initialized projects are editable.

sync_problem

No blind retries

If a call returns an unknown result, the owner/agent reads and reconciles state before further writes rather than blindly retrying.

lan

No unauthenticated public endpoint

Scoped strictly to authenticated MCP tunnels and local host. No publicly reachable unauthenticated ingress ports or open webhooks.

Brief in your language. Design in your mode.

Direct prompt-level control across languages and color modes without prompt drift.

EN Light (Default)
Primary Action

Clean blue & slate canvas

EN Dark
Primary Action

High-contrast deep slate (Active)

العربية (نهاري)
تأكيد العملية

Cairo RTL typography

العربية (ليلي)
تأكيد العملية

Arabic dark design direction

policy

Private integration today. Public access requires user authentication and review.

This integration currently operates as a self-hosted Model Context Protocol bridge for private use. The official Google Stitch MCP is documented as free under standard provider quotas and usage terms. There is no paid tier, gateway surcharge, or payment flow. A separate multi-user OAuth service is implemented and locally tested. Public account acceptance and hosting are pending; public listing has not been submitted.

· Standard Google provider terms apply · No gateway surcharge · Free community integration

Frequently asked questions

Does this recreate Google Stitch?

No. Jervis connects compatible MCP clients to Google’s official Stitch provider and returns real project, screen and artifact identifiers.

Can it change my old projects?

The safe write mode protects pre-existing projects. Only verified new projects created through this integration are enrolled for editing.

Can I install it from the public directory today?

The owner’s private integration is verified. The separate OAuth service is locally tested; public hosting, account acceptance and OpenAI review must pass before public installation is available.

What if a call times out?

Do not repeat a write. Read the exact project and screens first. A design may have been saved even when the chat reports a timeout; unknown operations remain blocked until reviewed.

Is usage free?

There is no Jervis payment flow or paid fallback in this integration. Google’s current quotas and terms apply. Access is not unlimited; stop when a quota or payment requirement is encountered.

Do edits keep the same screen ID?

An edit may produce a new revision with a new screen ID. Use the exact latest identifier returned by the provider. Variants still require separate live acceptance.