Static Studio CLI for AI agents
Let your AI agent manage
Static WordPress
Give Claude Code, Codex, Cursor, or your terminal a scriptable way to create sites, import WordPress backups, push static updates, manage domains, restore backups, inspect logs, and run performance reports in Static Studio.
Works with interactive OTP login codes during the trial period.
Use Personal Access Tokens for CI and agent workflows on paid plans.
Setup Prompt
Ready to automate the entire process with our AI-friendly Command Line Interface?
Copy this into your AI agent
Already working in Claude Code, Codex, Cursor, or another AI coding tool? Give your agent a safe starting point for Static Studio.
You are helping me manage a Static Studio site using the Static Studio CLI.
First, install and inspect the CLI:
npm install -g @simply-static/static-studio
static-studio --help
Authentication rules:
- Do not ask me to paste secrets into chat.
- If I use email OTP login, wait for me to complete the login step.
- If I use a Personal Access Token, read it from STATIC_STUDIO_ACCESS_TOKEN.
- Never print tokens, config files, or secret values.
- Prefer --json when you need structured output.
Start by running:
static-studio status
static-studio sites list
Then ask me which site I want to work on before making changes.Authentication is limited to OTP on trial accounts.
For permanent authentication, consider signing up for a paid plan and creating a personal access token.
Watch Static Studio run from AI
Install the CLI, authenticate, create or import a WordPress site, trigger a static deployment, inspect logs, connect a domain, and hand the workflow back to your AI agent.
AI can write code.
WordPress still needs a real place to run.
AI coding tools are changing how websites get built.
They can generate layouts, refactor templates, update content, write scripts, review logs, and automate repetitive work.
But WordPress still creates a problem for AI-native workflows.
The dashboard is visual. Hosting is fragmented. Deployments involve too many one-off clicks. Domains, redirects, backups, staging, logs, and performance checks are stored in different locations.
That is where Static Studio CLI comes in.
It gives your AI agent a narrow, scriptable interface to the Static Studio platform, so your workflow can stay in the terminal while Studio handles the WordPress and static hosting infrastructure.
The AI-native way to manage Static WordPress
Make Static WordPress easy by letting the AI agent handle it, while still getting the benefits of our rock-solid platform.
Your AI agent works in the terminal
Claude Code, Codex, Cursor, or your local shell can install the CLI, inspect available commands, and run structured workflows.
Static Studio handles the platform
Studio manages WordPress hosting, static site hosting, SSL, backups, forms, performance optimization, and migration.
Visitors get the
fast static site
Your public site is served as static output, while WordPress stays available as the editing and management environment.
Give your agent Studio actions
Your AI agent knows what to do; just tell it.
Workflow
Example copy
Create sites
Create a new Static WordPress site from the terminal.
Import WordPress backups
Upload a migration file and let Studio restore it.
Push static updates
Trigger full or changed-page static deployments.
Manage domains
Add, remove, and set primary domains.
Handle redirects
Create, update, enable, disable, or bulk-create redirects.
Invite users
Add editors, administrators, clients, and teammates
Run performance checks
Trigger and inspect Studio performance reports.
Debug issues
Tail debug logs and error logs without opening the dashboard.
Manage backups
Create, list, refresh, and restore backups.
Work with environments
Create and manage staging environments.
Agent workflows you can run
Practical examples for your AI-first workflows
with Static Studio.
Create a new Static WordPress site
Create a new Static Studio site called “Launch Demo,” then show me the site ID and current status.
static-studio sites create --name "Launch Demo" --subdomain launch-demo
static-studio sites list --jsonImport an existing WordPress site
Import this Studio backup, wait for the migration status, then show me the next recommended action.
static-studio sites create --name "Imported Site" --migration-file ./site-studio-backup.zip
static-studio sites list --jsonPublish changes
Push the latest changes for this site and summarize whether the deployment succeeded.
static-studio sites push <siteId> changes
static-studio sites get <siteId>Add redirects after a migration
Create redirects from this JSON file [file-path], then list disabled redirects for review.
static-studio sites create --name "Imported Site" --migration-file ./site-studio-backup.zip
static-studio sites list --jsonDebug a failed deployment
Tail the last 200 log lines, filter for errors, and tell me what to check next.
static-studio sites debug-log <siteId> --tail 200
static-studio logs get <siteId> --tail 200 --level errorRun a performance check
Run a fresh performance report and summarize the result for a client.
static-studio performance run <siteId> --force
static-studio performance reports <siteId>AI agents need boring infrastructure
AI workflows are exciting. Production hosting should not be.
Static Studio gives your agent a predictable target: managed WordPress for editing, static hosting for visitors, backups, SSL, domains, redirects, performance reports, and operational commands through one CLI.
Scriptable
Run Studio workflows from a terminal, an AI agent, local scripts, or CI.
Static-first
Publish the public site as static output instead of making every visitor request depend on dynamic WordPress.
WordPress-compatible
Keep the WordPress workflow, page builders, SEO setup, forms where supported, and the existing content model.
Production-minded
Use backups, logs, domains, redirects, users, performance reports, and more without stitching together five tools.
Built for agents, without treating secrets casually
Static Studio CLI supports interactive email OTP login for local workflows and token-based login for CI or agent workflows. Tokens should be stored as environment variables, not pasted into chats or committed to repositories.
Do
Don’t
Use environment variables for tokens.
Paste access tokens directly into AI chats.
Use separate profiles for each client or account.
Let an agent delete or restore sites without explicit confirmation.
Ask your agent to prefer --json for structured output.
Commit CLI config files to a repository.
Review destructive commands such as delete, restore, or redeploy.
Reference files without checking the file path.
Who is it for?
Built for the next wave of WordPress sites – generated via AI, human-curated, highly performant, and secure.
For AI builders
Spin up real WordPress-backed sites from your coding workflow instead of stopping at a prototype.
For agencies
Let agents help with setup, migration, redirects, domains, performance checks, and maintenance workflows.
For WordPress developers
Keep WordPress, but make operational tasks scriptable and scalable – backups, SSH, WP-CLI – all you need is available.
For technical marketers
Use AI to help publish, test, redirect, and optimize campaign sites without waiting on dashboard work.
Frequently asked
Simply Static is not about abandoning WordPress. It is about using WordPress where it is strongest and removing it where it creates risk, cost, and complexity.
Is this an MCP server?
No, this is not an MCP server – it’s a CLI.
While we won’t say there won’t be an MCP server in the future, the CLI delivers much better performance in all our tests with Claude, Codex, and Cursor – it’s simply way more efficient compared to an MCP.
Which AI agents does it work with?
Our CLI works with any agent and model you like. We’ve done some extensive testing with Claude Code, Cursor, and Codex – as long as it can install NPM packages and run shell commands, you’re good to go.
Do I need a Static Studio account?
Yes. The CLI controls Static Studio workflows, so users need a Studio account. Interactive OTP login is available for local use; Personal Access Tokens are intended for CI and agent workflows on paid subscriptions.
Can the CLI create and deploy sites?
Yes. The command reference includes site listing, site creation, migration-file imports, full and changed static pushes, redeploys, and deletion.
Can it manage domains, redirects, backups, and users?
Yes, you can manage domains, backups, redirects, users, teams, performance reports, logs, environments, tags, and SSH keys.
Is this only for developers?
The CLI is technical, but the target user is broader: anyone using an AI agent or terminal workflow to manage websites.
Does this replace the Studio dashboard?
No. It gives humans and agents another way to control Studio. The dashboard remains useful for visual review, billing, account settings, and manual workflows.