Stitch-kit stitch-mcp-get-project
Retrieves metadata for a specific Stitch project — title, theme, create/update time. Use to inspect a project before generating new screens. Do NOT use this if you already have a screenId — use stitch-mcp-get-screen instead.
install
source · Clone the upstream repo
git clone https://github.com/gabelul/stitch-kit
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/gabelul/stitch-kit "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/stitch-mcp-get-project" ~/.claude/skills/gabelul-stitch-kit-stitch-mcp-get-project && rm -rf "$T"
manifest:
skills/stitch-mcp-get-project/SKILL.mdsource content
Stitch MCP — Get Project
Retrieves full metadata for a specific Stitch project. Useful for understanding an existing project's theme and screen list before generating additional screens.
Critical prerequisite
Only use this skill when the user explicitly mentions "Stitch".
Do NOT call this if you already have both
AND projectId
. In that case, call screenId
stitch-mcp-get-screen directly — it's more efficient.
When to use
- User provides a Stitch project URL and you need its details
- You need to know the existing design theme before generating new consistent screens
- Verifying a project exists before proceeding
Step 1: Parse the project ID from context
The user may provide the project reference in several formats — always extract to the
projects/ID format:
| Input format | → Argument for |
|---|---|
(numeric) | |
| (use as-is) |
| Extract ID → |
Step 2: Call the MCP tool
{ "name": "get_project", "arguments": { "name": "projects/3780309359108792857" } }
Output schema
{ "name": "projects/3780309359108792857", "title": "Analytics Dashboard", "createTime": "2024-11-10T09:00:00Z", "updateTime": "2024-11-15T10:30:00Z", "deviceType": "PHONE", "visibility": "PRIVATE", "projectType": "TEXT_TO_UI", "origin": "STITCH", "metadata": { "isRemixed": false, "userRole": "OWNER" }, "designTheme": { "colorMode": "LIGHT", "customColor": "#6366F1", "colorVariant": "TONAL_SPOT", "roundness": "ROUND_TWELVE", "spacingScale": 1, "headlineFont": "ROBOTO", "bodyFont": "ROBOTO", "labelFont": "ROBOTO", "font": "ROBOTO", "namedColors": { "primary": "#5B5FC7", "on_primary": "#FFFFFF", "primary_container": "#E1DFFF", "on_primary_container": "#414594", "secondary": "#5C5D72", "on_secondary": "#FFFFFF", "tertiary": "#785572", "on_tertiary": "#FFFFFF", "surface": "#FBF8FF", "on_surface": "#1B1B21", "surface_container": "#EFEDF5", "surface_container_low": "#F5F2FA", "surface_container_high": "#E9E7EF", "outline": "#777680", "error": "#BA1A1A", "on_error": "#FFFFFF" }, "overridePrimaryColor": "", "overrideSecondaryColor": "", "overrideTertiaryColor": "", "overrideNeutralColor": "", "backgroundLight": "#FBF8FF", "backgroundDark": "#131316", "description": "Modern indigo-toned interface with clean surfaces", "designMd": "# Design System\n\n## Color Palette\n..." }, "screenInstances": [ { "name": "projects/3780309359108792857/screens/88805...", "id": "88805...", "sourceScreen": "screens/88805...", "type": "SCREEN_INSTANCE", "width": 412, "height": 892, "x": 0, "y": 0, "hidden": false }, { "name": "projects/3780309359108792857/screens/99901...", "id": "99901...", "sourceScreen": "screens/99901...", "type": "DESIGN_SYSTEM_INSTANCE", "width": 412, "height": 892, "x": 500, "y": 0, "hidden": false, "sourceAsset": "assets/design-system-123" } ] }
is truncated above — in practice it's a full auto-generated design system doc (often 500+ lines).designMdtypically contains 40+ semantic tokens; only the most common are shown here.namedColors
DesignTheme field reference
| Field | Type | Values / Notes |
|---|---|---|
| enum | , |
| string | Hex seed color (e.g. ). This is the color seed — NOT called |
| enum | , , , , , , , , |
| enum | , , , |
| number | – (density multiplier) |
| enum | 28-font set: , , , , , , , , , , , , , , , , , , , , , , , , , , , |
| enum | Same 28-font set |
| enum | Same 28-font set |
| enum | Deprecated — legacy single-font field, same enum |
| object | 40+ semantic color tokens (, , , , , , etc.) |
| string | Hex override, empty string if unused |
| string | Hex override, empty string if unused |
| string | Hex override, empty string if unused |
| string | Hex override, empty string if unused |
| string | Hex background for light mode |
| string | Hex background for dark mode |
| string | Brief aesthetic description of the theme |
| string | Auto-generated design system markdown — the full token spec. Can be very long |
Project-level fields
| Field | Type | Values / Notes |
|---|---|---|
| string | , , , etc. |
| enum | , |
| enum | , , etc. |
| enum | , |
| boolean | Whether this project was remixed from another |
| string | , , etc. |
ScreenInstance fields
| Field | Type | Notes |
|---|---|---|
| string | Numeric screen ID |
| string | Path reference to the source screen |
| enum | , , |
/ | number | Pixel dimensions |
/ | number | Canvas position |
| boolean | Whether hidden in the project |
| string | Present on types — references the design system asset |
Using the theme data
Use
designMd and namedColors when generating new screens — they contain the authoritative design system for this project. Pass namedColors to stitch-design-system for instant token extraction.
After getting the project
- Note the
— use it to keep new screens visually consistentdesignTheme - Note the
list — extract screenId values if you need to inspect specific screensscreenInstances - Use
for a richer view of the screen list including thumbnailsstitch-mcp-list-screens