stitch-mcp-list-screens
Scannednpx machina-cli add skill gabelul/stitch-kit/stitch-mcp-list-screens --openclawStitch MCP — List Screens
Lists all screens contained within a specific Stitch project. You typically call this right after generate_screen_from_text to find the screenId of the screen that was just created.
Critical prerequisite
Only use this skill when the user explicitly mentions "Stitch".
When to use
- Immediately after
generate_screen_from_text— to find the new screen's ID - User wants to browse all screens in a project
- You need a
screenIdto callget_screen - Checking what screens already exist before generating a new one
Call the MCP tool
Important: Use the projects/ID format — not the numeric ID alone.
{
"name": "list_screens",
"arguments": {
"projectId": "projects/3780309359108792857"
}
}
✅ "projects/3780309359108792857"
❌ "3780309359108792857"
Output schema
{
"screens": [
{
"name": "projects/3780309359108792857/screens/88805abc123def456",
"title": "Login Screen",
"screenshot": {
"downloadUrl": "https://storage.googleapis.com/..."
},
"deviceType": "MOBILE"
}
]
}
After listing
- Identify the target screen (usually the most recently generated — last in the list)
- Extract the numeric
screenIdfrom thenamefield:"projects/3780309359108792857/screens/88805abc123def456"→ screenId ="88805abc123def456"
- Call
stitch-mcp-get-screenwith the numericprojectIdandscreenId
ID format reminder
For the next call (get_screen), you need the numeric IDs for both project and screen:
projectId→3780309359108792857(stripprojects/prefix)screenId→88805abc123def456(stripprojects/.../screens/prefix)
Source
git clone https://github.com/gabelul/stitch-kit/blob/main/skills/stitch-mcp-list-screens/SKILL.mdView on GitHub Overview
Lists all screens contained within a Stitch project. It’s useful after generate_screen_from_text to locate the screenId of the newly created screen and then retrieve it with stitch-mcp-get-screen.
How This Skill Works
Sends a list request for a given project using a projectId in the projects/ID format. The response returns screen entries you can inspect to identify the target screen and extract its numeric screenId for subsequent get-screen calls.
When to Use It
- Immediately after generate_screen_from_text — to find the new screen's ID
- When you want to browse all screens in a Stitch project
- When you need a screenId to call stitch-mcp-get-screen
- When checking what screens already exist before generating a new one
- When validating screen presence or maintaining a screen inventory
Quick Start
- Step 1: Call stitch-mcp-list-screens with {"projectId": "projects/3780309359108792857"}
- Step 2: Inspect the screens array and identify the target screen (usually the last item)
- Step 3: Extract the numeric screenId from the name (e.g., .../screens/88805abc123def456) and call stitch-mcp-get-screen with the numeric IDs
Best Practices
- Always use the projectId in the projects/ID format for MCP calls
- Identify the target screen as the most recently added one (often the last item)
- Extract the numeric screenId from the name field (after /screens/)
- Use the numeric IDs for downstream calls like get-screen
- Verify the returned screen data (title, screenshot) matches expectations
Example Use Cases
- After generating a screen from text, list_screens to fetch its screenId for retrieval
- Browse all screens in a project to audit names and titles
- Retrieve a specific screen by calling stitch-mcp-get-screen with the projectId and screenId
- Validate a newly created screen's presence in the list before proceeding
- Perform maintenance by confirming IDs for a batch retrieve
