What’s New in mumcp v1.0.50

Overview

Version 1.0.50 was a milestone release for mumcp, marking the transition from a basic WordPress REST wrapper into a full-featured AI operations platform. This release introduced the Elementor validation engine, the template management system, and the foundation for the MCP tool architecture that now powers 139+ tools.

Elementor Validation Engine

The biggest feature in v1.0.50 was automatic Elementor data validation. Before this release, saving malformed Elementor JSON would silently break page rendering — you’d push data through the API and wonder why the page showed a blank white screen in the frontend.

The validation engine catches common mistakes:

• Missing element IDs — Every Elementor element (section, column, widget) requires a unique 8-character alphanumeric ID. The engine auto-generates missing IDs and logs a warning.
• Unknown widget types — If you pass widgetType: "headng" (typo), the engine suggests the correct name: “did you mean ‘heading’?”
• Invalid control keys — Elementor widgets have specific setting keys. Using title_size on an icon-box widget (which uses title_typography_font_size) silently breaks rendering. The engine warns about deprecated or incorrect keys.
• Column size validation — Columns in a section must have _column_size values that sum to 100. The engine checks and warns if they don’t.
• Structure mismatches — Multi-column sections need a structure setting (“20” for 2 columns, “30” for 3). Missing this causes layout issues.

All warnings are returned in the API response under the warnings[] array, giving AI assistants clear feedback about what went wrong and how to fix it.

Template Management

v1.0.50 added support for Elementor templates — the reusable building blocks that let you save and apply page designs. The API can now:

• List templates — Browse all saved templates with metadata
• Get template data — Retrieve the full Elementor JSON for any template
• Apply templates — Push a template’s design onto any page
• Create templates — Save a page’s current design as a reusable template

This enabled workflows like: design a page layout once, save it as a template, then apply it to 20 pages with one command. Particularly useful for multi-site management where you want consistent designs across all your WordPress installations.

MCP Tool Architecture

The Model Context Protocol integration was restructured in this release. Each API endpoint is now exposed as a named MCP tool with a clear description, typed parameters, and usage annotations. This means AI assistants like Claude can discover available tools, understand what each one does, and use them correctly without extensive prompting.

Before v1.0.50, connecting Claude to WordPress required custom instructions explaining every endpoint. Now the AI reads the tool definitions and knows exactly how to create a page, set SEO metadata, or upload media.

Additional Improvements

• Rate limiting — Configurable per-key rate limits to prevent accidental API abuse
• Activity logging — All API operations are logged with timestamps, tool names, and outcomes
• Batch operations — The wp_batch_update tool for executing multiple operations in a single request
• Media URL upload — Upload images directly from URLs without downloading them locally first

What Came After

Since v1.0.50, we’ve shipped 30+ additional releases adding SEO tools, form builder integration, the semantic page builder (wp_build_page), Theme Builder support, webhook system, Gutenberg block editing, widget management, taxonomy tools, multilanguage support, AI integrations (OpenAI, Gemini, ElevenLabs, Pexels), and much more. The current version (1.1.12) includes 139 MCP tools across 10 categories.

Check the full changelog for the complete release history, or visit the MCP Tools Reference to see everything that’s available today.