01 / INSTALL
Install the plugin
One zip, one activation. Nothing else to install, no account to create.
WordPress × MCP · v1.3.0
Let an AI build in your WordPress, not around it.
Mudy is a WordPress plugin that lets Claude, ChatGPT and other AI assistants work directly on your site. Pages get built in the page builder you already use, so you can still edit them afterwards.
● Free and open. One plugin, no account, nothing running on our servers.
Mudy / agent session
You → AI assistant
Build a services page matching the rest of this site.
✓inspect.site_context0.18s
✓detect.builder → elementor0.07s
✓create.page → draft1.42s
✓purge.caches0.31s
The problem
01
AI can write a page. Keeping it is the hard part.
Ask an AI assistant to build a page and you usually get HTML. It looks right. Then you paste it into WordPress, and the trouble starts.
Six months later your client opens that page to change a phone number. If the section is a real Elementor widget, they edit it in place. If it is a slab of HTML in a code block, they cannot touch it. Something that should have been theirs to maintain became yours.
The same goes for the rest of the site. An AI that cannot see which builder you use will guess. An AI that cannot clear a cache will build a page you swear is broken, because you are still looking at the old one.
Mudy closes that gap. It puts the AI inside WordPress, where it can see what the site actually runs and build accordingly.
How it works
Three steps. No extra service in the middle.
Install the plugin, approve the connection from your own WordPress, then ask your AI assistant to work with the site as it actually exists.
02 / CONNECT
Connect your assistant
Copy one URL into your MCP-capable AI client. Sign in to your own WordPress and approve the request.
03 / BUILD
Ask for what you want
Mudy checks the site, builds in its existing system, sets responsive values, and clears the caches afterwards.
Why Mudy
Built for the part after “generate”.
The important distinction is not whether an AI can produce code. It is whether the result fits the site, stays editable, and can be controlled later.
It builds in your builder, not around it.
Mudy detects whether a page type uses Elementor, Gutenberg, Divi or something else, and builds to match. On Elementor sites that means real containers and widgets, editable in the normal editor.
Nothing runs on our servers.
Your AI assistant talks to your site directly. There is no hosted Mudy service in the middle and no Mudy account required.
Access you can take back.
Every connection is listed, shows when it was last used, and can be revoked on its own. There is no permanent key to pass around.
Capabilities do not quietly expand.
Mudy exposes its own abilities and nothing else. Extra abilities from other plugins remain opt-in per site.
Security & responsibility
Powerful access should look powerful.
An approved connection can create and delete content, edit theme and plugin files, and run code. Mudy uses sign-in and approval, per-connection revocation, protected paths, file backups, and namespace scoping—but you still control what is approved.
Use development or staging first.
Before using Mudy on any production site, keep a current tested backup. Database recovery/version history is still in development.
OAuth 2.1 + PKCEENABLED
Per-connection revokeENABLED
Protected core pathsENABLED
Database rollbackIN DEV
FAQ
Questions developers ask first.
Straight answers about access, compatibility, requirements and what happens to your data.
Yes. All twenty-three abilities, on any number of sites, with no Mudy account. The plugin is GPL licensed.
No. Your AI assistant connects to your WordPress site directly. Mudy does not run a hosted service in the middle.
Anything that can connect to the MCP endpoint can work with Mudy. Claude and Claude Code are tested most. ChatGPT support for custom MCP actions varies by product and plan, so check the current client capability before promising a specific workflow.
An approved connection has administrator-level capability: it can create and delete content, edit theme and plugin files, and run code. Approve only applications you trust and revoke anything you do not recognise.
Elementor and the block editor are supported for authoring. Divi, Bricks, Oxygen, WPBakery and Brizy can be detected and read, but are not authored by this release; Mudy reports that limitation instead of pretending to match them.
WordPress 6.9 or newer, PHP 7.4 or newer, and HTTPS.
A cloud AI service cannot directly reach a local WordPress install, so a tunnel is needed. Editors running on your own machine can connect locally without one.
OnlineCaptain, a web and software agency in Surat, India. Mudy came out of real client work and the need to operate WordPress directly through AI tooling.
Free, and free to leave
Your site stays yours.
Mudy is GPL, like WordPress. Download it, read the code, change it if you want. There is no trial, no card, and no lock-in—everything lives on your own site.