stitch-setup

A setup guide for connecting the Stitch-kit plugin and Stitch MCP server to Claude Code or Codex CLI. Google Stitch is a cloud service for generating interface screens from descriptions.

In plain words
What is it for?
It is for setting up Stitch, checking tools such as project and screen generation, diagnosing connection problems, and completing plugin installation.
Why use it?
It helps first-time users install the required pieces, check whether the connection works, configure an API key, and troubleshoot missing Stitch tools.

Skill for Claude CodeCodex

Part of the stitch-kit plugin — 36 skills, 1 agent, 2 hooks shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/gabelul/stitch-kit/stitch-setup
Any agent
npx skills add gabelul/stitch-kit --skill stitch-setup
Clone the repo
git clone --depth 1 https://github.com/gabelul/stitch-kit

Made for: Claude Code, Codex.

Or install stitch-kit, the plugin that ships this one along with the rest of its 36 skills, 1 agent, 2 hooks.

Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,633 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00051 $0.01633
Opus 5 $0.00026 $0.00816
Sonnet 5 $0.00010 $0.00327
Haiku 4.5 $0.00005 $0.00163

Measured 3d ago against content hash 8c7f3294ee36, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

stitch-setup scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

Or add to `~/.claude/settings.json` manually:
skills/stitch-setup/SKILL.md · 232 lines

How it starts

The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.

stitch-kit Setup Guide

Walks users through two setup tasks:

  1. Stitch MCP Server — connect your AI client to Google Stitch's remote generation API
  2. stitch-kit Plugin — install the skills that orchestrate the Stitch workflow

When to use this skill

  • User says "how do I set this up", "it's not working", "Stitch isn't available"
  • Agent can't find Stitch MCP tools after running list_tools
  • First-time setup in a new environment

Step 1: Verify what's already installed

Run list_tools (or check the tool list). Look for any of:

  • create_project
  • generate_screen_from_text
  • get_screen

If found: Stitch MCP is working. Skip to Step 4 (plugin install). If not found: Continue with MCP setup below.


Step 2: Get a Stitch API Key

Stitch MCP is a remote HTTP server — it lives in the cloud at stitch.googleapis.com, not on your machine. It requires an API key to authenticate.

  1. Go to stitch.withgoogle.com/settings
  2. Scroll to the API Keys section
  3. Click "Create API Key"
  4. Copy the key — you'll need it in the next step

Never commit your API key to a public repository. Store it securely.


Step 3: Configure Stitch MCP

Claude Code

Using the CLI (recommended):

claude mcp add stitch --transport http https://stitch.googleapis.com/mcp \
  --header "X-Goog-Api-Key: YOUR-API-KEY" -s user

Or add to ~/.claude/settings.json manually:

{
  "mcpServers": {
    "stitch": {
      "type": "http",
      "url": "https://stitch.googleapis.com/mcp",
      "headers": {
        "X-Goog-Api-Key": "YOUR-API-KEY"
      }
    }
  }
}

Codex CLI

Add to ~/.codex/config.toml:

[mcp_servers.stitch]
url = "https://stitch.googleapis.com/mcp"

[mcp_servers.stitch.headers]
X-Goog-Api-Key = "YOUR-API-KEY"

Cursor

Create or edit .cursor/mcp.json:

{
  "mcpServers": {
    "stitch": {
      "url": "https://stitch.googleapis.com/mcp",
      "headers": {
        "X-Goog-Api-Key": "YOUR-API-KEY"
      }
    }
  }
}

Read the full file on GitHub · 232 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 232 lines · 51 tokens per session scan B 8c7f3294ee36

Subscribe to this mod's changes

stitch-setup is a skill published in the GitHub repository gabelul/stitch-kit (43 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 51 tokens to every session and 1,633 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

karakeep

Official skill for how to use karakeep (the bookmark manager) and interact with it programmatically.

karakeep-app/karakeep · 25 tokens

revenuecat

Integrate RevenueCat for in-app purchases — consumable credit packs or subscriptions. Use when setting up RevenueCat, creating products in App Store Connect / Google Play, configuring the SDK, building a paywall, or handling purchase webhooks in Supabase Edge Functions.

Ampli-Group/agentic-mobile-blueprint · 57 tokens

push-notifications

Set up push notifications for iOS and Android using Expo Notifications and Supabase Edge Functions. Use when adding push notifications, configuring APNs/FCM credentials, sending notifications from the backend, or troubleshooting notification delivery.

Ampli-Group/agentic-mobile-blueprint · 47 tokens

social-auth-setup

Configure Sign in with Apple and Sign in with Google for Supabase Auth. Use when adding social login, troubleshooting OAuth redirects, setting up Apple Services ID, Google OAuth credentials, or linking Google Play Console to Google Cloud.

Ampli-Group/agentic-mobile-blueprint · 49 tokens

stripe-payments

Integrate Stripe payments into the app — products, prices, checkout sessions, webhooks, customer portal, and subscription management. Use when setting up payments from scratch, adding a new product/plan, configuring webhooks, or debugging payment flows.

Ampli-Group/agentic-mobile-blueprint · 53 tokens

apple-appstore-setup

Set up Apple Developer account, App Store Connect app listing, and EAS credentials for iOS builds and TestFlight distribution. Use when creating a new iOS app, configuring Apple certificates/provisioning, or troubleshooting App Store Connect submission issues.

Ampli-Group/agentic-mobile-blueprint · 55 tokens