When should I use stitch-mcp-get-project vs stitch-mcp-get-screen?

Use stitch-mcp-get-project when you need full project metadata (title, theme, create/update times, screen list) to inform broader screen generation. Use stitch-mcp-get-screen when you already have a specific screenId and only need data for that screen.

What data does the get_project output include?

The output includes name, title, createTime, updateTime, designTheme (colorMode and primaryColor), and screenInstances (a list of screen references).

How should I use the designTheme from the project?

Use colorMode and primaryColor from designTheme to ensure new screens visually match the project's existing theme and branding.

stitch-mcp-get-project

npx machina-cli add skill gabelul/stitch-kit/stitch-mcp-get-project --openclaw

Files (1)

SKILL.md

2.2 KB

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/3780309359108792857`	`projects/3780309359108792857` (use as-is)
`https://stitch.withgoogle.com/projects/3780309359108792857`	Extract 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",
  "designTheme": {
    "colorMode": "LIGHT",
    "primaryColor": "#6366F1"
  },
  "screenInstances": [
    { "name": "projects/3780309359108792857/screens/88805..." }
  ]
}

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

Source

git clone https://github.com/gabelul/stitch-kit/blob/main/skills/stitch-mcp-get-project/SKILL.mdView on GitHub

Overview

Stitch MCP — Get Project retrieves full metadata for a Stitch project, including title, createTime, updateTime, and the designTheme. Use it to understand an existing project's theme and screen list before generating new screens. Do not use this if you already have a screenId; use stitch-mcp-get-screen instead.

How This Skill Works

Normalize the user-provided project reference to the standard projects/ID format, then call the MCP tool with name get_project and the argument name set to that project path. The tool returns a schema with fields like name, title, createTime, updateTime, designTheme, and screenInstances, which you review to plan new screens and maintain visual consistency.

When to Use It

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
You want to inspect the list of screen instances and extract screen IDs for targeted review
The project reference may arrive in multiple formats and needs normalization to projects/ID

Quick Start

Step 1: Obtain the Stitch project reference (URL or ID) and normalize it to projects/ID
Step 2: Call stitch-mcp-get-project with { name: 'projects/ID' }
Step 3: Review the returned metadata (title, createTime, updateTime, designTheme, screenInstances) to plan next steps

Best Practices

Only invoke this skill when the user explicitly mentions Stitch
Normalize any provided project reference to the projects/ID format before the call
Do not call this if you already have both projectId and screenId; use stitch-mcp-get-screen instead
Review designTheme (colorMode and primaryColor) to maintain visual consistency for new screens
Use screenInstances to extract screenIds if you need to inspect or audit specific screens

Example Use Cases

A designer shares a Stitch project URL; you fetch the project metadata to align new dashboard screens with the existing theme
Before generating new screens, you retrieve the project's title and theme to ensure naming and styling match
You verify the project exists and note createTime and updateTime to confirm activity
You extract screenIds from screenInstances to selectively review particular screens
You compare the designTheme's colorMode and primaryColor with your planned screens to keep visuals cohesive

Frequently Asked Questions

Add this skill to your agents