Skip to main content
Webstorio exposes a remote Model Context Protocol (MCP) server at:
Auth is OAuth (PKCE) with dynamic client registration. First connect opens a browser sign-in and consent screen. For a guided setup, see Connect MCP. For how MCP relates to the CLI and SDK, see CLI, MCP, and SDK.
Alpha — tools and behavior may change. Paid plan (Starter+) required; Free accounts receive 403. Share feedback at [email protected].

​
Requirements

  • Paid plan (Starter or higher)
  • OAuth sign-in when the MCP client connects
  • Enabled project features where applicable; mutating tools enforce plan limits (entry counts, products, App Data rows, etc.)

​
Security

  • OAuth-only with PKCE and a per-client consent screen on first connect
  • Every tool checks project membership; mutating services apply the same plan and feature gates as the dashboard
  • Every MCP request is authenticated with a Bearer token (stateless Streamable HTTP)
  • Rate limits: ~120 requests / minute / user, plus an IP cap before auth

​
Tools

​
Project & pages (read)

​
Content & CMS

​
Form & Survey

​
Online Store

​
App Data (Growth+)

Table schema (schemaJson field defs) and API settings (settingsJson) are managed with the table tools above, in the dashboard App Data UI, or as versioned JSON via the CLI feature schemas. MCP does not publish sites or rewrite page code — use the CLI for that.