Download
CHANGELOG

What's New

A history of every feature, fix, and improvement in MCPWP.

Coming next

In progress

  • Easier tools: job presets for API keys (Content writer, Designer, SEO, Store manager), and tool search that understands plain requests like "make the hero headline bigger".
  • A leaner tool catalog: overlapping tools merged, so agents pick the right one first time.
  • Approvals on their own database table: faster, and your approval history is kept for 90 days.
  • wp_look: the agent sees its own page as an image, with layout facts.
  • Watch the agent work: a live feed of what AI agents are doing on mcpwp.net.

3.14.9

September 30, 2026

  • Approvals now have their own database table: an approval can never apply or roll back twice, counts are exact, and a big queue no longer blocks new requests. Existing approvals move over automatically.
  • Only people in wp-admin and admin-scope API keys skip approval limits. AI agents (write keys, Claude and ChatGPT sign-ins, WebMCP) stay within them.
  • Approval history is kept for 90 days, and non-Latin text (Persian, Arabic, Chinese) counts at its real size.
  • Older approvals get their visibility worked out safely after the update; anything that can't be decided yet stays admin-only until it can.
  • Paid (Freemius) sites receive updates again.

3.14.8

September 29, 2026

  • WebMCP in wp-admin: the AI built into your browser can work on your site with your WordPress login, no API key. It reads, drafts and proposes changes; nothing is published or deleted without your approval. Off by default.
  • Approvals you can trust under load: each change applies once, failures are reported truthfully, and rollback of post and Elementor changes now works.
  • The activity log and embedded Elementor templates follow each API key's permissions.

3.14.7

September 28, 2026

  • Every tool that takes a post id checks who may touch that kind of content: products, coupons and orders need WooCommerce access, templates need template access, on Elementor, SEO, blocks and the site graph alike.
  • One clear "not found" answer everywhere, so hidden content can't be told apart from content that doesn't exist.

3.14.6

September 28, 2026

  • Approval requests only show to API keys that can work with what they change: a product delete needs WooCommerce access, a template change needs template access.
  • A draft or private post answers exactly like a missing one, so a key can't tell hidden content exists.

3.14.5

September 28, 2026

  • Deleting a WooCommerce product through the API now moves it to the trash, as the response says. Permanent deletes wait for approval.
  • API keys only see and change the post types their role covers: products need WooCommerce access, Elementor templates need template access.

3.14.4

September 27, 2026

  • A core tool profile: add ?profile=core to the MCP URL and agents load about 25 tools instead of 270, and search for the rest with mcpwp_find_tools and mcpwp_call.
  • Hard tools come with worked examples, and results suggest the next step to take.
  • Pages, brand, memory and guides are readable as MCP resources, with ready-made prompts for landing pages, fixing a page from a screenshot and publishing safely.
  • API key roles now cover the site settings routes. Author and Editor keys no longer change menus, options, memory or theme settings; give a key the Site category to allow it.

3.14.3

September 27, 2026

  • A site graph that WordPress keeps itself: pages, links, terms and media stored in your own database and kept up to date as you edit.
  • New read tools for agents: find orphan pages, look up a page's links in and out, and query the graph. Drafts and private content stay hidden from read-only keys.
  • MCP protocol 2025-11-25: tool titles, declared output shapes and structured results, checked before they are sent. Older clients keep working unchanged.
  • Jev can run through Cloudflare Workers AI with its own token, as well as through TypeSafe, and can be switched off in one place.
  • wp_build_page reports the page's real word count and whether it rendered.

3.14.2

September 27, 2026

  • Guardrails against scaled or duplicate publishing: a daily publish cap, and near-duplicate pages (like city-swapped copies) are held as drafts. Edits to live pages are flagged in the Control Room instead of blocked.
  • A shorter first briefing: wp_onboard answers in a few hundred tokens; detail=full still returns everything.
  • Forgiving parameters: a near-miss argument name is corrected and explained, and anything risky is refused with the right name.
  • Agents can read a whole rendered page in pages, footer included, and screenshots report failure honestly. Full-page and multi-width capture are supported.
  • Elementor Custom Code: exact readback, strict status values, snippets render right after being enabled or moved, and deleting one cleans up after itself.

3.14.1

September 27, 2026

  • Claude sign-in (the MCPWP broker) can call tools again: the sign-in token is forwarded as received.
  • Server errors keep their real HTTP status instead of a blanket 400, so agents can tell a failure from a bad request.
  • An Elementor save that WordPress refuses, or a CSS file that was never written, is reported as a failure.
  • Deleting an Elementor template also removes it from the display conditions.
  • Custom Code snippets can be updated again without a page-template error.
  • Every advertised MCP resource can be read, and names come back as plain text instead of HTML entities.

3.14.0

September 26, 2026

  • wp_seo_flags returns the six search signals worth acting on, with a ready-made SEO loop prompt.
  • AI crawler policy, IndexNow, and llms.txt/robots.txt that work alongside Yoast and Rank Math.
  • Tool failures come back as errors the model can read and recover from.
  • Accurate tool titles and read/write annotations for connector directories.
  • Optional Jev triage puts the most urgent approval requests first.

3.13.1

September 26, 2026

  • Fresh Elementor installs are detected correctly: container layouts are no longer rejected on new sites, and agents are steered to widgets that render.
  • Pasted HTML with scripts or styles no longer leaves code visible on the page; removals are reported back to the agent.
  • Find-and-replace edits appear on the live page immediately, and cost one rate-limit slot per page.
  • Header and footer templates publish only after their content saves, so a failed build never leaves an empty header live.
  • WooCommerce product templates keep every stored field when edited, and applying one no longer unpublishes live products.
  • Cleaner first install: no debug-log noise, the settings page shows the current update URL, and Free sites say "Free".

3.13.0

September 19, 2026

  • Publishing now requires an admin-scoped key. Write-scoped keys create drafts; a person with admin access publishes.
  • The agent role no longer holds plugin-settings rights, and the public API description no longer reveals the plugin version.
  • The admin Chat assistant can run site tools again.

3.12.0

September 19, 2026

  • Role-scoped API keys are enforced on every route, not only the MCP endpoint.
  • Elementor Custom Code snippets work again, and existing snippets are repaired automatically.
  • Elementor saves on published pages report failures instead of claiming success.
  • Large responses can be narrowed, and parameter names are consistent across related tools.

3.11.0 – 3.11.1

September 10, 2026

  • Permanent deletes wait for approval by default.
  • Safe retries: a repeated tool call with the same request ID is answered once.
  • Batch calls with a per-request spend budget, so one request can't run away with credits.
  • Stored provider keys use stronger encryption; weak encryption keys are refused.
  • Elementor element IDs match what Elementor Pro's live search and filters expect.

3.10.x

July – September 2026

  • SEO market data through DataForSEO: search visibility, ranked opportunities and an agent loop (bring your own account).
  • A long run of Elementor reliability fixes: no more silent successes, honest render checks, Kit CSS stored exactly.
  • Security hardening from independent adversarial reviews.

3.7 – 3.9

July 2026

  • Sign in from Claude with your WordPress login: add MCPWP as a custom connector, no API key to copy.
  • Tool-category toggles apply everywhere, and OAuth scopes fail closed.
  • Updates are published and monitored for both the self-hosted and Freemius channels.

Earlier releases are listed in the plugin's readme.txt changelog. Updates arrive automatically in WordPress from updates.mcpwp.net.

Want to see what's coming next?