mcp-stitch 0.1.4 → 0.1.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +45 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# mcp-stitch
|
|
2
2
|
|
|
3
|
-
MCP server for Google Stitch. It
|
|
3
|
+
MCP server for Google Stitch. It lets agents generate and retrieve Stitch screens, then export them into local, versioned implementation bundles with HTML, screenshots, linked assets, prompts, source metadata, and build guidance.
|
|
4
4
|
|
|
5
5
|
## Contents
|
|
6
6
|
|
|
@@ -9,6 +9,7 @@ MCP server for Google Stitch. It exposes Stitch project, screen, design-system,
|
|
|
9
9
|
- [Requirements](#requirements)
|
|
10
10
|
- [Install](#install)
|
|
11
11
|
- [Environment](#environment)
|
|
12
|
+
- [Agent Prompts](#agent-prompts)
|
|
12
13
|
- [VS Code Setup](#vs-code-setup)
|
|
13
14
|
- [Cursor Setup](#cursor-setup)
|
|
14
15
|
- [Continue Setup](#continue-setup)
|
|
@@ -70,6 +71,49 @@ Optional:
|
|
|
70
71
|
- `STITCH_TIMEOUT_MS`: defaults to `180000`
|
|
71
72
|
- `STITCH_MAX_RETRIES`: defaults to `2`
|
|
72
73
|
|
|
74
|
+
## Agent Prompts
|
|
75
|
+
|
|
76
|
+
Use prompts like these after your MCP client is configured.
|
|
77
|
+
|
|
78
|
+
Create a new Stitch screen and export a local build bundle:
|
|
79
|
+
|
|
80
|
+
```text
|
|
81
|
+
Use mcp-stitch to create a desktop Stitch screen for a guest comments page.
|
|
82
|
+
After it finishes, export the screen into a local artifact bundle with HTML, screenshot, linked assets, and rewritten local asset URLs.
|
|
83
|
+
Use artifactPath ".artifacts/stitch/guest-comments" and versioned true.
|
|
84
|
+
```
|
|
85
|
+
|
|
86
|
+
Export assets from an existing Stitch screen:
|
|
87
|
+
|
|
88
|
+
```text
|
|
89
|
+
Use mcp-stitch to export screen {screenId} from project {projectId}.
|
|
90
|
+
Save it to ".artifacts/stitch/{screen-name}" with versioned true.
|
|
91
|
+
Include the HTML, screenshot, linked assets, and rewrite the HTML asset URLs to local files.
|
|
92
|
+
```
|
|
93
|
+
|
|
94
|
+
Find an existing screen first, then export it:
|
|
95
|
+
|
|
96
|
+
```text
|
|
97
|
+
Use mcp-stitch to list screens in project {projectId}.
|
|
98
|
+
Find the screen whose title includes "{title or keyword}".
|
|
99
|
+
Then export that screen as a local build bundle with includeLinkedAssets true, rewriteHtmlAssetUrls true, and versioned true.
|
|
100
|
+
```
|
|
101
|
+
|
|
102
|
+
Direct tool arguments for the export step:
|
|
103
|
+
|
|
104
|
+
```json
|
|
105
|
+
{
|
|
106
|
+
"projectId": "projects-or-bare-project-id",
|
|
107
|
+
"screenId": "screen-id-or-title-fragment",
|
|
108
|
+
"artifactPath": ".artifacts/stitch/guest-comments",
|
|
109
|
+
"versioned": true,
|
|
110
|
+
"includeHtml": true,
|
|
111
|
+
"includeScreenshot": true,
|
|
112
|
+
"includeLinkedAssets": true,
|
|
113
|
+
"rewriteHtmlAssetUrls": true
|
|
114
|
+
}
|
|
115
|
+
```
|
|
116
|
+
|
|
73
117
|
## VS Code Setup
|
|
74
118
|
|
|
75
119
|
VS Code can load MCP servers from a workspace `.vscode/mcp.json` file or from your user MCP configuration.
|