Official, community or company-wide MCP server: which one to choose?
Three ways to connect a tool to ChatGPT or Claude through MCP. Who authenticates, where keys live, who sees what, what happens when someone leaves: the comparison.
Published on October 28, 2026
In short
- An MCP server connects a tool to an AI assistant. There are three kinds: the vendor’s own, community servers, and servers connected once for the company, like Persyst.
- The first two authenticate per person: everyone needs an account in the tool, or their own API key.
- A company-wide server opens the tool to people without an account, with per-team access and a history of who read what.
Which company tools can I query from here, and with which rights?
You have access to five sources: Sellsy (your account, read), Aircall (Sales line: search, summaries, notes), PostgreSQL (orders and customers tables), Search Console (persyst.ai) and Batch (App project). Aircall transcripts and the database’s other tables are not open to you.
Sources consulted
- Persyst · sources open to the member
What an MCP server is
The Model Context Protocol (MCP) lets an AI assistant call external tools. A Sellsy MCP server, for example, exposes “find a company” or “read an opportunity”; when you ask Claude to prepare a meeting, it calls those tools and reads the answer.
So the question is not only “is there an MCP for my tool?”, but who connects to it, with which rights, and who manages it.
The three options
The vendor’s MCP server. Published by the tool itself. Each person connects with their account: handy for those who have one, useless for the others. Rights are the account’s, history is the vendor’s.
A community MCP server. Written by a third party, often installed on each machine with an API key. It covers tools whose vendor publishes no server, but every member holds a key, with everything it allows.
A company-wide server. This is Persyst’s model: an administrator connects the tool once, with the company’s credentials or a personal connection depending on the tool, then opens to each team what it can read. Members add a single remote MCP server to their assistant.
The comparison
| Criterion | Vendor | Community | Company-wide |
|---|---|---|---|
| Who authenticates | Each member, with their account | Each member, with their API key | The company, once (or each member, depending on the tool) |
| Installation | None | On every machine, or at a third party | None: remote server |
| Where credentials live | One token per member | In each machine’s configuration | Encrypted in Persyst |
| Scope | Everything the account allows | Everything the key allows | Per team, then per opened item |
| History | Up to the vendor | None, or machine by machine | Who read what, for the whole team |
| Member leaving | Account to deactivate | Key to revoke, machine by machine | One-click revocation, in every AI |
How to choose
- Everyone already has an account in the tool and the vendor’s history is enough: its MCP server does the job.
- The tool has no official server and a single developer uses it: a community server may be enough, keeping an eye on the key.
- People without an account need to read the tool (leadership, agency, client, support), or you want per-team access and a shared history: connect it for the company.
Persyst connectors
Persyst connects Sellsy, Aircall, PostgreSQL, Google Search Console, Silae, Batch, Redash and Clever Cloud for the company, among other connectors. A vendor’s remote MCP server connects too, with the same access rules and history (MCP servers and catalog).
Questions
Frequently asked questions
What is an MCP server?
MCP (Model Context Protocol) is an open protocol that lets an AI assistant call tools: find a client, read a table, list calls. An MCP server exposes those tools for a given service; the assistant uses them when the question calls for it.
If the vendor publishes its MCP server, is Persyst still useful?
Yes, when people without an account in the tool need to read it, or when you need per-team access and a shared history. Persyst can also connect a vendor’s remote MCP server for the company, with its access rules and history.
Is a community server dangerous?
Not necessarily, but it usually needs an API key on every machine, often with all that key’s rights. It has to be installed, updated, and the key revoked machine by machine when someone leaves.
Which assistants are compatible?
Claude, ChatGPT, Copilot, Le Chat and any assistant that can add a remote MCP server. Persyst is added once per member, then shows up among their tools.