Client memory: what your assistant knows about each client
A shared fiche per client and a journal of what changed and why, the same in every assistant and for the whole team, with rules checked on writes.
Your assistant remembers you. Get MCP Ads remembers your clients. Each client has a short shared fiche and a journal, kept by the gateway, so they are the same in every assistant and for every teammate. Nobody re-explains the target CPA at the start of a conversation.
The fiche: what is trueLink to this section
| Section | What goes in it |
|---|---|
| Objective | Goals and KPI targets, the conversion event that counts, the attribution window. |
| Rules | What must or must not be done: campaigns not to touch, budget limits. |
| Context | Business facts: offer, margin, seasonality, stock. |
| Learned | What was tested and what came out of it. |
One fact per line, 300 characters at most, and 2,000 characters per fiche. The limit is on purpose: a short fiche is read, and it can travel with every answer. When it is full, the assistant merges or replaces lines instead of adding. A line can cover the whole client or one ad account, for workspaces that hold several clients' accounts. Lines older than 90 days are flagged so the assistant checks them with you.
The journal: what happenedLink to this section
- Changes made through Get MCP Ads, by any teammate's assistant, with the reason given at the time and the assistant used.
- Events you note, such as a promotion, a site outage, a tracking problem or a stock-out, for one day or a date range.
- Changes made directly in Meta Ads Manager or Google Ads, archived every day with who made them. Google keeps this history for 30 days only; the journal keeps it for over a year.
Where it shows upLink to this section
list_accounts, the first call every assistant makes, returns each client's fiche.- Reports carry the objective, the rules and the journal of the period they cover, so a drop on the 20th is read next to the outage noted that day.
get_reads everything, journal included, on demand.client_ memory - Dashboard → Client memory shows the same fiche and journal, and lets the team correct them.
How it is writtenLink to this section
| Tool | Use |
|---|---|
remember | Add, correct or remove a line of the fiche when you state a durable fact about the client. |
note_event | Add a dated event to the journal, or remove one. |
reason on any write | Why the change is made. Saved with the change in the journal. |
The assistant tells you what it saved. Everything is dated and signed, and anyone with write access to the workspace can edit it. Your own preferences, such as tone or language, stay in your assistant: the fiche is about the client, not about you.
Rules checked on writesLink to this section
Two kinds of rules in the fiche are enforced by the gateway on every preview and every confirmed write, whichever assistant makes it: protecting objects by name pattern or ID (for example BRAND_*), and capping a budget increase over a rolling 24 hours (for example +20%). A change that breaks one is refused with the code CLIENT_RULE and nothing is changed. An exception goes through only when the person explicitly approves it and gives a reason, which is kept in the journal.
PlansLink to this section
Client memory is included in Team and Enterprise.
| Plan | Client memory |
|---|---|
| Free | No |
| Pro | No |
| Team | Yes |
| Enterprise | Yes |