Connect your AI assistant to Wordify in one click and manage WordPress in plain English. Staging sites, PHP versions, backups, and logs: just ask.
Paste one URL into your AI assistant and approve with OAuth. No API keys, no config files, no tokens to manage.
“Clone this site to staging”, “why is example.com 500ing?”, “bump PHP to 8.4 everywhere”.
Every action runs under your account, shows up in your Activity Log, and respects your team permissions.
38 tools across the whole hosting control plane. You don’t learn them. You just say what you want done.
Spin up new WordPress sites, clone existing ones, check plans and regions.
“Create a new site in Sydney on the Business plan.”
Create a staging site, push it to live, or pull live back down to staging.
“Clone this site to staging.”
Create backups on demand, list what you have, restore when it matters.
“Back up every site before we update anything.”
PHP versions, cache, CDN, Redis, debug mode, basic auth and WordPress settings.
“Bump PHP to 8.4 and turn on Redis.”
List what’s installed, install new ones, enable and disable.
“Disable the gallery plugin on staging.”
Read the WordPress debug log, flip WP_DEBUG, check on long-running tasks.
“Why is example.org white-screening?”
Audit every site for stale plugins, themes, core and PHP in one call, then dispatch the fixes fleet-wide.
“Audit all my sites and fix what’s stale.”
Add custom domains and re-check DNS once you’ve pointed it.
“Add example.org and check the DNS.”
Usage and invoices, read-only, so the numbers are always at hand.
“What’s my bandwidth usage this month?”
One audit call returns the health of your whole fleet: stale plugins, themes, core versions and PHP, with the recommended fixes attached. One dispatch call rolls the remediation out across every affected site. That’s the difference between an AI plugin sitting inside one site’s wp-admin and an AI connected to the hosting control plane: Wordify’s AI surface manages the platform your sites run on, not one site at a time.
claude.ai connectors on Pro, Max, Team and Enterprise plans
in the terminal, IDE extensions, desktop and web
native app on macOS and Windows
Plus, Pro, Team and Enterprise, via developer-mode connectors
All product names, logos and brands are property of their respective owners and are used for identification purposes only.
An AI connection is a delegation, not a hand-over. Here’s exactly where the lines are.
AI actions mirror the team role you already have: site managers can manage, and only site creators can provision. Connecting an assistant never grants new access.
Deleting a site, suspending it, changing billing and managing team members are deliberately not exposed to AI. They stay in the Console UI, behind a human.
Every AI action is attributed to your user in structured logs, and connections and disconnections appear in your Activity Log.
Revoke any connected client instantly from Console. Tokens die immediately.
OAuth 2.1, one-hour access tokens, rotating refresh tokens and a strict redirect allowlist. Sensitive operations like restores and staging pushes have their own tighter rate limit.
❯ example.com is white-screening. What changed?
⏺ A plugin broke in last night’s update. Disabled it, site’s back.
Your AI reads the debug log, spots the plugin that broke in last night’s update, and disables it, while you’re still typing the apology email you no longer need to send.
❯ Bump PHP to 8.4 on every site that’s behind.
⏺ Audited 29 sites: 24 upgraded to 8.4, all healthy.
One audit finds 24 of 29 sites below PHP 8.4. One dispatch upgrades them all. That’s the whole job.
❯ Clone it to staging, and back up live first.
⏺ Backup done, staging clone ready to test.
Fresh backup, staging clone, test the change, push to live. The workflow you know you should follow becomes the path of least resistance.
❯ New client: site in London, domain, DNS check.
⏺ Provisioned in London, domain added, DNS verified.
Provision in the right region, add the domain, confirm DNS. One conversation instead of a checklist.
MCP (Model Context Protocol) is an open standard that lets AI assistants securely connect to other software. Wordify’s WordPress hosting exposes an MCP server, so assistants like Claude and ChatGPT can see and manage your sites under your account, with the permissions you already have.
Claude (claude.ai connectors on Pro, Max, Team and Enterprise), Claude Code, Claude Desktop, and ChatGPT (Plus, Pro, Team and Enterprise via developer-mode connectors). These are the clients we’ve verified end-to-end.
AI actions use the same team permissions your user already has, and nothing extra is granted. Every action is logged and attributed to you, destructive operations like deleting a site aren’t exposed to AI at all, and you can disconnect any client in one click.
Delete or suspend a site, change billing, or manage team members. Those stay human-only in the Console by design.
No. The AI connector is included with every Wordify plan. There’s no plan restriction and nothing to add on.
Yes. Each team member connects their own AI client, every action respects that member’s role, and multi-team accounts are supported.
One click in Console, under Integrations → AI Connectors. Tokens are revoked immediately.
No. You connect with a single OAuth approval. No keys, tokens or config files to manage.
Want the step-by-step? Read the quickstart guide.
New to Wordify? Start hosting with us and connect your assistant in minutes. Already a customer? Your AI is one OAuth click away.
