Agencies managing many clients
Set up Plugsight for an agency - manager accounts, one MCP server per client, cross-client checks, and how to keep each client's data apart.
Who it's for
You run or work at an agency and look after marketing, search or support for several clients. Each client has their own Google Ads, Analytics and Search Console, sometimes a store, a Mailchimp account or a Zendesk. You need to see every client at once for health checks, and one client at a time for their reports.
The Agency plan is made for this: 50 connections and unlimited MCP servers. Pro (10 connections, 5 MCP servers) works for a handful of clients. See Plans.
Connectors to set up
| Connector | How agencies use it |
|---|---|
| Google Ads | Sign in with the Google account that has your manager (MCC) account. Plugsight finds every client underneath, as one connection. |
| Microsoft Advertising | Sign in with the Microsoft login that reaches your clients' ad accounts. |
| Google Search Console | Every client site your Google login can open. |
| Google Analytics 4 | Every client property your Google login can open. |
| PageSpeed Insights | Speed checks for any client page. No connection needed. |
| Zendesk, WooCommerce, Magento, Mailchimp | Per-client accounts, when you run support, stores or newsletters for them. Each is its own connection. |
| Your agency mailbox, for example Gmail or Outlook | Client emails, briefs and report drafts. |
Name each connection clearly on Connections, for example "Acme Zendesk" or "Bright Dental Mailchimp". Your AI and Activity use those names.
How connections and client separation work
This is the most important part of an agency setup, so read it before you create servers.
- An MCP server picks connections, not individual ad accounts. If one Google sign-in reaches all your clients' Google Ads accounts, that is one connection. A server that includes it can reach every client that login can see.
- Hiding is per connection, on every server. Hiding a site or ad account under Show sites & accounts hides it from your AI everywhere, not just on one server. See Choose which sites and accounts your AI can see.
- Client-specific connections separate cleanly. A client's own Zendesk, store or Mailchimp is a separate connection, so you can put it in that client's server only.
So in practice:
- Use your manager logins for cross-client work on an all-clients server.
- Use per-client servers for each client's own connections, and, if you need a strict wall for ads and analytics too, connect that client with a Google or Microsoft login that only reaches that client.
Recommended MCP server setup
1. An all-clients server for your team
- Name: "Agency (all clients)"
- Account access: All accounts
- Allow changes: ticked if your team sends client emails through it, otherwise unticked
Use it for portfolio checks across every client at once.
2. One server per client
- Name: the client's name, for example "Acme (client)"
- Account access: Selected accounts, ticking only that client's connections
- Allow changes: your choice. Untick it if the server is only for reporting.
In a chat that uses this server, your AI can only reach that client's connections, so another client's tickets or orders can't come up by mistake. Remember to tick new connections in the right server: Selected accounts don't grow by themselves. See Edit an MCP server.
3. A read-only server if a client uses it
If a client will use a link themselves, make it read-only: Selected accounts with only their connections, and Allow changes unticked. The badge then shows Read & draft only.
Each AI app has to sign in to your Plugsight account and click Allow access to use one of your servers, and anyone with a server's API key can use it. Share access only with people you trust, and revoke a key when it's no longer needed. See API keys and Use several MCP servers.
Example questions
On the all-clients server:
- "Which clients' CPA rose more than 20% this month, and why?"
- "Across all client accounts, which ones spent more than 20% over last month?"
- "List wasted spend across all clients and the top negative keywords for each." (Ask your AI to split by account, so each client gets its own list.)
- "Give me an account overview of every connected platform this month against last month, per client."
- "Which client sites lost the most organic clicks compared with last month?"
On a client's server:
- "Prepare a one-page performance summary for Acme vs last quarter."
- "Which of Acme's campaigns are losing impression share to budget?"
- "Which of Acme's keywords have a quality score of 5 or less, and what's dragging them down?"
- "Where is Acme paying for clicks on queries they already rank top 3 for?"
- "Do Acme's top landing pages pass Core Web Vitals on mobile?"
- "What were Acme's most common Zendesk ticket reasons this month?"
A typical week
Monday: portfolio check. On the all-clients server, ask which accounts moved most against last week: spend, CPA and conversions per account. Note the clients that need attention.
Tuesday to Thursday: client work. Open a chat on each client's server. Run the wasted-spend, scale-opportunities or SEO-opportunities deep dives, and drill into anything they surface. Make changes in Google Ads or Microsoft Advertising yourself: Plugsight only reads ads.
Friday: reports. On each client's server, ask for a summary against last week or last month, in plain language for the client. If your agency mailbox is connected, ask your AI to save it as a draft to the client's contact, so you can check and send it.
Safety tips
- Name the client in every question on the all-clients server, or open the client's own server. The cross-client server can see everyone.
- Split by account. When you ask about several clients, rows with the same values are added together. Ask your AI to "show it per account" to keep each client's numbers apart, and to keep currencies apart.
- Keep client-facing links read-only. Untick Allow changes on any server someone outside your team uses.
- Client emails go through approval. Every email your AI sends shows you the recipients, subject and body first. Keep the daily email limit at a level that fits your team.
- Use Pause before handovers. If someone else will use your chat, or something in Activity looks wrong, click Pause everything on Permissions. Reading keeps working. See Pause changes.
- Remove a client's access when they leave. Delete their server and remove their connections. See Disconnect AI apps or delete a server and Remove access.