WordPress platform · 3 modules
WordPress MCP Platform Modules you can audit after the fact.
The WordPress MCP platform modules are the part of GoBuildWP that works on WordPress itself and on the agent's own context: posts, media, menus, users and plugins, plus skills and memory. Writes are recorded in the change ledger, so a session can be audited afterwards.
What goes wrong without a plugin-aware module
- An AI client given a broad admin session instead of typed tools
- Secrets or volatile facts stored as long-lived memory
- Client-side instructions treated as an authorization boundary
Modules
3 modules compared
WordPress Core and Skills are built into Free; Memory requires Pro. Availability still depends on the enabled abilities and the connected user's authority. Open a module for its full ability list, requirements and safety notes.
| Module | Edition | Abilities | Inspect / change / destructive | Covers |
|---|---|---|---|---|
| WordPress Core | Free | 69 | 27 / 23 / 19 | content discovery and search, posts and pages, media library, menus |
| Agent Memory | Pro | 4 | 2 / 1 / 1 | save memory, retrieve memory, list memory, delete memory |
| GoBuildWP Skills | Free | 4 | 1 / 1 / 2 | skill discovery, skill retrieval, skill source, site instructions |
Worked example
Teach the agent the site's house style once, so the next session starts from it instead of from a pasted brief.
GoBuildWP's own skills and memory, which is the part of the product that shapes what the agent knows before it calls anything else.
wppilot/skill-writeFreeSaves the house style as a user skill. The title is cleaned into a lowercase, dash-separated slug, and a title another skill source already uses, such as a bundled skill, is refused.
wppilot/skill-getFreeLoads the skill back by slug with its full text and metadata, which is also what an agent does when the skill catalogue in its instructions matches the request.
wppilot/memory-saveProStores the one durable fact that is not a procedure, such as which page is the pricing page, as a memory. The memory index is added to the agent's instructions in later sessions.
wppilot/memory-listProShows the index of stored memories, to catch a duplicate or an outdated entry before it misleads the next session.
wppilot/list-changesFreeLists what the session wrote, with the ability, the credential and client behind each write, and whether it can be rolled back.
What to check yourself. Start a fresh session, explicitly call wppilot/skill-get for the saved slug and retain the named tool result or trace. Check catalogue eligibility in the Skills screen if it is absent. Then test whether the next draft follows the procedure; similar prose alone does not prove that the skill was loaded, and guidance does not grant authority or guarantee compliance.
Why it matters
What plugin-aware changes for wordpress platform
This group is GoBuildWP inspecting itself: which modules loaded, what an agent changed, what is waiting for a human, and what it is allowed to remember. It is the difference between an agent you can audit after the fact and one you have to take at its word.
A first safe workflow
The change ledger records supported writes from the first call, with nothing to switch on, so read it before you need it rather than after. Run one ordinary session, read the ledger, and confirm the entries describe what you believe happened. That single comparison is what tells you whether the record is detailed enough to rely on when the session in question is one you were not watching.
How to tell it worked
Read the change ledger after any session that wrote something, and confirm the entries match what you believe happened. Treat anything stored in memory as content a future prompt will act on, which is reason enough to keep secrets and short-lived facts out of it.
The core every other module builds on
WordPress core abilities work on every site, with or without other plugins
Every integration on this site loads only when its plugin is active. The WordPress Core module is the exception: it is part of GoBuildWP Free and answers on any install that meets the plugin's floor (WordPress 6.9 and PHP 8.0 or newer), because it works on what core itself stores. Posts and pages, media, menus, terms, comments, users, settings, plugins and themes are all reachable before a single third-party plugin is installed. On a small brochure site that may be everything an agent needs.
How much of a core change can be taken back follows the table it lands in, not how big the change feels:
- Posts, pages, custom post types and menu items share a trash, revisions for content and a before-image the change ledger can restore.
- Terms have no trash, so delete-term is final, and menu deletions, media deletions and permanent comment deletions cannot be restored either.
- Settings writes through update-site-settings are limited to ordinary site options. Rewrite internals, authentication settings and arbitrary option rows are never touched.
- Plugins and themes are files on disk. install-plugin and delete-plugin are critical operations, and a basic update-plugin or update-theme keeps no copy of the previous version.
Plugin and theme changes deserve their own plan
The core module can install, update and remove code, and that is the part of it that can break a whole site. switch-theme is confirmed separately because it changes every front-end page at once, drops widgets the new theme has no area for and re-maps menu locations. Updates replace files with no previous version kept by the ledger, so a failed update is recovered from a backup, not from rollback-change.
GoBuildWP Pro adds a safe-update kit with its own backup and health-check requirements and a bounded files-only recovery; the safe updates workflow explains the sequence. On sites without it, check backups first and update one plugin at a time.
What each safety profile allows in the core module
The Read Only profile refuses every write, which makes it the right first connection: the agent can inventory content, plugins and settings and nothing else. Production Safe permits ordinary content work but refuses critical operations, such as installing or deleting code and critical account changes. Deletes still run under it once confirmed, and by default the agent sends that confirmation itself. Anything beyond that belongs to a connection you deliberately raise. Since the core module is on every site, its profile decides most of what a new client can do on day one; see safety profiles.
Agent memory and skills in WordPress: deciding what goes where
Memory and skills both end up in the instructions an agent reads when it connects, which makes it easy to put things in the wrong one. A useful test:
- A procedure with steps, such as how this site builds a landing page or the checks before publishing, is a skill. Someone writes it on purpose and reviews it like documentation. Skills are part of Free.
- A fact about this site or its people, such as which page is the pricing page or a correction the owner made, is a memory. Memory is Pro, and the agent can save one itself with memory-save.
- Anything the site already shows, the current task's state, and every secret belong in neither. Every connected agent sees the memory index, and anyone who can manage GoBuildWP can read the bodies.
Keeping memories and skills from going stale
Both are content that a future prompt will act on, so outdated entries do real harm: an agent will follow last year's pricing page note as confidently as a current one. Review memory-list after a redesign, a domain change or a staff change, and delete what no longer holds. Memories are posts, so an edit can be restored from the ledger and a new one undone by trashing it; uninstalling GoBuildWP Pro removes them all.
For skills, keep the description precise, since a skill without one is never listed and a vague one is loaded at the wrong time. Pro's own integration skills cannot be edited on the site and appear only when their plugin is active. Write a user skill alongside one rather than trying to change it. The approvals, memory and skills guide covers the screens.
An audit routine that uses only the platform modules
After any session that wrote something, run list-changes for that session and read it against what you asked for. Each entry names the ability, the credential and client behind it, and whether it can be rolled back. Anything marked irreversible is the part to check on the site by hand. Then decide on undo with rollback-change, newest change first. The change ledger and rollback guide explains what each entry holds.
FAQ
WordPress platform and AI, answered
How do I see what an agent actually changed?
The change ledger records writes with the ability that made them, redacted for secrets. It is the record to read after any session that wrote something, and it is what makes rollback a decision rather than an investigation.
What should never be stored in agent memory?
Secrets, credentials and anything short-lived. Memory is content a future prompt will act on, so treat it as instructions to your own agent rather than as a private notepad.
What does the approval queue gate?
Nothing until you switch it on: Pro's approval queue is off by default. Once on, it holds the operations you route into it, which usually means destructive calls and anything touching people's access. An approval is a person confirming a specific change before it is applied, not a permission granted once.
Where are skills stored, and can I edit them outside the agent?
User skills persist in a private post type in the site's database, with ten revisions kept. Retrieved text and catalogue guidance are sent to the connected AI client and may be processed under its provider's policies. The Skills screen lists, edits, uploads and downloads them; an uploaded .md file can be at most 1 MB. Store no secrets and review outdated guidance.
Are memory and skills in GoBuildWP Free?
Skills are part of Free: writing, editing, loading and deleting them. The memory abilities are part of Pro. Both end up in the same place, the instructions the agent reads when it connects, which is why neither should hold a password, a key or anything that changes weekly.
Start in Read Only, then add what the site runs
Connect your AI client to the free MCP foundation and check what it can see. Core and Skills are Free. Add Pro for Memory; retrieved context is visible to the connected client and must contain no secrets.