AI-native release platform

Deploy static sites with your team or your AI agent.

StaticX gives people a visual dashboard and gives AI agents scoped API, CLI, and MCP access to publish immutable releases safely, capture leads, and measure which version converts.

Streamlined capabilities

Everything needed to run static-site releases, team operations, and agent-driven automation.

Hosting & deployment

Create, upload, and publish static sites from one release workflow.

History & rollback

Keep immutable releases and restore a previous version instantly.

Forms & lead inbox

Collect submissions from HTML forms without building a backend.

Version analytics

Compare views, leads, sources, and conversion by deployed release.

Automation API

Use scoped tokens to automate releases safely and predictably.

Team collaboration

Group sites by workspace and keep ownership and access visible.

Powerful CLI

Deploy folders, manage domains, and inspect releases from your terminal.

AI-native agents

Let agents publish through MCP with every action visible in history.

Domain management

Connect custom domains with one DNS record and automatic SSL.

Forms and analytics stay attached to each release.

Static sites should not need a separate backend just to collect leads or understand what changed. StaticX keeps submissions, traffic sources, devices, and conversion quality tied to the deployment version that produced them.

  • Lead inbox for static forms Every HTML form becomes a structured inbox with editable entries and export-ready data.
  • Conversion analytics by version See views, leads, conversion rate, source, country, device, and release lifetime together.
  • Source-aware decisions Know if a release converts better from direct traffic, search, email, or social campaigns.
Olive Orbit Release #24 · active
28.57% conversion
Views
7
Leads
2
Top source
Direct
Direct 2 leads
Email 1 lead
Lead Version Source Device
shcod Release #24 Direct Desktop
tototch Release #22 Email Mobile

Security first

Scoped security controls

Keep global, workspace, and site tokens isolated so each workflow can publish safely without borrowing a broad personal credential.

  • Site-specific tokensRestrict an agent to publishing one site only.
  • Workspace isolationCollaborate across teams without leaking access.
auth_config.json
{
  "token_name": "agent-deploy-primary",
  "scope": "site:olive-orbit",
  "permissions": [
    "publish:immutable",
    "inspect:logs",
    "trigger:rollback"
  ],
  "expires_at": "2026-12-31T23:59:59Z"
}

Operational transparency

Every deployment, rollback, build failure, workspace change, and support event stays visible in one activity stream.

Release #245Published by AI agent via CLI · 2 mins ago
Live now
Release #244Manual deployment by Amina Hart · 1 hour ago
Ready
Live deployment output Release #245
✓ 36 files hashed
✓ 31 existing blobs reused
✓ 5 new blobs uploaded
✓ manifest stored
✓ production pointer updated

olive-orbit.staticx.store is live
Every publish appears as a normal release with logs, rollback, and retention controls.

Open agent infrastructure

Install the official StaticX MCP server from npm.

Use the public package in Claude, Cursor, Codex, Cline, Windsurf, Zed, Continue, and any MCP client that can run a local command or connect to HTTP mode.

Production ready Safety contracted

Install the MCP

Pick your agent, copy the snippet, and paste it into the client configuration. StaticX authenticates with a scoped API token you can expire or revoke at any time.

staticx-mcp-server on GitHub
Claude Code Terminal
claude mcp add staticx --scope user \
  --env STATICX_API_TOKEN=sx_replace_with_your_token \
  --env STATICX_API_BASE_URL=https://staticx.site/api/v1 \
  -- npx -y staticx-mcp-server
Adds StaticX for your user account. Run claude mcp list to verify the connection.

Ready to automate your release pipeline?

Start in the visual dashboard, then connect an AI agent when the workflow is ready to move faster.