Connect GitHub, your databases and your tools once. Your team queries them from ChatGPT, Claude or Cursor, with each member’s own access. Nobody gets a credential.
Works withChatGPTClaudeCursorGrokand your usual AI
Your sources
Code
GitHub - GitLab
Data
PostgreSQL - ClickHouse
Tools
Asana - Drive - Search Console
Set up once. Used by the whole team, in every AI.
Shared memory
Access by member and tool
Usage tracking
Your AI
Any MCP-compatible AI
How does account deletion work?
2 files found
A newcomer understands a feature by asking the repository from their assistant. No dev environment, no direct GitHub access.
Decision
Account deletion keeps a 30-day grace period.
Business rule
A test account is never an active user.
Decisions, business rules, ways of working. Saved once, found by the whole team from its assistant.
CCamille - Product
An admin connects each source with their own credentials and picks, for each member, the allowed connectors and tools. Persyst enforces the rule, whatever the assistant.
Every tool call is logged: who, which action, which source, when. An answer ready when someone asks who accessed what.
ENHANCED CONNECTORS
GitHub, Asana, Drive or Notion ship their own MCP. On those tools, Persyst adds a layer they don’t offer.
The whole repository is synced: search, file reading, history. A product manager asks how a feature works from ChatGPT, with no IDE and nothing to install.
Every task is synced and indexed. A plain-language question finds the related tickets, even without the right keywords.
Documents are indexed: you find them by asking a question, not by browsing a list of pages or files.
An admin connects the access once, with their own credentials. The team reaches it from its AI, without ever handling credentials.
The whole catalog
Batch
AgorapulseSources, members and memory in one place.
An admin links repositories, databases and tools, then sets each member’s access.
Authorize Persyst in ChatGPT, Claude, Grok or your usual AI. That’s it.
TO PASS ON TO YOUR LEADERSHIP
Without a shared layer, everyone pastes their own keys into their AI and nobody knows who reads what. Three one-sentence arguments to get the green light, without explaining MCP.
Sources are connected once, in Persyst. Switching assistant, adding or removing a member happens in one place. Someone leaves? Their access drops in every assistant, without touching the tools.
GitHub, ClickHouse or Postgres keys stay with the admin. Members use the sources from their AI without ever seeing them.
Who read which file, ran which query, at what time. The question “what does the AI do with our data?” has an answer.
In its usual assistant, connected to Persyst through MCP. The Persyst app is where you manage projects, sources, access and memory.
An open standard that lets ChatGPT, Claude, Cursor or Grok connect to external tools. Persyst plugs in like any MCP server: nothing to install on workstations.
No. Everyone uses their own assistant subscription. Access to MCP servers depends on that assistant’s terms.
No. An admin sets up the connection once in Persyst, with their own credentials. Authorized members use it from their AI, read-only, without ever handling credentials.
No. Your tools stay in place. Persyst keeps the synced code, the memory and the permissions, then sends the authorized assistant the excerpts it asks for.
Persyst’s infrastructure is hosted in France, at Clever Cloud. The excerpts an authorized assistant asks for are sent to it, under that assistant’s terms.
No. It is filled explicitly, from Persyst or from the assistant. Your private conversations are never imported.
Pricing depends on team size. Book a demo and we’ll come back with a quote.
Create a project, connect a source, find it in your assistant.
No extra AI subscription. Your tools stay where they are. Your conversations stay private.