# How agencies can manage each client brand memory with MCP

> Create and maintain separate DunSocial memory collections for each client so AI-assisted drafts do not flatten every brand into one voice.

- Published: 2026-08-06
- Last updated: 2026-08-06
- Author: DunSocial
- Topics: mcp, how-to

---

The failure clients notice first is not a missing comma. It is when every account begins to sound like the agency. Per-workspace memory and personalization help, but only when the source material is reviewed and maintained.

One client workspace should never contain another client’s facts, examples or banned phrases.

Search phrases: client brand memory AI, agency MCP memory, separate client brand voices, DunSocial memory collections, AI social media agency workflow.

## What you will do

- Separate voice settings from factual memory.
- Save small client-approved entries.
- Audit and remove stale context before a new campaign.

## Before you start

- An active DunSocial workspace with the intended social accounts already connected.
- An MCP client that supports Streamable HTTP and OAuth, such as Claude, ChatGPT, Cursor or Copilot Studio.
- A person who can review the final account, copy and time before publishing.

## Step by step

### 1. Collect approved source material

Use the client brand guide, current website and approved examples. Exclude private strategy notes that should not influence generated public copy.

### 2. Draft memory entries for approval

Ask the assistant to convert source material into short entries grouped by audience, positioning, terminology and boundaries. Show them before saving.

### 3. Save in the client workspace

Create or reuse clearly named collections. Save one fact per entry so later changes are surgical.

### 4. Run a pre-campaign audit

Search for the product names and claims in the new brief. Update or delete stale entries instead of preserving both versions.

> Search this workspace for the product, audience and claims in the new brief. Flag memories that conflict with the brief. Do not update them yet.

## Check before you finish

- The assistant names the correct DunSocial workspace and destination accounts.
- Every factual claim comes from the source material or saved workspace memory.
- The final action, timezone and returned post or draft IDs are visible.

## Where to go next

Use a test draft to confirm the client voice, then delete the test rather than leaving review noise in the content queue.

---

## About this document

This is the Markdown representation of https://www.dunsocial.com/blog/manage-client-brand-memory-with-dunsocial-mcp. The HTML version of the same page is at the same URL. You can also request Markdown from any page by sending `Accept: text/markdown`.

Machine-readable summary of the whole site: https://www.dunsocial.com/llms.txt

## Company

- Product: DunSocial, https://www.dunsocial.com
- Legal entity: THISUX PRIVATE LIMITED, Chennai, Tamil Nadu, India
- Support: support@dunsocial.com
- Open the app: https://app.dunsocial.com/login