--- title: "Static Studio CLI - Let AI manage Static WordPress for you - Simply Static" description: "We’ve released the Static Studio CLI: a command-line interface for Static Studio that lets you manage sites from your terminal, as well as scripts, CI" date: "2026-06-29T10:01:40+02:00" language: "en-US" canonical_url: "https://simplystatic.com/tutorials/static-studio-cli-ai-agents/" source_url: "https://simplystatic.com/tutorials/static-studio-cli-ai-agents/" content_type: "text/markdown" --- # Static Studio CLI – Let AI manage Static WordPress for you 29/06/2026 Welcome to another update for Static Studio – and this one is all about making Static WordPress easier to control from the tools we already use every day. We’ve released the [Static Studio CLI](https://simplystatic.com/simply-static-studio-cli/): a command-line interface for Static Studio that lets you manage sites from your terminal, as well as scripts, CI workflows, and AI coding agents like Claude Code, Codex, and Cursor. That means your AI agent can now create sites, import WordPress backups, trigger static deployments, manage domains, inspect logs, restore backups, run performance checks, and more – while Static Studio handles the actual WordPress and static hosting infrastructure. I’ve also created a little walkthrough video to get you started: ## AI Can Write Code. WordPress Still Needs a Real Place to Run. AI coding tools are getting incredibly good. They can generate layouts, refactor templates, update content, write scripts, review logs, and automate repetitive work. For developers, agencies, and technical marketers, they are quickly becoming part of the daily workflow. But WordPress still creates a gap in that workflow. The dashboard is visual. Hosting is fragmented. Deployments usually involve a mix of dashboards, DNS providers, backup tools, FTP/SFTP, redirects, logs, performance checks, and manual review. That is fine for humans. It is not ideal for agents. If you want an AI agent to help you run real production workflows, it needs a narrow, scriptable, predictable interface. That is exactly why we built the Static Studio CLI. ## What the Static Studio CLI Does The CLI gives your terminal, scripts, and AI agents a safe way to control Static Studio workflows. **You can use it locally, in CI, or inside an AI coding tool that can install NPM packages and run shell commands. A few examples: - Create new Static Studio sites - Import existing WordPress sites from backup files - Trigger full or changed-page static deployments - Manage domains - Create, update, enable, disable, or bulk-create redirects - Invite users and manage access - Run performance checks - Inspect debug logs and error logs - Create, list, refresh, and restore backups - Work with staging environments - Manage tags and SSH keys In short, many of the operational tasks for Static WordPress can now be automated from a single place. - Your AI agent can help with the workflow. - Static Studio handles the platform. - Visitors still get the fast static site. ## The AI-Native Way to Manage Static WordPress Static WordPress has always been a great fit for performance, security, and maintenance. You keep WordPress as the editing environment, but visitors are served a static version of the site. No public database. No public PHP execution. No need to make every visitor request depend on dynamic WordPress. With the CLI, this setup becomes much easier to manage in an AI-first workflow. Your agent can stay in the terminal and ask Static Studio to do the work: ``` npm install -g @simply-static/static-studio static-studio --help static-studio status static-studio sites list ``` From there, the agent can inspect what is available, ask which site to work on, and start running structured workflows. For example: ``` static-studio sites create --name "Launch Demo" --subdomain launch-demo static-studio sites list --json ``` Or: ``` static-studio sites push changes static-studio sites get ``` Or: ``` static-studio performance run --force static-studio performance reports ``` That is the kind of workflow AI agents are good at: structured, repeatable, inspectable actions. ## Built for Claude Code, Codex, Cursor, and Your Terminal The CLI is not tied to one specific AI tool. We’ve tested it with Claude Code, Codex, and Cursor, but the idea is simple: if your agent can install NPM packages and run shell commands, it can work with the Static Studio CLI. You can also use it without AI at all. For developers and agencies, it is just as useful as a normal CLI: - Run commands from your terminal - Add Studio actions to scripts - Use structured JSON output - Automate repetitive maintenance work - Build internal workflows around site creation, deployment, migration, redirects, and reporting The AI part is exciting, but the foundation is intentionally boring: a CLI that exposes real platform actions in a predictable way. That matters because AI workflows are only useful in production if the underlying infrastructure is stable. ## A Safe Starting Point for Agents One of the things we added to the CLI page is a ready-to-copy setup prompt for AI agents. The prompt tells the agent to install and inspect the CLI, check the current Studio status, list sites, and ask which site to work on before making changes. It also includes a few important rules: - Do not ask the user to paste secrets into chat. - Use email OTP login for local trial workflows. - Use Personal Access Tokens for CI and agent workflows on paid plans. - Read tokens from environment variables. - Never print tokens, config files, or secret values. - Prefer `--json` when structured output is needed. - Ask before making destructive changes. That last part is important. We want agents to help with real workflows, but not treat production infrastructure casually. A good AI workflow should speed things up without removing humans from decisions that matter. ## Why a CLI Instead of an MCP Server? A common question will be: Is this an MCP server? No – this is a CLI. We may still explore MCP in the future, but for the workflows we tested, the CLI was faster, simpler, and more reliable with Claude Code, Codex, and Cursor. It also fits how many developers already work. AI coding tools are already comfortable in the terminal. They can install packages, run commands, inspect JSON output, and modify scripts. The CLI gives them something clear and limited to operate against. Instead of giving an agent broad access to everything, you give it a focused tool for Static Studio actions. ## Example Workflows Here are a few practical workflows you can run today. ### Create a New Static WordPress Site Ask your agent: > Create a new Static Studio site called “Launch Demo,” then show me the site ID and current status. The agent can run: ``` static-studio sites create --name "Launch Demo" --subdomain launch-demo static-studio sites list --json ``` This is useful when you want to quickly create a new marketing site, test project, or client setup. ### Import an Existing WordPress Site Ask your agent: > Import this Studio backup, wait for the migration status, then show me the next recommended action. The agent can create a new site from a migration file and then inspect the result. This is especially useful for agencies moving existing WordPress sites into Static Studio. ### Publish Static Changes Ask your agent: > Push the latest changes for this site and summarize whether the deployment succeeded. The agent can trigger a changed-page deployment, inspect the site status, and summarize the result. That means publishing no longer has to start in a dashboard. ### Add Redirects After a Migration Redirects are one of those migration tasks that can easily become repetitive. With the CLI, your agent can help create redirects from structured files, list disabled redirects, and prepare them for review. This is a perfect example of where AI shines: not by making the final strategic decision, but by handling the tedious setup work. ### Debug a Failed Deployment Ask your agent: > Tail the last 200 log lines, filter for errors, and tell me what to check next. The agent can inspect, debug, and view error logs and deployment status without you having to jump through multiple dashboard screens. That makes troubleshooting faster, especially when you already work in a code editor. ### Run a Performance Check Ask your agent: > Run a fresh performance report and summarize the result for a client. The agent can trigger a performance check, retrieve the latest report, and prepare a client-friendly summary. That is useful for agencies, marketers, and anyone managing multiple sites where performance needs to be reviewed regularly. ## Who This Is For The CLI is technical, but the audience is broader than developers only. ### AI Builders If you are building sites with AI tools, the CLI lets you move from prototype to real WordPress-backed infrastructure. Your agent can help create the site, manage the setup, push changes, and inspect the result. ### Agencies If you manage client sites, the CLI can help with setup, migrations, redirects, domains, logs, backups, and reporting. That means less dashboard work and more repeatable processes. ### WordPress Developers If you already like working from the terminal, the CLI gives you a faster way to control Static Studio. You keep the WordPress workflow, but operational tasks become scriptable. ### Technical Marketers If you work on campaign sites, landing pages, or content-heavy WordPress sites, the CLI gives you a way to combine AI-assisted work with a real hosting platform. - Use WordPress where it is strong. - Serve the public site static. - Let the agent help with the repetitive parts. ## Authentication and Safety The CLI supports interactive email OTP login for local workflows. During the trial period, OTP login is available, allowing you to test the CLI without setting up long-lived credentials. For paid plans, Personal Access Tokens are available for CI and agent workflows. The recommendation is simple: - Use environment variables for tokens. - Do not paste tokens directly into AI chats. - Do not commit config files or secrets to repositories. - Review destructive commands like delete, restore, or redeploy. Give your agent enough access to help, but not enough room to create avoidable damage. ## Why This Matters for Static WordPress Static Studio already gives you managed WordPress for editing and static hosting for visitors. That means your public site benefits from static delivery, while your team keeps the WordPress workflow they already know. The CLI adds a new layer on top of that: Automation. You can now manage Static WordPress from your terminal, your scripts, your CI workflows, or your AI agent. That is a big step toward making WordPress feel modern again – not by replacing it, but by putting it behind a cleaner, safer, more scriptable workflow. ## Try the Static Studio CLI The Static Studio CLI is available now. You can install it from NPM: ``` npm install -g @simply-static/static-studio ``` Then run: ``` static-studio --help ``` You can also copy the agent setup prompt from the CLI page and paste it into Claude Code, Codex, Cursor, or another AI coding tool. If you already have a Static Studio account, you can start using it right away. If you are new to Static Studio, start a free trial and try the full workflow yourself. ## What’s Next? This is the first step toward making Static Studio much more automation-friendly. We’ll keep expanding the CLI, improving the command coverage, adding more examples, and refining the workflows based on real-world usage. We’ll also keep exploring what makes sense around MCP, deeper agent integrations, and other ways to make Static WordPress easier to manage from modern development tools. As always, if you have any questions or feedback, reach out via the chat in your dashboard or email us at [support@simplystatic.com](mailto:support@simplystatic.com). Have a great week, Patrick Table of Contents ### Security Workbook Sign up and get our actionable WordPress Security Workbook** as a download straight to your inbox. #### Thank you! You have successfully joined our subscriber list. Table of Contents ### About the Author ![](https://simplystatic.com/wp-content/uploads/2026/06/patrickposner-wceu-profile-photo-2048x1917-1.jpg) **Patrick Posner** Founder and lead developer of Simply Static and a Static WordPress nerd. You can find me at various conferences, on Twitter/X or in our support desk. - [WordPress](https://profiles.wordpress.org/patrickposner/) - [X](https://x.com/patrickposner_)