Store and recall project context across AI sessions. Remembers conventions, decisions, patterns, and configuration.
Every new AI session starts blank. Without somewhere to keep decisions, you re-explain your conventions, your field names and last week's reasoning — every single time.
Decisions and conventions outlive the session that produced them.
Values are stored and recalled by key, so an agent fetches what is relevant rather than everything.
An agent can list what it already knows before asking you again.
Memory belongs to the site it describes, so two projects never bleed into each other.
Anything stored can be deleted — a wrong convention is worse than none.
Built into NibWP. Nothing to install, nothing to configure.
Tell the agent how this site does things once. Every later session recalls it instead of asking you again.
Naming rules, spacing scale, which builder to use — stated once, applied always.
Keep the reasoning behind a choice, so a later session does not undo it.
Where things live on this particular install, in this particular setup.
A colleague's session starts with the same context yours ended with.
Memory is built into NibWP and gives any MCP-compatible AI agent — Claude, Cursor, Claude Code and others — somewhere to keep what it learns about your site between sessions.
Without it, every conversation starts from nothing. You re-state the naming conventions, re-explain which builder the site uses, re-argue a decision that was settled last week. With it, the agent lists what it already knows and asks only about the rest.
Values live in your own WordPress install, keyed so an agent can fetch what is relevant rather than reloading everything, and deletable the moment a remembered fact stops being true.
| Tool | Type | What it does |
|---|---|---|
| nibwp/memory-store | write | Store a value against a key. |
| nibwp/memory-recall | read | Recall what is stored for a key. |
| nibwp/memory-list-keys | read | List every key the site already remembers. |
| nibwp/memory-delete | destructive | Forget a key. |
No. Memory is built into NibWP and available on every plan, including Free.
On your own site, alongside the rest of your WordPress data. It is not sent anywhere for storage.
Storing is an explicit action. An agent writes to memory when it is asked to, not as a side effect of a conversation.
Delete the key. A stale convention is worse than an empty memory, so forgetting is a first-class operation.
Activate the integration and it's live on your MCP endpoint instantly.