Memory
These abilities register when Memory is detected on the site and a Pro licence is active. If either is missing the module stays absent rather than failing at call time.
At a glance
Memory registers 4 abilities: 2 that only read, 1 that write, and 1 marked destructive. That split is the practical answer to how much of this module can run unattended. Reads cost nothing and are safe to repeat, so discovery is the part to be generous with; the writes are where review belongs, and the destructive calls stop for an explicit confirmation every single time regardless of which profile is active.
What this module is for
WPPilot Pro can save, retrieve, list, and delete controlled memory records so approved site context can carry between sessions.
Before you rely on it: Store only durable, non-secret context and periodically review memory for accuracy and data minimization.
Typical workflows
- Store an approved brand or editorial rule
- Retrieve site-specific context before planning work
- Review and remove stale operational memory
The Agent Memory integration page covers the same module from the workflow side, with the capability map and the questions worth asking before a first write.
Availability on your site
The Memory module needs three things at once: WPPilot Free as the MCP foundation, an active Pro licence, and the companion plugin detected on the site. Miss any one and the module does not register, which is deliberate: an ability that appears in the tool list but fails at call time is worse than an ability that was never offered. What the connected agent can actually call is then narrowed twice more: by the safety profile active on the site, and by the WordPress capabilities of the user behind the credential. A read that succeeds for an administrator can be absent entirely for an editor.
Every write these abilities perform is recorded in the change ledger, and destructive calls can be routed through the approval queue so a person signs off before anything is applied. A successful tool result means the operation returned, not that the front end, the cache, and every dependent template are correct: that still needs a look.
Reads
Available in every safety profile, including Read Only. Inspection costs nothing and is not rate limited.
| Ability | What it does |
|---|---|
wppilot/memory-getGet Memory | Returns the full content of a single memory by id. |
wppilot/memory-listList Memories | Returns the concise memory index (id, name, description, type) for every stored memory. Note: the memory index is also automatically prepended to your tool discovery instructions, so you only need to call this if you need to fetch the index again during the session. |
Writes
Gated by the active profile and your WordPress capabilities. Rate limited to 120 per minute per credential.
| Ability | What it does |
|---|---|
wppilot/memory-saveSave Memory | Creates a new memory or updates an existing one. Use this to build up a persistent understanding of the user, their feedback, ongoing projects, and external references across conversations. |
Destructive
Marked destructive in the source, so each call needs an explicit confirmation flag, every time.
| Ability | What it does |
|---|---|
wppilot/memory-deleteDelete Memory | Permanently deletes a memory. Use when a memory is wrong, outdated, or the user asks you to forget it. |