Get the plugin
WP MCP/Integrations/Operations

Operations integration

MCP for Duplicator

get-duplicator-status on the theme dispatcher pair reads Duplicator's own packages table (the current one since Duplicator 5, or the older one on a site that has not migrated): the packages newest first and the last completed build. Only the id, name, status, creation time and flags are read. The serialized package model, its hash and the archive name are never selected, so nothing is unserialized and no download name leaks. Read-only, at manage_options.

theme-read

What your AI can do

Real Duplicator operations, every write reversible.

  • List backup packages, newest first, with status
  • See the last completed build

Example prompts

Just ask.

Has Duplicator built a package this week?

List the last five Duplicator packages and whether they completed.

Under the hood

The real calls.

wpmcp, duplicator

theme-read({ operation: "get-duplicator-status" }), id, name, status, time, flags only

Frequently asked

Questions, answered.

Why are archive names left out?

Duplicator forms its download names from the hash and archive name in the package record, so those columns are never selected and no download name leaks into a model context.

Point your AI at Duplicator.

Release notes, straight to your inbox.

One email per release, what shipped, what's verified, what's production-only. No drip campaigns. Unsubscribe in one click.