One MCP hub or separate MCP servers
Updated November 4, 2026
A separate MCP server per service works when you use one or two services in one AI client. With more services, several accounts or several AI clients, every server has to be added and signed in to in every client, usually for one account each. A hub such as Manyplug is added once per client and holds all your services and accounts behind one address with the same rules.
| What | Manyplug | separate MCP servers |
|---|---|---|
| Setup per AI client | Add one address once | Add and sign in to every server in every client |
| Several accounts of one service | Named accounts behind one address | Usually one account per server entry |
| Services without their own MCP server | Built-in connectors, any IMAP mailbox, any REST API | Not available |
| Approvals and rules | Same approvals and per-app rules for every service | Whatever each server and client offer |
| Tool list in the AI’s context | Compact catalogue, details on demand | All tools of all servers at once |
| Claude free plan | Counts as one custom connector | One custom connector in total |
Choose Manyplug if
- You use more than a couple of services, several accounts of one service, or more than one AI client.
- You want one place to see what the AI did and to approve risky actions.
Choose separate MCP servers if
- You need one service in one client, and its official server has a tool Manyplug lacks.
Use both
You can have both: add an official remote MCP server inside Manyplug by its address, and every AI client gets it through Manyplug with the same rules and approvals.
Facts about separate MCP servers come from its own pages, checked on November 4, 2026: Claude: custom connectors, Model Context Protocol