What Site update report for MainWP does
Built for WordPress sites managed in MainWP (mainwp.com), the WordPress management dashboard. After a round of updates, it turns the before and after versions into a short, branded PDF a client can read, plus a ready-to-send email. It only reads from MainWP. It never runs updates, syncs or changes a site, because the update itself should stay a human decision.
What you give it
A site managed in MainWP, connected through the MainWP MCP server, plus either the plugins you updated or a before-state snapshot taken before you updated.
What you get back
- One branded PDF per site: info table, PHP, WordPress core, plugins updated, all themes, developer comments and completion date
- A short client email with a subject line and a body in plain words, ready for you to attach the PDF
- An optional before-state snapshot, saved before you start updating
Use cases
Monthly maintenance proof for clients
Send each client a clear record of what was updated this month, with the versions before and after.
Capturing the before-state in MainWP
Take a snapshot of the pending updates before you start, then compare after a sync so the report shows the real previous versions.
Reports across many sites
Every report comes from the same single template, so a client who gets six months of reports sees six identical layouts. One site, one PDF.
How to use Site update report for MainWP
Install the productivity toolkit
/plugin install productivity-toolkit@claude-skills
Connect the MainWP MCP server
The skill reads your sites through it. If it is not connected, the skill says so and offers a manual path where you type the versions.
Say "make the maintenance report"
A short wizard asks Manual or Automated, then which site, one question per screen.
Update the site yourself
On Automated, the before-state is saved first. You update and sync in MainWP, then run the skill again to generate the report.
Send the PDF and email
You get the PDF and a suggested client email. Nothing is sent for you.
Benefits
Audit only
It uses read-only MainWP calls. It never updates, activates, deletes, syncs or backs up a site.
One template, every time
Same layout, same sections, same wording for every site and month. Only the data and your branding change.
Short for the client
The plugins table lists only plugins that were updated. Core, PHP and all themes are always shown.
Real data only
Versions and dates come from MainWP or from you. Nothing is guessed or invented.
Install site-update-report
This skill ships in the productivity-toolkit plugin. Add the marketplace once, then install the plugin in Claude Code.
/plugin marketplace add rodneylungayan/claude-skills
/plugin install productivity-toolkit@claude-skillsAfter that the skill loads on its own whenever your request matches it. You can also invoke it by name with /site-update-report.
- Needs
- The MainWP MCP server, connected. Python 3 with the reportlab library to build the PDF.
- Profile
- Reads
~/.claude/profiles/site-update-report.md (optional). It asks for the details the first time and offers to save them there, so later runs ask nothing.
Questions about site-update-report
- Does it work without MainWP?
- No. This skill is for sites managed with MainWP. It reads versions through the MainWP MCP server. If the server is not connected, only the manual path is available, where you type the versions in.
- Does it run the updates for me?
- No. It only reads. You do the updating, usually on staging first, because an update is the step that can break a site.
- How do I put my own company name and logo on the PDF?
- Add them to the optional profile file. The skill asks once if there is no profile and offers to save your answers. Nothing about the author's own branding is built in.