agentsclimarketplace

Stitch mcp get project

Skill gabelul/stitch-kit/skills/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.From its SKILL.md

Install
npx -y skills add gabelul/stitch-kit --skill stitch-mcp-get-project

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

7.6 KB, ~2.1k tokens by cl100k_base, as published. Nobody here has run it

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 projectId AND screenId. In that case, call 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 get_project
3780309359108792857 (numeric)projects/3780309359108792857
projects/3780309359108792857projects/3780309359108792857 (use as-is)
https://stitch.withgoogle.com/projects/3780309359108792857Extract ID → projects/3780309359108792857

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": "DESKTOP",
  "visibility": "PRIVATE",
  "projectType": "TEXT_TO_UI",
  "origin": "STITCH",
  "metadata": {
    "isRemixed": false,
    "userRole": "OWNER"
  },
  "designTheme": {
    "colorMode": "LIGHT",
    "customColor": "#6366F1",
    "colorVariant": "TONAL_SPOT",
    "roundness": "ROUND_TWELVE",
    "saturation": 3,
    "spacingScale": 1,
    "headlineFont": "INTER",
    "bodyFont": "INTER",
    "labelFont": "INTER",
    "font": "INTER",
    "headlineFontFamily": "Inter",
    "bodyFontFamily": "Inter",
    "labelFontFamily": "Inter",
    "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"
    }
  ]
}

designMd is truncated above — in practice it's a full auto-generated design system doc (often 500+ lines). namedColors typically contains 40+ semantic tokens; only the most common are shown here.

DesignTheme field reference

FieldTypeValues / Notes
colorModeenumLIGHT, DARK
customColorstringHex seed color (e.g. #6366F1). This is the color seed — NOT called primaryColor
colorVariantenumMONOCHROME, NEUTRAL, TONAL_SPOT, VIBRANT, EXPRESSIVE, FIDELITY, CONTENT, RAINBOW, FRUIT_SALAD
roundnessenumROUND_FOUR, ROUND_EIGHT, ROUND_TWELVE, ROUND_FULL
spacingScalenumber0–3 (density multiplier)
headlineFontenum68-font set: INTER, GEIST, DM_SANS, MANROPE, PLUS_JAKARTA_SANS, WORK_SANS, SPACE_GROTESK, SORA, OUTFIT, RALEWAY, QUICKSAND, MONTSERRAT, OSWALD, PLAYFAIR_DISPLAY, MERRIWEATHER, NOTO_SERIF, EB_GARAMOND, LITERATA, SOURCE_SERIF_4, SOURCE_SANS_3, NUNITO_SANS, JETBRAINS_MONO, BEBAS_NEUE, ANTON, ARCHIVO_NARROW — see stitch-ued-guide for the full 68-value list
bodyFontenumSame 68-font set
labelFontenumSame 68-font set
fontenumDeprecated — legacy single-font field, same enum
namedColorsobject40+ semantic color tokens (primary, on_primary, surface, surface_container, outline, error, etc.)
overridePrimaryColorstringHex override, empty string if unused
overrideSecondaryColorstringHex override, empty string if unused
overrideTertiaryColorstringHex override, empty string if unused
overrideNeutralColorstringHex override, empty string if unused
backgroundLightstringHex background for light mode
backgroundDarkstringHex background for dark mode
descriptionstringBrief aesthetic description of the theme
designMdstringAuto-generated design system markdown — the full token spec. Can be very long
spacingobjectOptional. Map of spacing token name → CSS value (e.g. {"sm": "8px"})
typographyobjectOptional. Map of typography level name (e.g. h1, body) → Typography token (fontFamily, fontSize, fontWeight, letterSpacing, lineHeight, all optional strings)

Project-level fields

FieldTypeValues / Notes
deviceTypestringMOBILE, DESKTOP, TABLET, AGNOSTIC, or DEVICE_TYPE_UNSPECIFIED
visibilityenumPRIVATE, PUBLIC
projectTypeenumTEXT_TO_UI, PROJECT_DESIGN, etc.
originenumSTITCH, IMPORTED_FROM_GALILEO
metadata.isRemixedbooleanWhether this project was remixed from another
metadata.userRolestringOWNER, VIEWER, etc.

ScreenInstance fields

FieldTypeNotes
idstringNumeric screen ID
sourceScreenstringPath reference to the source screen
typeenumSCREEN_INSTANCE, DESIGN_SYSTEM_INSTANCE, GROUP_INSTANCE
width / heightnumberPixel dimensions
x / ynumberCanvas position
hiddenbooleanWhether hidden in the project
sourceAssetstringPresent on DESIGN_SYSTEM_INSTANCE 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 designTheme — use it to keep new screens visually consistent
  • Note the screenInstances list — extract screenId values if you need to inspect specific screens
  • Use stitch-mcp-list-screens for a richer view of the screen list including thumbnails

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most mcp tooling skills give in ~2.1k tokens

Counted across 780 of the 1,136 authors here whose files we hold, read 2026-09-06

  • Use Zod for input validationin 34 of 780, across 21 files
  • Use stdio for local clientsin 27 of 780, across 10 files
  • Restart Claude Code after configurationin 26 of 780, across 23 files
  • Verify MCP server connection before using toolsin 23 of 780, across 17 files
  • Define input schemas for every toolin 20 of 780, across 11 files
  • Use Streamable HTTP for remote clientsin 18 of 780, across 8 files
  • Pin SDK version in package.jsonin 17 of 780, across 6 files
  • Keep server logic independent of transportin 16 of 780, across 6 files
  • Verify SDK methods against official documentationin 15 of 780, across 5 files
  • Format evaluation results as an XML filein 15 of 780, across 12 files
  • Test servers using the MCP Inspectorin 15 of 780, across 14 files
  • Create ten complex and independent evaluation questionsin 14 of 780, across 11 files

Said here and by no other author read

  • extract project ID to projects/ID format
  • call get_project with the formatted project ID
  • use designTheme to maintain visual consistency
  • use designMd and namedColors when generating new screens
  • inspect screenInstances to identify specific screen IDs

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.