French company dataConnector
Company agreements
Search filed company-level collective agreements by theme, and retrieve one by identifier or filing number, from Claude or ChatGPT via Tulina's MCP server.
Official site: www.legifrance.gouv.fr
What it can do
3 read
- 01Read
Search filed company-level collective agreements
- 02Read
Retrieve an agreement by identifier or filing number
- 03Read
List the themes agreements are classified under
A filed agreement is a company stating on the record how it actually operates — not a careers page, a document with a date and a theme. One that filed on remote work has a remote-work policy whatever its site says.
They concern the relationship between a company and its staff. Using them to qualify a company is one thing; drawing conclusions about identifiable employees is another.
How do you connect company agreements to Claude and ChatGPT?
Through Tulina's MCP server, reading straight from Légifrance. Search filed agreements by theme, or pull one by identifier or filing number, in the same chat as the qualification call it informs, whether that chat is Claude or ChatGPT.
Why through Tulina
The connection was never the hard part.
Most systems now publish their own way for a model to reach them, and that is good: it is what Tulina connects to. The hard part is deciding who may use it, what it is allowed to return, and what the model knows before it asks.
The keys stay in one place
YouTeamOrganisation
Connect Company agreements once. The credential is encrypted in a vault, never held in clear, and never pasted into a chat or a workflow file. A person uses their own key where they have one, their team's where they do not, the organisation's after that, so nobody is blocked and nobody holds more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
fields droppedmasked or hashedpseudonymised
Roles decide who can reach Company agreements at all. Beyond that, a policy on the connector itself decides what comes back. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
whatwhowhen
Runs are logged for the organisation. That is what makes an automated action reviewable after the fact, and it is what a security review asks for first.
The run starts knowing your company
namingkey accountsdecisions
A direct connection gives a model access. It does not tell it how your company names things, which accounts matter, or what was decided last quarter. Tulina carries that across every tool, so the same request against Company agreements returns something usable instead of something generic.
Processes that run on Company agreements
None published yet.