Staticbot

What is Staticbot?

Staticbot is an MCP server for the Staticbot platform that lets AI agents (Claude Code, Cursor, any MCP-compatible runtime) orchestrate deployment workflows via the Staticbot API. Staticbot itself is a managed operations platform for complex, long-running deployment workflows—it hosts static websites and web apps inside your own AWS account using S3 and CloudFront, with no vendor lock-in.

How to use Staticbot?

Prerequisites: a Staticbot account, an API key (generated at Settings → API Keys in the Staticbot UI), and Node.js 18+. Add the server to your MCP client configuration (e.g., .mcp.json) with command npx -y staticbot-mcp and environment variable STATICBOT_API_KEY. Optionally set STATICBOT_API_URL to override the default http://localhost:9000.

Key features of Staticbot

• Deploy static sites and web apps to AWS via S3 + CloudFront
• Orchestrate full Supabase project migrations to own AWS infrastructure
• Manage multi‑stage deployments (dev, preview, production)
• Provide tools for listing, getting, confirming, and resuming migrations
• Create infrastructure stacks from templates with custom domains
• Return immediate status URLs for human oversight and agent polling

Use cases of Staticbot

• Deploy a static website to AWS with a custom domain and automatic SSL
• Migrate a Lovable project from Supabase to your own AWS account (database, edge functions, storage, auth)
• Manage independent lifecycle of dev, preview, and production stages per website
• Let an AI agent handle orchestration while Staticbot manages state, credentials, and approval gates

FAQ from Staticbot

Is Staticbot a CI/CD platform?

No. Staticbot does not replace GitHub Actions or deployment pipelines; it is a managed operations platform for specific, opinionated deployment playbooks.

What are the runtime requirements?

Node.js 18+ and a Staticbot account with an API key. No additional dependencies beyond those needed for MCP‑compatible clients.

Where does my deployment data live?

All deployments run inside your own AWS account using S3 and CloudFront. Staticbot orchestrates the workflow but the infrastructure and data remain in your control.

How does an agent orchestrate a deployment?

The agent calls a tool (e.g., create_stack), receives an ID and a statusUrl deep‑link to the Staticbot UI, shares that link with the human, and then polls the status until completion. When human action is needed (e.g., DNS setup), the agent tells the human what to do and waits.

What transports and authentication does the server use?

The server runs via npx and communicates over stdio with the MCP client. Authentication is provided by the STATICBOT_API_KEY environment variable.