Persyst connector
Silae MCP connector for ChatGPT, Claude and Copilot
Connected once by the company or the accounting firm, with no Silae account for each member.
Updated on October 18, 2026
Your tools
- Connected once, by the admin
- Rights per person, team or client
- Who read what, and when
Everyone’s AI
In short
- Silae publishes no MCP server: Persyst provides its own, hosted in France, with nothing to install on workstations.
- The payroll file is the unit of access: a file is opened to a team, a client or a person. The other files don’t exist for their assistant.
- Each file is set tool by tool: listing employees doesn’t open payslip lines, reading totals doesn’t open PDFs.
- Silae API credentials stay encrypted in Persyst; the assistant only receives authorised data. Read only: nothing is written to Silae.
EXAMPLES
What your team can ask
Compare gross payroll between August and September for Company A.
Gross payroll is up 4% in September: €212,400 against €204,200 in August. The gap comes from two hires on 1 September and overtime in the workshop team. Here are the totals per employee.
Sources consulted
- Silae · Company A · August totals
- Silae · Company A · September totals
How many payslips were produced in September for Company A, and which ones include overtime?
Forty-two payslips. Seven include overtime, all in the workshop team, for a total of 118 hours. Here is the list with hours per payslip.
Sources consulted
- Silae · Company A · September payslips
- Silae · Company A · payslip lines
HOW IT WORKS
Silae in your AI, in three steps
Connect the access
In Data sources, an administrator adds Silae and enters the client ID, secret and subscription key of the API access. Persyst tests authentication, encrypts the credentials and discovers the available payroll files. The administrator selects the ones to declare in Persyst; the others stay out of reach.
Open files and rights
Each file is granted to a team, a client or a person, with the allowed tools: employee list, payslips, totals, employment salary, PDFs. A file can be open to HR with every tool and to leadership with totals only. Grants can be changed at any time and apply to the next question.
Ask from the assistant
The member asks in ChatGPT, Claude, Copilot or Le Chat. The assistant finds the employee or the month, reads the authorised items and answers with its sources. Every tool call is logged: who, which file, which tool, when.
TOOLS
What your assistant can do
Silae· 4 tools
Opened team by teamLists the payroll files open to the member, with the tools allowed on each.
list_silae_dossiersBrowses a file: employees, employments, then a month’s payslips.
list_silae_recordsReads a payslip (header or lines), an employee’s totals or the current salary of an employment.
read_silae_payrollProvides a payslip PDF, when that right is open on the file.
download_silae_payslips
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 direct access to Silae?
| Criterion | Persyst | Without Persyst: direct access to Silae |
|---|---|---|
| Who authenticates | The company, once, through an administrator. | Each person, with a Silae account or through someone who has one. |
| Installation | None: a remote MCP server, authorized from the assistant. | Nothing to install, but an export or a screenshot to redo for every question. |
| Where credentials live | Encrypted in Persyst, never in the assistant. | One Silae account per person, or files passed around by email. |
| Scope | Per person, team or client, then per opened item. | Everything the account allows. |
| History | Who used which tool, and when, for the whole team. | None. |
| When a member leaves | One-click revocation, in every AI. | Account to remove in Silae; what was already shared stays shared. |
What this connector does not do
- Read only: no payroll variable entered, no payslip computed, no DSN filed from the assistant.
- No full-text search: an employee is found by name, a payslip by month, not by the content of a line.
Questions
Frequently asked questions
Is there an official MCP server for Silae?
No, neither official nor community. Persyst calls the Silae API with the company’s or firm’s access and exposes its own read tools, file by file.
Does every person need a Silae account?
No. An administrator connects the API access once. Authorised members consult their files from their assistant, with no Silae account or portal access.
Can an accounting firm open each file to its client?
Yes. The payroll file is the unit of access: the firm opens a client’s file to that client, and only that one. Several Silae connections can coexist in the same organisation.
Can leadership see totals without seeing individual payslips?
Yes. Rights are set per file, then per tool. Totals and employment salary can be opened to leadership, while payslip lines and PDFs stay with HR.
Does payroll data leave Silae?
Persyst doesn’t store it. It reads what the member asks for, passes it to their assistant and logs the lookup. Once in the assistant, the content falls under that provider’s terms, as with any source.
