# One MCP server per client or purpose

> When to split your accounts across several MCP servers, how to name and set each one up, and the limits of what a separate server can separate.

One MCP server with **All accounts** is fine when you're the only person and every account is yours. Once you work with clients, share data with scripts, or want some AI apps to only read, separate servers keep things apart.

## Why split

- **No mix-ups.** In a chat that uses a client's server, your AI can't see another client's accounts, so it can't mention them by mistake.
- **Different permissions.** One server can allow changes while another is read-only.
- **Separate off switches.** **Disconnect all AI apps**, **Regenerate key** and **Delete server** affect one server only.
- **Clearer Activity.** Every entry shows the server it came through, "via [server name]".

## Ways to split

| Split by | Example servers | Typical settings |
| --- | --- | --- |
| Client | "Acme (client)", "Bright Dental (client)" | **Selected accounts**: only that client's connections. **Allow changes** usually unticked. |
| Purpose | "Reporting", "Support", "Inbox" | **Selected accounts** per purpose. Changes only where needed, for example on "Support". |
| AI app | "Claude", "ChatGPT", "Claude Code" | Often **All accounts**. Lets you cut off one app without touching the others. |
| Script or system | "Company dashboard", "Website stats" | **Selected accounts**, **Allow changes** unticked, an API key. One server per system. |

Mixing is fine: for example, "Me" with everything, plus one read-only server per client.

## Name servers clearly

The name is what your AI app shows for the connector, and what **Activity** shows under **Who**. Name each server after who or what it's for: "Acme (client)", "Support desk", "Website dashboard". Up to 60 characters.

## What a separate server can't separate

A server picks **whole connections**. It can't pick some ad accounts or sites inside a connection and leave out others.

- One Google Ads connection through your manager (MCC) login reaches every client under it, so a server with that connection reaches every client.
- Hiding an item with **Show sites & accounts** hides it from **every** server, not one.

To give a client a server that reaches only their ad account, you need a connection that reaches only that client: a Google login with access to their account and no others. See [Set up Plugsight for a new client](https://docs.plugsight.app/guides/new-client-setup.md).

## How many servers you can have

Free 1, Pro 5, Agency unlimited. See [MCP server limits on each plan](https://docs.plugsight.app/mcp-servers/plan-limits.md). On Pro, a common pattern is one server for yourself, one read-only reporting server and up to three client or system servers.

## Keep them tidy

- **Selected accounts don't grow by themselves.** When you connect a new account, tick it on each server that should reach it.
- **One account can be in many servers.** Connect it once, tick it wherever it's needed.
- **Delete servers you no longer use**, for example when a client leaves. The link stops working in every AI app and any API key is deleted. Your connections aren't touched.

## Several servers in one AI app

If your AI app allows several connectors, you can add more than one server, for example "Me" and "Acme (client)". Each shows under its own name. Switch on only the one you need for a chat, so answers don't mix.

## Related articles

- [Use several MCP servers](https://docs.plugsight.app/mcp-servers/multiple-servers.md)
- [Give your AI the least access it needs](https://docs.plugsight.app/guides/least-privilege.md)
- [Edit an MCP server](https://docs.plugsight.app/mcp-servers/edit.md)

---

Web version: https://docs.plugsight.app/guides/one-server-per-purpose
