Your AI just learned WordPress.

No — that’s the point. You bring the Claude or ChatGPT you already use, and it works on their free plans too. WPVibe never charges for AI inference. Paid WPVibe plans only raise your daily allowance of WordPress actions, which is completely separate from your Claude or ChatGPT limits.

WPVibe was built around that exact fear. It doesn’t open your site to the world — there’s no public endpoint sitting there for bots to hit. Access runs through WordPress’s own Application Passwords, encrypted (AES-256-GCM) and revocable in one click. Posts default to draft, deletes go to trash, WP-CLI uses a default-deny allowlist, and database queries are read-only unless you approve the change in your browser with a dry-run preview. Every sensitive action lands in an append-only audit log.

The whole workflow is draft-first. New pages come in as drafts using your existing theme, and you preview and edit them before anything goes live. Theme work happens in an isolated draft with a private preview URL, and publishing keeps a backup of the old theme files so you can roll back. Your live site isn’t touched until you hit publish.

The free plan is genuinely usable: every tool and every skill, unlimited connected sites, and a daily allowance of WordPress actions (with a bonus bump your first week to soak up setup). Your account page shows a live percentage of today’s usage, so you’re never guessing. Pro ($19/mo, or $99/yr) gives you 5x more daily usage; Power ($49/mo, or $299/yr) gives you 20x. See the pricing page for the full breakdown.

Any MCP-compatible client: Claude.ai, Claude Desktop, Claude Code, ChatGPT (including the official WPVibe connector in ChatGPT Apps), Cursor, Windsurf, and more. Because WPVibe is hosted, it runs right inside the claude.ai and chatgpt.com web apps — no local server to set up.

Yes and no. WPVibe can build classic themes and pages — but that’s only part of what it does. It’s a general-purpose WordPress MCP server: it also manages content, inspects site health, uploads media, runs 40+ WP-CLI commands, searches stock photos, and interacts with plugin APIs. Think of it as giving your AI full access to the WordPress dashboard — through conversation, not just a page builder.

MCP (Model Context Protocol) is an open standard that lets AI assistants connect to external tools and data sources. WPVibe is a WordPress MCP server — it gives AI assistants a structured interface to your site for reading content, creating posts, managing media, running WP-CLI commands, and more.

The WordPress MCP Adapter is the official WordPress.org project — it runs locally via stdio and works great in desktop clients like Claude Desktop and Cursor. WPVibe adds remote access (so you can use Claude.ai and ChatGPT too), plus WP-CLI, stock photo search, theme building, rendered HTML inspection, and the Abilities API. Both are free.

If that setup works for you, you’ve already got the core of it. A raw Application Password can only reach what the REST API exposes, though. WPVibe adds 40+ WP-CLI commands — emulated through PHP, so they work on shared hosting with no shell and no SSH — plus theme-file editing, plugin abilities, and stock photo search. And it adds a safety layer a DIY setup doesn’t have: approval gates, dry-run previews, and an audit log.

It creates and edits pages in Gutenberg, Elementor, and SeedProd, with built-in skills for each. Divi works to an extent today — there’s no official Divi skill describing how Divi stores its content yet, but one is in the works.

Yes. ACF fields are post meta under the hood, and WPVibe reads and writes them properly — including the custom-post-type meta case that makes plain REST/MCP setups silently fail. Other plugins are driven through their own REST APIs or the WordPress Abilities API — WooCommerce, Rank Math, AIOSEO, and form plugins all work — and for plugins with no API, WP-CLI emulation can still reach their data and options.

Yes. It doesn’t matter who hosts your WordPress — if you can log into your wp-admin dashboard, you’re good, and you don’t need a WordPress.com account. Shared hosting, VPS, and managed WordPress (WP Engine, Flywheel, Cloudways) all work. The MCP server runs in the cloud, so your site needs to be reachable over HTTPS. For local development (localhost, .local, .test), expose it with a free Cloudflare Tunnel (cloudflared) and connect using the generated public URL.

Yes. WPVibe requires a small WordPress plugin (WPVibe) on your site. The plugin exposes the secure endpoints WPVibe uses, enforces your WordPress user capabilities on every request, and executes approved operations. Authentication itself uses WordPress’s built-in Application Passwords — the same standard used by Jetpack and the WordPress mobile app. It’s free on WordPress.org.

Yes — connected sites are unlimited on every plan, including Free. Connect all your WordPress sites to one WPVibe account and switch between them in any AI client conversation.