> ## 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.

# Developer

> Build Webstorio sites with the CLI, use AI agents on local code or MCP, and call the client SDK on published sites.

This tab is for developers who start with the **CLI**: local React (`.tsx`) files, version control, live preview, and `webstorio push` to deploy — with **zero deployment configuration** (no separate hosting or build pipeline setup).

Prefer the dashboard AI builder instead? Start in [Documentation](/) with [Create your first site](/guides/create-your-site). See [Dashboard vs CLI](/guides/dashboard-vs-cli) for a comparison.

<Note>
  Bring your own editor or AI coding agent — for example Claude Code, Codex,
  Cursor, Antigravity, Zed, Windsurf, Kiro, or any tool that can edit local
  files. A Webstorio site is plain React; see [Use AI agents on local
  files](/developer/ai-agents).
</Note>

<CardGroup cols={2}>
  <Card title="Your first site with the CLI" icon="rocket" href="/developer/your-first-site">
    Scaffold, preview, and publish a site from local files — step by step.
  </Card>

  <Card title="How the CLI works" icon="terminal" href="/developer/how-cli-works">
    Compose-and-push model, zero deploy config, and install.
  </Card>

  <Card title="Project structure" icon="folder-tree" href="/developer/project-structure">
    Config, pages, components, brand, assets, and schemas.
  </Card>

  <Card title="CLI, MCP, and SDK" icon="layers" href="/developer/cli-mcp-sdk">
    Which tool owns page code, project data, and runtime APIs.
  </Card>

  <Card title="Connect MCP" icon="bot" href="/developer/connect-mcp">
    Point an AI agent at your live Webstorio project.
  </Card>

  <Card title="Feature schemas" icon="database" href="/developer/schemas">
    CMS, forms, and App Data as versioned JSON in the repo.
  </Card>

  <Card title="Routing" icon="route" href="/developer/routing">
    Static paths, nested URLs, and dynamic slug wildcards.
  </Card>
</CardGroup>

<Tip>
  MCP **enriches** the developer workflow — it does not replace the CLI for page
  code. Use the CLI (or dashboard) to create and publish pages; use MCP to
  manage CMS, forms, store, and App Data.
</Tip>

## Lookup

When you need exact options and methods, use [References](/api-reference/introduction): [CLI commands](/cli/commands), [configuration](/cli/configuration), [Client SDK](/api-reference/sdk/overview), and [MCP tools](/api-reference/mcp/overview).