← ClaudeAtlas

upload-to-stitchlisted

Upload local assets (images, mockups, extracted HTML, design markdown) to a Stitch project. Use this skill when you need to upload visual assets, HTML pages, or design docs to Stitch, particularly when direct MCP tool calls fail or truncate due to base64 token limits.
coachpo/plugins-claude · ★ 0 · Data & Documents · score 68
Install: claude install-skill coachpo/plugins-claude
# Upload-to-Stitch Upload local assets (images, mockups, HTML, and markdown files) to a Stitch project using the provided upload script, which bypasses the MCP tool's base64 output token limits. > [!NOTE] > The AI model cannot upload files via MCP tools directly because the base64 > encoding of even a small file exceeds the model's output token limit (~16K > tokens). This script reads the file and sends it directly over HTTP. ## Steps ### 1. Identify Target Project Use `list_projects` to find the correct `projectId`. ### 2. Get the API Key Locate the Stitch MCP server configuration and extract the API key. In Claude Code, check in order: - `claude mcp get stitch` (via Bash) — shows the server config and where it is defined - Project config: `.mcp.json` in the project root - User config: `~/.claude.json` (top-level `mcpServers` or the current project's entry) Extract: - **API Key**: From the `X-Goog-Api-Key` header or auth argument - **MCP URL** (optional): From the `httpUrl` or endpoint argument (defaults to `https://stitch.googleapis.com`) > [!IMPORTANT] > If you cannot find the API key in any of these locations, or if you cannot access these files, you MUST ask the user to provide the Stitch API key. Do not proceed without a valid API key. ### 3. Run Upload Script > [!WARNING] > **Checkpoint — User Confirmation Required.** > Before running the upload script, you **MUST** pause and present the file(s) > to be uploaded (paths, sizes, and types) to the user and wa