Development release. Back up first. Start on development or staging before using Mudy on a production site.
MUDY.
Install
Documentation / getting started

From ZIP to connected.

Install the plugin, copy the connection URL, approve the request in your own WordPress, then start with a small draft task.

WordPress 6.9+PHP 7.4+HTTPS required

Requirements

  • WordPress 6.9 or newer
  • PHP 7.4 or newer
  • HTTPS

Mudy uses capabilities available from WordPress 6.9 onward. Keep WordPress itself updated to the latest security release available for your branch.

Install

Download the release zip, then open Plugins → Add New → Upload Plugin → Activate.

When updating from an earlier version, delete the old plugin first rather than overwriting it. Activation is where Mudy creates its database tables, and activation does not run on a simple overwrite.

Download release ZIP

Building from source

cd mudy
composer install --no-dev -o
cd ..
zip -r mudy.zip mudy/

Connect

  1. Open Mudy → Connections in WordPress admin.
  2. Copy the connection URL.
  3. Add it as a custom MCP connection in your compatible AI assistant or editor.
  4. Sign in on your own WordPress site and approve the request.

Client support is not identical across products or plans. The server endpoint is MCP-based; check the current documentation for the AI client you plan to use.

Start with a draft

Build a services page matching the rest of this site.
Create it as a draft. Do not publish it.

Mudy can inspect the site context and builder conventions before authoring. Page creation is draft-first by default, which gives you a review point before visitors see anything.

If a connection fails

Run the host check on the Connections screen. Some hosts remove the header that carries authentication, which can make sign-in appear successful while every later request fails.

What the host check does

It reports whether the authentication header survives the hosting stack and, when it does not, points you to the configuration fix.

Before production use

Do not treat this like a harmless content generator.

An approved Mudy connection can perform administrator-level actions. Use development/staging first and keep a current, tested backup before any production session.

Recommended workflow

  1. Take and verify a full files + database backup.
  2. Prefer a staging clone for structural, code or bulk changes.
  3. Keep page creation as draft until it is reviewed.
  4. Review connection grants and revoke clients you no longer use.
  5. After changes, verify desktop/mobile output and critical site flows manually.