@google/stitch-sdk — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor this implementation for changes in adoption, MCP interface, maintenance and permission boundary.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Generate interface screens via Google Stitch SDK

What we know

Generate UI screens from text prompts and extract their HTML and screenshots programmatically. Generate interface screens via Google Stitch SDK.

Maintenance / activity evidence

npm downloads 172978 in 2026-09-08..2026-10-07

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation. Reported action classes: generate design assets. Complete write authority is not verified.
Developer project credentials and SDK installation
Design prompts, generated HTML and screenshots

SDK, not necessarily an independent MCP Server; do not imply direct installation into an MCP client.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 173k package downloads / 30 days

Downloads observed Oct 9, 2026.

Exact npm package @google/stitch-sdk; provider interval 2026-09-08–2026-10-07 (inclusive); observed 2026-10-09.

All limitations / Review context

Has @google/stitch-sdk changed its specific MCP integration, install method or privilege scope, and does it justify shortlist promotion?

High-impact permissions explicitly documented; no known blocker to an accurately caveated public Radar listing in limited first-party review.

SDK, not necessarily an independent MCP Server; do not imply direct installation into an MCP client.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Developer project credentials and SDK installation
Design prompts, generated HTML and screenshots
Reviewed write actions: generate design assets
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No exhaustive advisory or runtime review performed; never infer installation safety.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
npm package downloads explicitly observed

Original activity observations

npm downloads 172978 in 2026-09-08..2026-10-07

Technical identity

npm/@google/stitch-sdk

Exact implementation source: https://www.npmjs.com/package/@google/stitch-sdk ↗
Reviewed resource type: SDK
Package identity: npm:@google/stitch-sdk

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Package registry ↗
@google/stitch-sdk
Recorded package identity, distribution or download evidence.

Setup · Watchlist

SDK setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install SDK / application integration
Publisher instructions
Developer library/integration. Install in an application; not a plug-and-play MCP Server. Review publisher README. Not a standalone local MCP server; application integration required.
publisher documented install or connect · Publisher instructions
npm install @google/stitch-sdk
Configure / authenticate
MCP100 setup guide
Install @google/stitch-sdk as a Node/TypeScript application dependency. Set STITCH_API_KEY (or STITCH_ACCESS_TOKEN and GOOGLE_CLOUD_PROJECT for OAuth); use SDK StitchToolClient with published endpoint https://stitch.googleapis.com/mcp. Do not treat the SDK package as an stdio MCP executable.
Check connection
Suggested check
SDK: initialize Stitch client with STITCH_API_KEY or OAuth access token/project ID and validate local initialization. Avoid screen generation as a smoke test. SDK/plugin validation means app import/initialization or feature availability, not an MCP client tools/list test unless the consuming app actually exposes a server.
Remove / uninstall / revoke
MCP100 setup guide
Google Stitch SDK is a client-side library. Remove project dependency using `npm uninstall @google/stitch-sdk`; remove its imports and local STITCH_API_KEY references. SDK removal does not delete Stitch projects or revoke credentials.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate credential guidance / limitations: @google/stitch-sdk is a library. It does not issue MCP credentials: STITCH_API_KEY belongs to Google Cloud API keys, where Google documents deleting a key. If using STITCH_ACCESS_TOKEN OAuth instead, revoke it with the Google identity issuer; the SDK has no own revocation.
Package / application cleanup · matching installation environment · MCP100 composed guide
npm uninstall @google/stitch-sdk

Official Documentation & Sources

What it does

Generate UI screens from text prompts and extract their HTML and screenshots programmatically. Generate interface screens via Google Stitch SDK.

Capability: Design & Creative
Resource type: SDK
Best fit: Generate interface screens via Google Stitch SDK

Representative uses

Generate screen layouts from prompts
Retrieve generated HTML and screenshots
Iterate visual screen variants
Generate interface screens via Google Stitch SDK

Limitations

SDK, not necessarily an independent MCP Server; do not imply direct installation into an MCP client.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
npm package downloads explicitly observed

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Developer project credentials and SDK installation
Permissions: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Data handling: Design prompts, generated HTML and screenshots
Cost: may incur external API or infrastructure charges; unverified
Risk and cautions: SDK, not necessarily an independent MCP Server; do not imply direct installation into an MCP client.

Access scope and cautions

Write actions: Not verified generate design assets
Risk level: moderate
Security notes: SDK, not necessarily an independent MCP Server; do not imply direct installation into an MCP client.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-09. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Generate screen layouts from prompts; Retrieve generated HTML and screenshots; Iterate visual screen variants; Generate interface screens via Google Stitch SDK.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Command provided only where first-party command or package existence is established; verify the client configuration against upstream documentation. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Developer project credentials and SDK installation

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: generate design assets. Recorded permission context: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.

What data-handling boundary should I consider?

Design prompts, generated HTML and screenshots

What limitations and risks should I check before use?

SDK, not necessarily an independent MCP Server; do not imply direct installation into an MCP client. Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation. npm package downloads explicitly observed. No exhaustive advisory or runtime review performed; never infer installation safety.