Analytics Memory
Per-site memory for the GA4 and Search Console MCP tools. Every analytics call quietly records what it read, then the next call shows what changed since your last look. A deduped recommendation ledger and a dated note log per site mean your assistant stops giving you the same generic advice every time you ask about traffic.
The problem it solves
Without memory, every analytics question starts cold. The assistant sees raw numbers with no record of what it already recommended and no baseline to compare against, so it regenerates the same evergreen advice ("improve your top pages", "post consistently") session after session.
Analytics Memory fixes both halves. It remembers what was recommended, and it anchors every reading to the previous one so advice is about change, not absolutes. Everything is scoped strictly per site and per surface (GA4 and Search Console are tracked separately).
How it works
Automatic capture
Every ga4_* and gsc_* read writes a normalized metric snapshot. No extra step. The time series builds itself as you use the tools.
Delta since last look
Each response carries an analyticsMemory block comparing the current reading to the previous one. Differing windows (28d vs 7d) are flagged so deltas are never read out of context.
Recommendation ledger
Recommendations are fingerprinted. Re-surfacing the same idea bumps a counter instead of creating a duplicate, and the assistant is told to report progress rather than repeat open items.
Per-site note log
Logging a finding writes a dated note tagged analytics-log, analytics:<domain>, and surface:<ga4|gsc>. Your readable history lives in BlackOps notes.
The tools
Injected automatically
You do not call anything to read memory. Every GA4 and Search Console tool response already includes the analyticsMemory digest: per-metric deltas, the open recommendation ledger, and recent findings for that site and surface.
log_analytics_finding
Call this at the end of an analytics discussion. It records a summary, findings, and recommendations, upserts the recommendation ledger, applies any status changes you pass (in_progress, done, dismissed), and creates the dated note log entry for the site.
get_analytics_memory
Returns the full per-site, per-surface memory on demand: every tool's latest reading and delta, the complete open recommendation ledger, and recent findings. Useful before deciding what to recommend.
What it is not
There is no charting view. Snapshots are captured only when you use the tools, so their cadence is uneven, and GA4 and Search Console already hold the continuous metric history. Memory exists for the deltas between your sessions and to anchor recommendations to a date, not to redraw charts the provider already gives you.
Access and isolation
Analytics Memory is part of the analytics surface and requires Pro tier or higher, the same gate as the GA4 and Search Console tools. All data is isolated per workspace. One site never sees another site's snapshots, recommendations, or findings.