# Use several MCP servers

> Set up one server per client, a read-only server to share, or separate servers per AI app, and keep data apart.

Each MCP server is a separate link with its own accounts, its own **Allow changes** setting, its own connected AI apps and its own API key. Having several lets you give different AI apps or people different access.

How many servers you can have depends on your plan: 1 on Free, 5 on Pro, unlimited on Agency. See [MCP server limits on each plan](https://docs.plugsight.app/mcp-servers/plan-limits.md).

## Common set-ups

### One for you, with everything

- **Account access:** **All accounts**
- **Allow changes:** ticked

Your everyday link. New accounts you connect are included automatically. Changes still depend on each account's switch and your approval in the chat.

### One per client

- **Name:** the client's name, for example "Acme (client)"
- **Account access:** **Selected accounts**, ticking only that client's accounts (their Google Ads, Analytics, Zendesk and so on)
- **Allow changes:** your choice

In a chat that uses this link, the AI can only see that client's connections, so another client's data can't come up by mistake.

> [!IMPORTANT]
> A server chooses whole connections, not single ad accounts inside them. If one Google login (for example a Google Ads manager account) reaches several clients, every server that includes that connection reaches all of them. Hiding an ad account under **Show sites & accounts** hides it on every server, not just one. To keep clients fully apart, connect each client with its own login (for example an access grant on the client's own account) and put only that connection in their server. See [Agencies](https://docs.plugsight.app/use-cases/agencies.md).

### A read-only server to share

- **Account access:** **Selected accounts**, ticking only what the other person should see
- **Allow changes:** unticked

The badge shows **Read & draft only**. Whoever uses this link can read those accounts and write email drafts, but can't send email, update tickets or book events, whatever the account switches say. It can still archive, label and mark emails in the mailboxes it reaches. This suits a server you share with a client or colleague.

> [!IMPORTANT]
> Each AI app must sign in to **your** Plugsight account and click **Allow access** before it can use a server. A server with an API key can also be used by anyone who has the key, so share a key only with people you trust, and revoke it when they no longer need it. See [API keys](https://docs.plugsight.app/mcp-servers/api-keys.md).

### One per AI app

For example, "Claude" and "Cursor". Then **Disconnect all AI apps** on one server doesn't affect the other, and **Activity** shows which server each request came through.

## Tips

- **Name servers clearly.** The name is what your AI app shows for the connector, and what **Activity** shows under **Who** ("via Work").
- **Selected accounts don't grow by themselves.** When you connect a new account, tick it in each server that should reach it.
- **One account can be in many servers.** Connecting an account once is enough; add it to as many servers as you like.
- **Check what a link reaches.** Ask your AI "list my Plugsight accounts" to see exactly what the server it's using can reach.
- **Account switches apply everywhere.** The switch on **Connections** belongs to the account, not the server. A server with **Allow changes** unticked never makes changes, but a server with it ticked follows each account's switch.

## Related articles

- [Choose which sites and accounts your AI can see](https://docs.plugsight.app/connectors/hide-sites-and-accounts.md): keep individual sites or ad accounts away from your AI.
- [Create an MCP server](https://docs.plugsight.app/mcp-servers/create.md)
- [Edit an MCP server](https://docs.plugsight.app/mcp-servers/edit.md)
- [Read-only connectors](https://docs.plugsight.app/permissions/read-only-connectors.md)

---

Web version: https://docs.plugsight.app/mcp-servers/multiple-servers
