Can you build a WordPress site with Claude? Yes. I built a complete café website with Claude in one hour. No wp-admin, no config files and no code, just a conversation.
Cherry & Crema is a demo coffee shop site on WordPress. Claude was connected to it over MCP (the Model Context Protocol) using the free MCP Manager plugin, so every request I typed went straight to the live site: a theme.json design system, SEO, caching and a discount popup, all in about an hour, using just five free plugins. The finished site scores 93 for Performance and 100 for SEO in Google Lighthouse. Watch the full build on YouTube.
1 hr
To build the complete site
5
Free plugins, all from WordPress.org
93
Lighthouse Performance
100
Lighthouse SEO
Five free plugins to build a WordPress site with Claude
Every plugin used in the build is free on WordPress.org. Two connect Claude to WordPress; three do the actual work.
01
Connects Claude
AcrossAI MCP Manager
The WordPress MCP server. It connects Claude (or any MCP client) to the site, authenticating as a real WordPress user through Application Passwords.
02
Gives Claude abilities
AcrossAI Abilities Manager
Registers the operations Claude can perform: installing plugins, reading block templates, updating post meta, purging caches, and hundreds more. It also exposes each installed plugin’s own settings, which is how Claude configured the three below. See every ability.
Everything else came from WordPress itself: the Twenty Twenty-Five block theme, theme.json and core blocks.
What Claude built in one hour
Design
A theme.json design system
An espresso, cherry and crema palette, custom gradients, Roboto Slab headings, and a homepage with a hero, signature coffees, a full menu and opening hours.
SEO
Yoast SEO
Installed, organisation schema set up, the header logo set as the organisation logo, and a homepage title and meta description written from the page’s real content.
Performance
LiteSpeed Cache
Page cache confirmed working on the server, plus browser caching and image lazy loading.
Marketing
A 20% welcome popup
Built with Popup Maker from core blocks that use the theme.json presets, so it matches the site’s colours, fonts and spacing.
The Lighthouse scores: 93 Performance, 100 SEO
A fast build only counts if the result is good, so I ran the finished site through Google Lighthouse:
Google Lighthouse report
93
Performance
The result of the page cache, browser caching, and lazy loading with the hero image and logo excluded.
92
Accessibility
Core blocks and the theme’s design tokens give a solid base out of the box.
77
Best Practices
The one score with room to improve, and the next thing I’ll work on with Claude.
100
SEO
Yoast’s schema, the sitemap, and a title and meta description written from the page’s real content.
None of these needed manual tuning. They came from Claude making careful choices while it set things up.
The best part isn’t the speed
One hour is a nice headline, but it isn’t why this is worth doing. The reason is that Claude checked things before and after acting, the way a careful developer would.
01 · SEO
Checked before configuring
Before setting up Yoast, it checked that search engines weren’t being blocked and that no other SEO plugin was active.
02 · Branding
Found the right logo
It found the logo actually used in the header, not the reverse version sitting next to it in the media library.
03 · Server
Confirmed the cache works
LiteSpeed’s page cache only works on a LiteSpeed server, so it read the environment report to confirm the server supported it before calling the job done.
04 · Performance
Protected the first paint
Before turning on lazy loading, it excluded the hero image and the logo. Lazy-loading images at the top of the page makes it look blank for a moment and hurts Largest Contentful Paint.
05 · Popup
Didn’t invent the offer
Before publishing the popup, it asked how customers actually claim the 20%. The popup makes a promise to real visitors, so it didn’t invent that part.
The moment Claude said no
What I asked
I asked for the popup to appear whenever someone closes the tab.
What Claude said
Claude explained that no website can do that. Browsers block it so sites can’t trap people, and the most they allow is their own generic “Leave site?” warning. It suggested exit intent as the real-world alternative, pointed out that Popup Maker’s exit-intent trigger needs the Pro version, and flagged that a once-per-visitor popup would never reappear on exit for someone who had already seen it.
A tool that just follows commands would have written some JavaScript that didn’t work. This one understood what I was actually trying to achieve.
Verify after every write
The habit that makes this trustworthy
When Yoast’s response came back with an empty meta description, Claude didn’t assume it had worked. It read the setting straight from the database, confirmed it was saved, and explained that Yoast’s cached copy would catch up once indexing finished. That’s the habit that makes managing a site through chat trustworthy: every change is followed by a read that proves it happened.
How this compares to other ways of connecting Claude to WordPress
There are several good WordPress MCP tools now, and they make different trade-offs. Here’s how the approach in this build differs:
| Tool | How it connects | Where it’s meant to run | How it builds |
|---|---|---|---|
| MCP Manager + Abilities Manager | Plugins on your own site, built on the official WordPress MCP Adapter. No external account. | Production sites. This build ran on a live site. | Named, permission-checked abilities. Block themes, theme.json and core blocks. |
| WPVibe | A plugin plus WPVibe’s hosted MCP server. | Any self-hosted site. | Classic PHP themes with Tailwind, edited in a draft. |
| Novamira | A plugin that lets the AI run PHP, edit files and query the database. | Development and staging sites, with backups. | Writes and runs its own code. |
| InstaWP MCP | A managed MCP server built into InstaWP. | Sites hosted on InstaWP. | Depends on the tools you enable. |
If you want an AI that writes and runs arbitrary code, a PHP-execution tool gives it more freedom. If you want an AI you can safely point at a live site, named abilities that run as a real WordPress user are the better fit: every action is one WordPress already knows how to do, and every one respects that user’s permissions. For a deeper breakdown, see MCP Adapter vs MCP Manager.
How to build your own WordPress site with Claude
Step 01
Install the two free plugins
Add MCP Manager and Abilities Manager from WordPress.org.
Step 02
Connect Claude
Run the Quick Connect wizard, generate an Application Password, and paste the ready-made config into Claude. It also works with ChatGPT, Cursor, VS Code and other MCP clients.
Step 03
Start small
Ask for something reversible first, like “install Yoast SEO and tell me what needs setting up”.
Step 04
Build up
Move on to the design system, homepage, performance and popups, one request at a time.
Step 05
Verify each change
Ask Claude to read back what it changed, then run Lighthouse on the finished site.
Frequently asked questions
Can Claude build a WordPress website?
Yes. Once Claude is connected to WordPress over MCP, it can install and configure plugins, edit the theme’s design system, build pages from blocks and set up SEO and caching. This café site was built that way in about an hour.
Do I need to know how to code?
No. Everything in this build was done by describing what I wanted in plain English. Claude chose the settings, and ready-made plugins did the work.
Is it safe to let Claude manage a live WordPress site?
With MCP Manager, Claude connects as a real WordPress user through Application Passwords, so it can only do what that user is allowed to do. It uses named abilities rather than running arbitrary code, and you can revoke access at any time from your profile page.
Which AI assistants work besides Claude?
MCP is an open standard, so the same setup works with ChatGPT, Cursor, VS Code with GitHub Copilot, Gemini CLI and other MCP clients. MCP Manager includes ready-to-paste configs for each.
How much does it cost?
All five plugins used in this build are free on WordPress.org. You only need a Claude account to chat with.
Build your own site with Claude
Install the two free plugins, connect Claude, and start with one small, reversible request. Everything in this build is free on WordPress.org.
Watch the build: Building a café website in one hour with Claude · Learn more: acrossai.co