# How agencies can manage client social workspaces with DunSocial MCP

> Keep client accounts, memory and drafts isolated by authorizing a separate DunSocial MCP connection for each client workspace.

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

---

For an agency, the dangerous shortcut is a single conversation that can blur several client identities. DunSocial workspaces are the isolation boundary for accounts, memory, personalization, media and members.

Authorize and name one MCP connection per client. The extra clarity is worth more than a clever cross-client prompt.

Search phrases: MCP for social media agencies, manage multiple client social accounts AI, client workspaces MCP, agency social media automation, DunSocial agency workflow.

## What you will do

- Create a clean workspace boundary for every client.
- Name MCP connections so the active client is obvious.
- Verify client identity before any write action.

## 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. Prepare the client workspace

Connect only that client’s accounts. Save their memory, personalization, media and reviewers inside the same workspace.

### 2. Authorize one connection

From Settings → MCP, add `https://api.dunsocial.com/api/mcp` to the assistant and choose this client on the OAuth screen.

### 3. Name and isolate it

Use a connection name such as “DunSocial · Lumen.” Disable other client connectors during sensitive drafting when the host allows it.

### 4. Repeat identity before work

Start every client conversation with a read-only verification.

> Name the DunSocial workspace, connected account names and current personalization. Do not create or modify anything.

## 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.
- No prompt asks one MCP authorization to act across several client workspaces.

## Where to go next

Use the client-memory guide to onboard brand context, then the brief-to-draft guide for actual campaign work.

---

## About this document

This is the Markdown representation of https://www.dunsocial.com/blog/manage-multiple-client-social-workspaces-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