Persyst connector
Sellsy MCP connector for ChatGPT, Claude and Copilot
Each member authorizes their own Sellsy account to create and enrich CRM records from their assistant.
Updated on October 28, 2026
Your tools
- Each member connects their account
- Rights per person, team or client
- Who read what, and when
Everyone’s AI
In short
- Persyst works without a vendor MCP server: Sellsy does not publish one, Persyst provides its own, hosted, with nothing to install on workstations.
- Search, read and write CRM tools: create and enrich records, add follow-up comments, fill custom fields and link contacts to companies.
- Permissions are Sellsy’s: privilege profiles and per-object sharing apply as they are. A record hidden in Sellsy stays hidden in the AI.
- The connection is personal: a member never reads the CRM with a colleague’s account.
EXAMPLES
What your team can ask
Prepare my meeting tomorrow with Dupont SA: where do we stand with them?
Dupont SA has an open opportunity “Renewal 2027” at €24,000, Negotiation stage, owned by Camille. Last exchange on October 2: follow-up on the volume discount. A June quote went unanswered; two active contacts, Marc Dupont (CEO) and Léa Morel (purchasing).
Sources consulted
- Sellsy · company record
- Sellsy · timeline
- Sellsy · opportunities
Which opportunities in my pipeline are above €10,000 with no activity for 30 days?
Four opportunities: Atelier Nord (€18,500, 41 days), Groupe Verne (€12,000, 35 days), Mairie de Sault (€11,200, 33 days) and Beltran (€10,800, 31 days). All at the Proposal stage.
Sources consulted
- Sellsy · opportunity search
HOW IT WORKS
Sellsy in your AI, in three steps
Connect your Sellsy account
In My connectors → Add a connector, choose Sellsy. Enter the Client ID and Client Secret of your company’s private API V2 access, then authorize your own account on Sellsy’s consent screen. The connection can be renewed or disconnected from My connectors.
Open the tools
An administrator decides which Sellsy tools each team can use: search, record reads, history or CRM updates. These grants add to Sellsy’s permissions, they never widen them.
Ask from the assistant
The member asks their question in ChatGPT, Claude or Copilot. When several companies match, the assistant presents the candidates before reading a record. Every call goes through Persyst with the member’s personal connection and shows up in the history.
After identifying the right record, ask for example: “Add this meeting summary to this prospect” or “Update their phone number”. The assistant can create a prospect, enrich contact details, fill custom fields and follow an opportunity. Writes use the connected Sellsy account and require the corresponding Sellsy and Persyst permissions.
Enable write scopes on the Sellsy API access, then connect your account in My connectors. If your personal account is already connected, reconnect it to renew consent. Shared sources remain available for reads.
TOOLS
What your assistant can do
Sellsy· 12 tools
Opened team by teamFree-text search across the CRM: companies, contacts, individuals, opportunities, with each result’s type and id.
search_sellsy_crmFiltered search by type, status, owner or stage.
search_sellsy_recordsReads one CRM record by type and id.
get_sellsy_recordA record’s history: exchanges, notes, events, page by page.
search_sellsy_timelineBrowses a bounded collection: companies, contacts, opportunities, staff.
list_sellsy_resourcesReads a linked object: opportunity, quote or order.
get_sellsy_objectReference data to interpret records: pipelines, stages, staff, custom fields.
get_sellsy_referenceCreates a company, contact, individual or opportunity using the connected account.
create_sellsy_recordUpdates the supplied fields on an existing record.
update_sellsy_recordAppends a meeting summary or follow-up comment without replacing record notes.
create_sellsy_commentFills existing custom fields on a CRM record.
update_sellsy_custom_fieldsLinks an existing contact to a company.
link_sellsy_contact
Rights and audit trail
Rights per person, team or client.
Then, inside the tool, only the items you open. The rest does not exist for the AI.
One-click revocation.
Removing a member cuts their access in every AI at once.
A history.
Who used which tool, and when.
Credentials that stay put.
They remain encrypted in Persyst, never in the assistants.
COMPARISON
Persyst or a Sellsy MCP server?
| Criterion | Persyst | Community Sellsy MCP server |
|---|---|---|
| Who authenticates | Each member, with their Sellsy account, through Persyst. | Each member, with their own API key. |
| Installation | None: a remote MCP server, authorized from the assistant. | A server to install and maintain on every machine, or a third-party service you hand the key to. |
| Where credentials live | Encrypted in Persyst, never in the assistant. | In each member’s assistant configuration. |
| Scope | Per person, team or client, then per opened item. | Everything the key allows. |
| History | Who used which tool, and when, for the whole team. | None, or machine by machine. |
| When a member leaves | One-click revocation, in every AI. | A key to revoke at the vendor, machine by machine. |
What this connector does not do
- Writes require a personal Sellsy account, the corresponding OAuth scopes and Persyst tool grants. Shared sources remain read-only.
- Each member must connect their own Sellsy account in My connectors to write, including the person who added a shared source.
- No indexing or copy of the CRM: every question queries Sellsy live.
- Invoices, the product catalog and the Files module are not covered by the current tools.
Questions
Frequently asked questions
Is there an official MCP server for Sellsy?
Persyst does not need one. It links your assistant to Sellsy through OAuth and exposes its own CRM read and write tools, with no server to install. API access credentials are entered in Persyst and are not given to the assistant. If Sellsy ever publishes a connector, Persyst will keep its per-team rights and its history.
Does the AI see the whole CRM?
No. It sees what the connected member can see in Sellsy, no more, no less. Sellsy’s privilege profiles and per-object sharing apply to every call, and a Persyst administrator can still remove tools from a team.
Why a personal connection rather than a company account?
Because Sellsy assigns permissions per collaborator. A personal connection guarantees that everyone only reads their authorized records and that the history is nominative. Database or Search Console connectors, by contrast, connect at the organization level.
Can a sales rep prepare a meeting from Claude?
Yes. They ask their assistant to summarize a company’s record, timeline and opportunities. The assistant reads those through Persyst and drafts the preparation. Nothing is written to Sellsy.
How do I remove access for a member who leaves?
Deactivate them in Persyst: their tools disappear from every AI they use. Their Sellsy account is still managed in Sellsy, as today.
