Often it can produce the same project result, but it does not reproduce every click or session state. File tabs, panel selection, expansion, zoom, and similar navigation remain UI concerns; some machine inspection and batch operations are MCP-only; several workflows have only partial MCP coverage.
Use the UI-to-MCP capability map.
Yes. Both routes can change the same project model. Work in small scopes: read current state, make one bounded change, verify it, then review the affected file in the editor before beginning the next change.
Follow the combined-work pattern.
Select the project first and prefer a structured project/file/element reference copied from the editor. Names and paths can be ambiguous after moves or duplicates; reread the target immediately before a write when other people or agents may be editing.
Target files and elements safely.
Review the target's current content, Preview, diagnostics, and generated output as appropriate. Desktop read/write marks remain until explicitly cleared and help locate recent MCP activity, but they are session-only indicators—not authorship, proof, or a durable audit log.
Usually for supported selected-file content changes. MCP undo and redo use the same design-file history model as the editor and move one history step at a time. They do not roll back file creation/deletion, export destinations, Git, publication, invitations, or other external actions.
Evidence appropriate to the result: a read-back for data, Preview or screenshot for appearance, behavior checks for interaction, diagnostics for model/export issues, and the consumer build for shipped code. A successful tool response proves only that the call returned.
Stop and reread the target before retrying. Some operations can report warnings, skipped targets, or partial results; repeated blind writes can compound the problem. Check undo history, Preview, diagnostics, and any external destination affected by the call.
The packaged desktop application provides the production MCP server connection. Operations that ask the app to render, preview, capture, or export also require its connected runtime. The browser editor does not independently replace that packaged MCP connection.
Not through the current production capability described here. Collaboration invitations, the complete sync/history UI, Git push, package publication, and hosted website publication are separate account or external workflows and must not be inferred from content-authoring tools.