Skip to main content
Publish local static output to StepFun Page with the steppage plugin, get preview links, and manage versions. The plugin connects through the steppage-mcp MCP server to provide deployment, site queries, version management, promotion, and rollback. It accepts a local directory or ZIP for static hosting, not application backends or databases.

Prerequisites

Install inside Step Code:
The official installer is https://dl.stepfun.com/steppage-mcp/p/install.sh, overridable with STEPCODE_STEPPAGE_INSTALLER_URL. To run it manually:
For Bash / Zsh environment-based credentials:
Replace the placeholder with your key and restart after changing environment variables. See Static hosting CLI and MCP for standalone usage. See Plugins for plugin installation and management. See MCP for MCP connections and authentication.

Deployment

Deployment uploads artifacts to an external hosting service. Public links may be accessed and shared by others. Review content and permissions before publishing.
  1. Build your frontend into static output, such as dist/.
  2. Check entry pages, asset paths, and output contents. Exclude keys, private configuration, and user data.
  3. Tell Step Code which directory to publish and whether it should go live.
  4. Check the returned preview URL, version, and management link. Open the page in a browser and verify its assets.
The model uses page_deploy to publish a directory or ZIP as a site version. Results automatically include the management link. Provide a precise site identifier when updating an existing site. See Common use cases for other project task examples.

Versions and rollback

  • Each deployment creates a version; list sites and versions as needed.
  • promote makes a version live; rollback returns to a specified version.
  • Verify site and version identifiers before acting, then revisit the page.
  • Confirm the target before deleting a site or version; this action may be irreversible.
Example:

Management

Use site management for sites, versions, and publication status. Hosting allowances, access rules, and limits are governed by the static hosting documentation and your account, not by Step Plan model allowances.