Managed WordPress hosting that is AI-ready out of the box.
Every InstaWP site carries its own MCP server, and your account carries one too. One URL connects a chat client, OAuth connects the fleet, and the CLI hands a coding agent the whole environment. Locked down by default.
One real site. Two ways in.
Same WordPress, different reach. MCP is the universal doorway: paste a URL into any chat or coding client, nothing installed. The CLI is the deep doorway: a token-auth binary that owns the whole environment around the site.
InstaMCP Live
Best for chat & web clients
Paste one authenticated URL into ChatGPT, Claude on web or desktop, Cursor, anything that speaks MCP. No install, no application password. The agent gets 40+ structured WordPress tools and works inside the conversation.
You want to drive WordPress from a conversation, hand a scoped token to a client or teammate, or work in a chat or web client with zero setup.
InstaCLI Live
Best for coding agents & CI
A token-auth binary your terminal agent runs non-interactively: Claude Code, Codex, Antigravity, the Gemini CLI, or a CI job. It owns provisioning, local-to-cloud, deploy, sync and one-command rollback.
$ instawp login
✓ Logged in successfully
# a coding agent owns the whole environment
$ instawp create --name acme --php 8.3
✓ acme (ID 48213) · https://acme.instawp.site
$ instawp wp acme plugin activate woocommerce --api
$ instawp local push acme --with-db
✓ Push complete! · URLs rewrittenAn agent needs to own the environment: spin sites up and down, push a local build to the cloud, run it in CI, snapshot and roll back around risky changes.
Real problems, solved by the agent.
Six jobs every WordPress team runs into, and the actual moves an agent on InstaWP makes to clear each one, from chat over MCP or the terminal over the CLI.
A client brief means days of building pages by hand.
Updating pricing or tags across 200 posts eats an afternoon.
Titles, slugs and schema are a mess across dozens of pages.
The site is down with a 500 and you can't tell which plugin.
One bad plugin update can take the whole site down.
You can't safely reproduce a production bug on the live site.
Everything your agent gets, the moment it connects.
InstaMCP is built into every InstaWP site. One authenticated URL, 40+ structured WordPress tools, and raw access switched off until you decide otherwise.
One URL. It just connects.
Every InstaWP site exposes its own authenticated endpoint. Drop it into ChatGPT, Claude, Cursor or anything that speaks MCP and the agent is in. No Node bridge, no application password, no config file to babysit.
One scoped token. Paste it into any MCP client. Connected in one step.
One endpoint, the whole site.
Content, plugins and themes, media and taxonomy, diagnostics, skills and memory. Your agent calls a named tool like create_content or plugin_operations, so every action is a structured call with a result it can check, not a guess at raw SQL.
Safe Mode is on before you are.
Most AI-for-WordPress access is an application password with the run of a live site. InstaMCP hands over a scoped, revocable token and structured tools instead. Raw PHP, SQL and file access all ship off, and only you switch them on, from the site's own wp-admin.
Two scopes, both live.
The per-site endpoint is for deep work inside one install: build it, configure it, debug it end to end. The account-level connection runs over OAuth, so an agent can manage the account itself and fire one job across every site you own.
One token per site. One click to enable, one paste to connect, revoke it any time.
Your whole InstaWP account over OAuth. One prompt, every site in the fleet.
Want zero risk? Point the agent at a $2 disposable sandbox first. Let it build and break on a throwaway site, then promote the same site to production with one plan change. Other tools tell you to use staging. We are the staging.
Build, break, fix, ship. InstaCLI runs the whole loop.
Local WordPress with no Docker. Tests over HTTPS with no SSH key. A checkpoint you can undo in one command. Your coding agent runs it like any other tool.
Already at home in your terminal.
Claude Code, Codex, Antigravity, the Gemini CLI or a CI job. InstaCLI is one binary they shell out to like any other, so there is no plugin to write and no client to wait for.
Output it can reason over.
Add --json to any command and the agent gets machine-readable output, the observe half of an observe-then-act loop. Nothing to scrape, nothing to guess.
$ instawp logs acme --php --json
{ "level": "error",
"message": "Undefined array key \"tier\"",
"file": "checkout.php:42" }One token. That is the whole setup.
Export INSTAWP_TOKEN, or run instawp login once. No SSH keys to distribute, no wp-admin password, no browser step, so the same script runs on your laptop and in CI.
A failure fails, not hangs.
Commands return faithful exit codes, so a broken step stops the run instead of looking like success. Destructive operations need --force in --json mode, so a script errors out rather than waiting forever on a prompt nobody will answer.
More AI, on the way.
The MCP and the CLI are live today. Here is where AI goes next across the platform, each item badged so you always know what is shipping and when.
AI Builder July 2026
Describe the site you want and watch a real WordPress take shape on a sandbox you can promote to production. Not a throwaway draft: a real site you own, keep building on, with the agent that built it still on hand.
AI Assistance Coming
Chat with your site from inside wp-admin. Ask what is slow, what changed, and what to fix, without leaving WordPress.
AI Way Sync Coming
Let AI keep two sites in step, syncing just what changed between them instead of the whole install.
The real questions, answered straight.
MCP or CLI, which should I use?
Use MCP to drive WordPress from a chat or any MCP client with no install, great for conversational edits and handing a scoped token to a client or teammate. Use the CLI to provision, deploy, sync and roll back from a terminal or CI. Many teams use both.
Which AI clients work?
Any MCP client with a bearer token. We publish setup guides for 14, including Claude (Desktop, Code and web), ChatGPT (web and desktop), Cursor, Windsurf, Cline, Zed, GitHub Copilot, the Gemini CLI and the Codex CLI.
Is it safe to point AI at my site?
Yes. The agent gets a scoped, revocable token tied to a WordPress role and acts through structured tools, not raw code. Safe Mode blocks destructive writes and deletes, and raw PHP, SQL and file access stay off until you turn them on.
Can the agent run arbitrary code or SQL?
Only if you enable it. execute_php, db_query and site_files ship off by default and admin-gated, and execute_php also needs the admin scope. Agents can see the tools exist but get a "how to enable" message until you opt in.
Does the CLI need SSH set up?
Not necessarily. The CLI uses SSH by default and generates and caches the key for you. Add --api to run over HTTPS with no SSH setup, the way it works in CI and behind firewalls.
How is this different from the official WordPress MCP?
Same protocol, none of the setup. No Node bridge, no application password, no config files. One scoped token, 40+ tools and a $2 sandbox to test against, hosted and managed. On WordPress 6.9+ every tool is also registered through the WordPress Abilities API, so the official adapter sees them too.
What is live today, and what is coming?
Live: site-level and account-level MCP, InstaCLI and AI-enabled migrations. Coming: the AI Builder (July 2026), AI Assistance in wp-admin and AI Way Sync. Each one is badged so you always know which is which.
What does it cost?
The MCP is part of the site, no extra charge. You pay the usual per-site price, from a $2 sandbox up, billed by the day. The CLI is free to install. See pricing.
More than a chatbot.
Every InstaWP site plugs into the rest of the platform. Keep exploring:
Staging →
Clone, test, push live
Dev Tools →
SSH, CLI, Git deploy, MCP
API & Webhooks →
Provision sites by API
Snapshots →
Save sites & reusable presets
Hosting →
Managed WordPress, per site
Domains →
Buy, connect, or resell
Migrations →
Bring sites in, free
Integrations →
Connect your stack
Manage →
Every site, one dashboard
WaaS →
Resell hosting, your brand
Portal →
Panel for your clients
Templates →
Sell ready-made sites
Point your AI at real WordPress.
Connect by MCP from any chat client, or drive the CLI from your terminal. Either way, let an agent build, operate and troubleshoot a real WordPress, without leaving WordPress.