webstudio 0.284.0 → 0.285.0

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 CHANGED
@@ -70,7 +70,30 @@ Here is the list of independent commands:
70
70
 
71
71
  The **`link`** command stores access to a Webstudio Cloud project. MCP clients use that connection to read and edit the latest Builder build directly; the project does not need to be published or synchronized first.
72
72
 
73
- Shell-capable agents can use local CLI commands such as `webstudio meta.index` immediately after linking. `webstudio connect <client>` is optional persistent native MCP registration and is unnecessary for local CLI usage.
73
+ Shell-capable agents can call MCP tools directly as CLI subcommands immediately after linking. This does not require MCP client configuration or a client restart:
74
+
75
+ ```bash
76
+ webstudio meta.index
77
+ webstudio components.search '{"brief":"button"}'
78
+ webstudio insert-fragment --input-file .temp/insert-fragment.json --dry-run
79
+ ```
80
+
81
+ `.temp/insert-fragment.json`:
82
+
83
+ ```json
84
+ {
85
+ "parentInstanceId": "<parent-id>",
86
+ "fragment": "<ws.element ws:tag='section' />"
87
+ }
88
+ ```
89
+
90
+ The explicit equivalent is `webstudio mcp single-op-call <tool> '<json>'`.
91
+ Use `webstudio connect <client>` only when you want persistent native MCP tools
92
+ inside Claude Code, Codex, Cursor, or VS Code. A persistent client may need to
93
+ reconnect after its configuration or cached tool catalog changes.
94
+
95
+ See the [Webstudio MCP documentation](https://docs.webstudio.is/university/mcp)
96
+ for setup, discovery, editing, verification, and safety guidance.
74
97
 
75
98
  You can link a project from Webstudio Cloud with the following command:
76
99