Connect Claude or ChatGPT in one click, then just ask. Draft a post, build a page, clone to staging or bump PHP, in plain English, on your real sites.
❯ Draft a post announcing our new opening hours. Leave it as a draft.
⏺ wordify · create_post (MCP)
└ saved as a draft
Drafted “We’re open later from Monday”, 320 words, saved to Bright Path Dental. Nothing is published.
Your assistant can now write the content, not just run the hosting underneath it. Ask Claude or ChatGPT to draft a post, tidy up a page, or build a new one, and it happens on your real WordPress site in the same conversation. Content Tools is included on every plan, and it stays off until someone on your team switches it on.
Draft a new post from a brief or a few notes. New posts save as drafts, so nothing goes live until you ask for it.
“Draft a post announcing our new opening hours. Leave it as a draft.”
Read a page back, rewrite a tired paragraph, fix a heading, tidy an excerpt. Posts and pages both.
“Read my About page and tighten the second paragraph.”
Every edit creates a WordPress revision, so there’s always a way back to an earlier version of a post or page.
“Put the pricing page back to yesterday’s version.”
On block themes, edit site-wide colours and typography, templates, template parts and navigation menus. Caches clear themselves, so a change shows on the next page load.
“Warm up the site background and add Pricing to the main menu.”
Change every mention of something inside one post or page. It shows you each match in context before it writes, then leaves a single revision behind.
“Replace the old phone number everywhere on the contact page.”
Install a theme from the WordPress.org directory and make it the active one. These are hosting tools, so they work whether or not Content Tools is switched on.
“Install Twenty Twenty-Five and switch to it.”
List posts and pages across every site on your team and read any of them back, so you can see what’s stale or unfinished.
“List every post still sitting in draft on my main site.”
One click signs you into WordPress so you can read the work yourself before it goes anywhere.
“Open that draft in WordPress so I can check it.”
Your assistant writes the whole thing in one go, in Gutenberg blocks or hand-written HTML, on a template from your active theme. The markup renders exactly as it was written.
Pictures still come from your WordPress media library.
<section class="alignfull">
<h1 style="font-size:clamp(
2rem,6vw,4rem)">Learn to surf
</h1>
<p>Small groups, warm water.</p>
<a class="wp-block-button">
Book a lesson
</a>
</section>
Learn to surf
this spring
Small groups, warm water, boards provided.
Book a lessonYour assistant writes through WordPress, so every change it makes creates an ordinary revision, sitting in the same list as everyone else’s. If an edit lands wrong, roll the page back the way you always have.
New posts save as drafts unless you ask to publish, and anything deleted goes to the trash rather than away for good.
Wordify talks to your assistant over MCP (Model Context Protocol), the open standard AI assistants use to connect to other software. There is nothing to install on your sites.
Paste one address into your assistant and approve it once. No API keys and no config files.
In Console, go to Integrations, then AI Connectors, and flip the Content Tools card. Only a Wordify team Owner or Team Admin can switch it on.
It keeps the tool list it was given when it connected, so one restart is what brings the new tools through.
51 tools as at 20 August 2026, hosting and content together. You never learn the tool names. 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 question returns the health of your whole fleet: stale plugins, themes, core versions and PHP, with the recommended fixes attached. One more sentence rolls those fixes 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 host. A plugin only ever sees the site it’s installed on. We run the servers your sites sit on, so your assistant reaches every site on your team, and can move between the hosting and the content in the same request.
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.
Connecting an assistant hands it a job, not the keys. 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.
❯ Draft a post about our new opening hours. Leave it as a draft.
⏺ Draft saved. Open it in WordPress to review.
You describe it, your assistant writes it, and it lands as a draft on the real site. You read it in WordPress and publish, or ask for another pass.
❯ Upgrade the sites still on PHP 8.1, then draft a note for each client.
⏺ 5 sites upgraded, 5 drafts waiting for you.
A fleet audit, a hosting change, and five drafts, from one sentence. That’s what having your host in the conversation is actually worth.
Anthropic shipped a /design research preview in Claude
Code on 17 August 2026, which gives you editable artboards while you work. Draw a
page there, then ask Claude to build it on your WordPress site through the same
connector. No export, no copy and paste, no plugin in between.
Yes. With Content Tools switched on, Claude or ChatGPT can create, edit and trash posts and pages on any site on your Wordify team, and build a whole page from Gutenberg blocks or HTML. New posts save as drafts unless you ask for them to be published.
Yes. Paste the Wordify connector address into Claude, Claude Code, Claude Desktop or ChatGPT and approve it once, with no API keys and no config files. The connection covers every WordPress site on your Wordify team, rather than one site at a time.
No. Wordify is the host, so the connection happens at the hosting layer and already reaches every site you run with us. There’s nothing to install on your sites and nothing to set up site by site.
New posts and pages save as drafts unless you ask your assistant to publish, so going live stays your decision. Every edit creates a WordPress revision you can roll back to, and anything deleted goes to the trash rather than disappearing.
On block themes, yes. Your assistant can edit site-wide colours and typography, templates, template parts and navigation menus, and roll any of it back to a revision like any other change. On a classic theme it returns a clear error and sticks to posts and pages.
Partly. A page built with Elementor, Divi, WPBakery or Beaver Builder can’t have its body edited, because those builders store the layout outside the post content, so your assistant returns an error instead of breaking the page. Titles, excerpts and status still work, and ordinary Gutenberg posts on the same site are fully editable.
Almost always because the client hasn’t been restarted since Content Tools was switched on. Claude and ChatGPT keep the list of tools they were handed when they connected, and turning the connector off and on in settings doesn’t refresh it. Restart the client and the content tools show up.
MCP stands for Model Context Protocol. It’s an open standard that lets AI assistants connect to other software. Wordify runs an MCP server, so assistants like Claude and ChatGPT can see and work on your sites under your own 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.
On the hosting side: delete or suspend a site, change billing, or manage team members. Those stay human-only in the Console by design. On the content side it can’t upload images or set a featured image, so pictures come from your WordPress media library, and it can’t set categories or tags. It can’t touch theme files or stylesheets, and find and replace works inside one post at a time, never across a whole site. Scheduling isn’t part of Content Tools yet, so ask for a draft and then publish or schedule it in WordPress.
No. The AI connector and Content Tools are 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. Content Tools is switched on once for the team, by a Wordify team Owner or Team Admin.
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? You’ve been talking to your hosting since June. Turn on Content Tools and it can write as well.
