Agent tools

MCP Quick Start

Connect Claude, Cursor, Codex, Cline, Windsurf, Zed, and other agents to StaticX with one scoped API token.

API-token-first MCP

Deploy static websites from any AI agent.

StaticX uses scoped API tokens for MCP because it is built for automation, CI/CD, and AI agents. Create a narrow token, add one config, and let the agent use explicit StaticX tools.

Install

npx

Auth

API token

Clients

Any MCP

01

Create a scoped token

For one site, choose a site token with a short expiry. The token is shown once and can be revoked at any time.

02

Add the MCP server

Paste the config below into your agent. Keep the placeholder in shared files and inject the real token locally.

03

Ask for a safe deploy

Ask the agent to build, verify index.html and 404.html, call staticx_deploy_zip, and return the live URL.

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.

First prompt

Give the agent a clear finish line.

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 and release
- inspect logs if anything fails
- stop on PLAN_QUOTA_EXCEEDED and show the exact quota message
- do not roll back or delete anything without asking me first
Keep secrets out of shared config.

Never commit a real token. Use the placeholder in examples, then store the real value only in your local client configuration or environment.