EMCP Tools 3.3.0: your AI now understands, undoes, and reuses your site

Most MCP servers are a pipe: they hand an AI a pile of low-level tools and hope it strings them together correctly. EMCP Tools 3.3.0 is about something different: giving the agent real intelligence about your site. It can now understand a page in one call, undo anything it changes, and reuse what you’ve already built.

Five cross-cutting features, plus full WordPress nav-menu management and a multi-site proxy. Eleven new tools, all free. Here’s the tour.

📸 Page Snapshot: understand a page in one call

Before this release, an AI editing a page had to call get-page-structure, then get-global-settings, then list-global-classes, then maybe an audit or two, and stitch the results together itself. That’s slow, token-heavy, and error-prone.

get-page-snapshot returns one normalized digest of a page:

• the structure tree with counts (how many of each widget, how deep it nests)
• the global colors, fonts, and classes actually in use, with usage counts
• per-device (tablet/mobile) responsive overrides
• a content outline: headings, word count, images, images missing alt text, links, buttons
• an SEO-lite summary (title, meta description, canonical, og:image, from Yoast, Rank Math, or core)
• structural warnings (empty containers, missing H1, excessive nesting)

Need more? Pass include: ["performance", "a11y", "seo"] to fold in audit summaries on demand (accessibility and deep SEO are Pro). It’s the read foundation everything else builds on. The AI reasons about the whole page from a single, cheap call.

↩️ Change History & Rollback: let AI experiment without fear

The number-one hesitation people have about letting an AI touch their site is: what if it breaks something?

3.3.0 answers that directly. Every mutation an agent makes (an Elementor page edit, a filesystem write, a database write) is recorded to a unified change ledger. And any recorded change can be undone:

• list-changes: recent changes, newest first, with whether each is reversible
• get-change: the full detail of one change, including its before-image
• rollback-change: undo a change by id: it re-saves the page’s prior Elementor data, restores a file from its backup, or inverses a database write from its before-image

Prefer a human in the loop? There’s a new History tab in the WordPress admin (EMCP Tools → History) that shows the same ledger with a one-click Roll back button on every reversible change. Let the AI move fast; you keep the undo button.

🔍 Content Search: reuse, don’t rebuild

Ask an AI for a “pricing section” and, without help, it builds one from scratch every time, ignoring the perfectly good pricing template you already have, and drifting from your design system.

search-content fixes that. It searches your own pages, saved templates, widgets, and global styles by natural-language query:

search-content({ query: "team testimonials" })
// → your existing testimonials template, ranked by relevance

The agent then clones or adapts the match instead of reinventing it. Behind the scenes it’s a materialized index (the plugin’s first custom table) that re-indexes incrementally whenever you save a page or template. Call reindex-search for a full rebuild. Reuse-not-recreate is the single biggest lever on output consistency.

🗂️ Content Mirror: git-trackable page history

For teams who live in version control, export-content writes each page/template’s content to git-trackable JSON files under uploads/emcp-content-mirror/. Point your own git or CI at that folder and you get a diffable, revertable history of every design. restore-content brings a page back from its file; list-content-exports shows what’s mirrored. An opt-in toggle auto-exports on every save. The plugin never runs git itself. It just maintains the files, so it stays within WordPress.org guidelines.

🧭 Navigation Menus: finally, over MCP

WordPress nav menus used to be reachable only through the Elementor Pro widget. Now there are two dispatcher tools, menu-read and menu-write, covering the whole surface: list/get menus and their nested item trees, list theme locations, create/rename/delete menus, assign locations, and add/update/delete/reorder items (custom links, pages, posts, CPTs, categories, taxonomies). Updates preserve unspecified fields, so nothing gets wiped.

There’s also an [emcp_menu] shortcode so a custom HTML header (say, an Elementor Canvas page) can render a live menu. Edit it once and every header updates. Big thanks to community contributor @Mrshahidali420 for this one.

🌐 Multi-site: one connection, many sites

The @msrbuilds/emcp-proxy package (1.9.0) now drives many WordPress installs from a single connection. Give it a site registry and switch between installs mid-conversation with emcp_use_site. Each site keeps its own session, initialized transparently. Perfect for agencies managing a fleet of client sites from one Claude session.

Also fixed

.mcpb bundles for multiple sites no longer overwrite each other in Claude Desktop. Each site’s bundle now gets a unique name so they install side by side. Thanks to @Threadcrapper for the sharp bug report and @Mrshahidali420 for the fix.

Get it

Free users get 3.3.0 through the in-dashboard updater; Pro rolls out on Freemius. Read the full changelog or dive into the docs. The new features each have a page under AI intelligence and WordPress tools.

As always, we’d love to see what you build. Drop a note in the community or open an issue on GitHub.