WordPress MCP · Claude Code · Codex
Built with Claude Code. Made for AI to build with.
GF Builder was designed and built with Claude Code, and our own agency site was built with it the same way. Connect Claude or Codex to your WordPress site and it can compose real GF Builder pages: heroes, pricing tables, animations and all. You review the draft and publish.
› Rebuild /services as a landing page: angled hero, three service cards that fade up on scroll, stats band with rings, FAQ, CTA.
Loaded schemas: hero, card, stat, accordion, section
hero.composition = "angled"
card.animation = "fade-in-up", trigger = "scroll"
stat.display = "ring" × 3
✓ Draft saved. 22 blocks, all editable.
Proof, not a promise
An AI WordPress website builder, built by AI-assisted developers.
GF Builder was not retrofitted for AI. We built the plugin and theme with Claude Code from day one, so every block was shaped by what an agent needs: one schema per block, predictable settings, and patterns to start from. Our agency's own 50-page site was composed the same way.
Plugin and theme
Built with Claude Code
goodfellastech.com
Composed by AI, refined by hand
This website
Built with Claude, too
Your next site
Same workflow, your prompts
The idea
What WordPress MCP means for site builders.
MCP, the Model Context Protocol, is how AI assistants like Claude and Codex connect to outside tools. With a WordPress MCP connection, your assistant can read and write content on your site directly. What it can build is only as good as the blocks it has to work with.
The catch
Why AI struggles with Elementor and Divi layouts.
Bolt-on builders save layouts in their own data formats, with settings an agent has to guess at. Core blocks are easy to write but too basic to make a premium page. GF Builder sits in the gap: standard block markup, with every setting declared in a schema the agent can read.
Today
Set up a WordPress MCP server for Claude or Codex.
These work right now. All three write the same GF Builder blocks.
OPTION A
Claude Code or Codex
Point a coding agent at a local or staging site with WP-CLI, exactly how GF Builder itself was built.
OPTION B
WordPress MCP Adapter
Install the official MCP Adapter plugin from WordPress.org and add the server to Claude or Codex.
OPTION C
REST API
Create an application password and let the agent create and update pages through the WordPress REST API.
Good habits
- Have the agent save drafts, then review in the block editor before publishing
- Use a dedicated WordPress user with the editor role for AI work
- Build on staging first. Local and staging sites need no licence registration
Native GF Builder MCP tools.
We are building GF Builder's own AI tools straight into the plugin. Connect Claude or Codex and it will see GF Builder actions directly, instead of writing raw markup.
- Browse and insert patterns by name
- Compose whole pages from sections
- Apply style packs and design settings
- Read every block's options before using them
Get an email the day native MCP tools ship.
You are on the list.
We will email you when native MCP tools launch.
Questions