CLI, MCP, and SDK - Webstorio

Developers typically use three surfaces. They solve different jobs:

Surface	Works on	Best for
CLI	Local `.tsx` files	Building and editing page code, then `webstorio push` / publish
MCP	Your live Webstorio project	Reading project context and managing CMS, forms, store, and App Data via an AI agent
Client SDK	Published (and preview) page JavaScript	`window.webstorio` calls for CMS, forms, store, auth, and App Data in the browser

Page code vs project data

Page code (layout, components, routes) — built with the CLI or the dashboard. See Dashboard vs CLI.
Project data (CMS types/entries, forms, store products, App Data tables/rows) — managed in the dashboard or via MCP. Feature schemas can also be versioned with the CLI.
Runtime API — page code calls the SDK (or same-origin fetch) on the live site.

MCP does not publish sites or rewrite page modules. The CLI does not replace the dashboard/MCP for day-to-day content and data management.

Typical developer flow

Scaffold and ship pages with the CLI tutorial.
Optionally connect MCP so an agent can manage content and other features.
In page code, call the Client SDK for live data.
Look up exact options in References.

Project structure Local development