> ## Documentation Index
> Fetch the complete documentation index at: https://docs.webstorio.com/llms.txt
> Use this file to discover all available pages before exploring further.

# CLI, MCP, and SDK

> How the Webstorio CLI, MCP server, and client SDK fit together — page code, project data, and runtime.

Developers typically use three surfaces. They solve different jobs:

| Surface                                       | Works on                                | Best for                                                                             |
| --------------------------------------------- | --------------------------------------- | ------------------------------------------------------------------------------------ |
| **[CLI](/developer/how-cli-works)**           | Local `.tsx` files                      | Building and editing page code, then `webstorio push` / publish                      |
| **[MCP](/developer/connect-mcp)**             | Your live Webstorio project             | Reading project context and managing CMS, forms, store, and App Data via an AI agent |
| **[Client SDK](/api-reference/sdk/overview)** | 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](/guides/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](/developer/schemas).
* **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

1. Scaffold and ship pages with the [CLI tutorial](/developer/your-first-site).
2. Optionally [connect MCP](/developer/connect-mcp) so an agent can manage content and other features.
3. In page code, call the [Client SDK](/api-reference/sdk/overview) for live data.
4. Look up exact options in [References](/api-reference/introduction).