WP & AI content

WP & AI is the content side of a WordPress site: open a site (/sites/:serverId/:domain) and the left rail gives you Posts · Pages · Categories · Tags plus Media, Menus, SEO and AI Studio — a wp-admin-style surface you drive from MZPanel, so most content work never needs a WordPress login. It’s a Pro feature.

Edit a post, step by step

1. In the site rail, open Posts (or Pages). You get a searchable table of that site’s content with status, author and dates.
2. Click a row to open the full-screen editor, or hit New to start a draft. The editor is its own route (/sites/:serverId/:domain/posts/:postId/edit) — the rail drops away so you get a centered writing canvas.
3. Write in the body. The right rail’s tabs — General · SEO · AI — hold the real WordPress fields: status, publish/schedule, slug, author, discussion, format, categories, tags, featured image and excerpt.
4. Save. Reads come over the fast path; the save is written straight into WordPress through the agent, so kses, hooks and block structure stay correct.

What else you can do

• Posts / Pages — bulk-select rows and change status, publish, move to draft or trash, all through the agent.
• Categories / Tags — full CRUD on taxonomies; assign them from inside the editor.
• Media — browse and manage the site’s media library (see Media).
• Menus — build and arrange the site’s navigation menus.
• SEO — plugin-free titles, social cards, schema and sitemaps, edited per-post from the editor’s SEO tab or fleet-wide on the SEO page.
• AI Studio — the site’s AI rail entry, a per-site content-recipe surface (see the status note below).

How it works

Content flows through the site’s agent — no remote child plugin, no Internet round-trip per request:

• Reads and writes dispatch a wp.content job. It proxies a WordPress REST call (wp/v2/posts, wp/v2/pages, wp/v2/categories, …) locally on the box through a mu-plugin bridge the agent installs and keeps current automatically — authenticated with a per-site token that never leaves the server. There’s no plugin for you to install, expose or maintain, and nothing talks to WordPress over the public Internet.
• Per-post SEO rides the same pattern on a wp.seo job.
• The Content Index is how listing stays instant. Each agent syncs lightweight metadata (title, status, type, URL, author, dates, categories, tags, word count) up to the control plane as its wp_content inventory — not the post body. The table filters against that index; the full body is fetched on demand only when you open a post.
• Block fidelity — the editor is Tiptap, but it round-trips through the Gutenberg block layer: block markup is parsed in for editing, and blocks it can’t edit natively are preserved verbatim and re-emitted on save, so a block-heavy post isn’t flattened.

Because it works locally, MZPanel manages content only for WordPress sites on servers you run — by design; it’s a control panel for your servers, not a tool for WordPress hosted elsewhere.

CLI & automation

Every content action maps to an mz command on the box — the same engine the dashboard drives. SSH in and run them directly, or let an on-box AI (ClaudeCode) run them:

mz content-index --json                                   # build the fleet Content Index
mz wp <domain> content GET wp/v2/posts --json             # list posts
mz wp <domain> content POST wp/v2/posts \
   --data '{"title":"Hello","status":"draft"}' --json     # create a draft
mz wp <domain> content GET wp/v2/categories --json        # taxonomies

The path and method match the WordPress REST API. See The mz CLI and the command catalog.

Gotchas & troubleshooting

• AI drafting is not live yet. The editor’s AI tab and the per-site AI Studio rail entry are built as surfaces, but the AI backend is still being wired up — AI Studio opens a “coming next” placeholder, and the editor’s Generate / quick-action buttons show “AI actions are coming soon.” Everything else on this page (Posts, Pages, taxonomies, the editor, SEO) is fully live.
• Draft-first by design. MZPanel’s stance is human-in-the-loop: when AI drafting does land, results arrive as an editable draft and never auto-publish — deliberately, both to keep a human in the loop and to stay clear of search-engine penalties for mass-generated content.
• SEO needs a first save. Per-post SEO is keyed by the post’s WordPress ID, so the SEO tab is disabled until you save the post once.
• Needs the agent online. Editing and saving read/write live through the agent; when it’s offline the site shell shows an “agent offline” banner and the table renders from the last Content Index snapshot.
• Your servers only. Content management is scoped to WordPress sites on servers you’ve connected to MZPanel — there’s no remote-site mode.

Related

• Site overview — the per-site health cockpit and quick actions.
• Posts & pages — the content table in depth.
• Media library — managing images and files.
• SEO — plugin-free titles, schema and sitemaps.
• The mz CLI — driving the box from the command line.