StaticX MCP Server

Official Model Context Protocol server for StaticX, the deployment infrastructure for static websites.

Give Claude Code, Cursor, Codex, Cline, Windsurf, Claude Desktop, Zed, Continue, or another MCP client a scoped StaticX API token. The agent can then create sites, upload files, publish releases, inspect logs, start manual custom domain setup, and roll back with explicit confirmation when deployment history is enabled.

StaticX intentionally uses scoped API tokens instead of OAuth because it is designed for developers, CI/CD, automation tools, and AI agents.

Install

The package runs directly through npx; a global install is not required.

{
  "mcpServers": {
    "staticx": {
      "command": "npx",
      "args": ["-y", "staticx-mcp-server"],
      "env": {
        "STATICX_API_TOKEN": "sx_replace_with_your_token",
        "STATICX_API_BASE_URL": "https://staticx.site/api/v1"
      }
    }
  }
}

Create the narrowest token that fits the job. A short-lived, site-scoped token is the safest default for one-site deployments.

Full client-specific snippets are available in the StaticX MCP documentation.

Related MCP server: Hostsmith MCP Server

Claude Code

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

Codex

codex mcp add staticx \
  --env STATICX_API_TOKEN=sx_replace_with_your_token \
  --env STATICX_API_BASE_URL=https://staticx.site/api/v1 \
  -- npx -y staticx-mcp-server

Local HTTP debugging

STATICX_API_TOKEN=sx_replace_with_your_token npx staticx-mcp-server http

Then connect a Streamable HTTP client or the MCP Inspector to:

http://localhost:3100/mcp

HTTP mode listens on 127.0.0.1 by default. Do not expose it publicly without a secure reverse proxy and a deliberate authentication policy.

Environment variables

Never paste a real token into documentation, source control, screenshots, prompts, or issue reports.

Plan limits

MCP tools use the public StaticX API and cannot bypass account capacity.

If a tool returns PLAN_QUOTA_EXCEEDED, stop and return the exact message to the user. Do not retry blindly, change endpoints, or bypass StaticX Forms.

Tools

Safety contract

• Tokens are never returned by a tool.

• Write tools explain their effect in their descriptions.

• Rollback requires ROLLBACK <deployment_id>.

• Deployment deletion requires DELETE <deployment_id>.

• The server only calls the public StaticX /api/v1 contract.

• Use a site-scoped token for one-site agents and revoke it when the task is complete.

• Plan limits are enforced by the API and hosted forms runtime. Tools must stop on PLAN_QUOTA_EXCEEDED.

• ZIP uploads are queued by the StaticX API. staticx_upload_zip and staticx_deploy_zip wait for import completion before reporting success or publishing.

• Sites default to versioned deployment history. If the user asks to avoid release history, pass versioning_enabled: false to staticx_create_project, staticx_deploy_project, or staticx_deploy_zip; StaticX keeps one baseline release for analytics, forms, and live serving.

• DNS Connect requires browser approval in the StaticX dashboard. MCP tools should return manual DNS records or tell the user to approve DNS Connect; they must not claim to authorize an external DNS provider silently.

• Generated subdomain suffix changes are dashboard-only. If an account has an active publishing domain, use Site → Settings → Domain to save a generated address on that suffix.

Recommended agent prompt

Use StaticX MCP to deploy this static website.

Before deploying:
- build the project
- verify index.html and 404.html exist at the build root
- explain what you will publish

After deploying:
- return the live URL, release, and deployment mode
- inspect logs if anything fails
- stop on PLAN_QUOTA_EXCEEDED and show the exact quota message
- if I ask to disable version history, create or deploy with versioning_enabled=false
- if the user asks to move a generated subdomain to a publishing domain, direct them to Site Settings → Domain
- do not roll back or delete anything without asking me first

Development

git clone https://github.com/madprodworks-coder/staticx-mcp-server.git
cd staticx-mcp-server
npm install
npm test

The MCP package must continue to use the public StaticX API. It must not import Laravel controllers, services, or internal engine classes.

Security

Please report vulnerabilities privately as described in SECURITY.md. Do not open a public issue containing tokens, private URLs, or customer data.

License

MIT