Persyst connector
GitLab MCP connector: code the whole team can ask about
A product owner, support or leadership get an answer drawn from the code, with no GitLab account and no project to clone.
Updated on October 31, 2026
Your tools
- Connected once, by the admin
- Rights per person, team or client
- Who read what, and when
Everyone’s AI
In short
- Persyst works without an MCP server to install: it is a remote MCP server shared by the team, with no developer tooling on anyone’s computer.
- Read-only: Persyst only asks GitLab to read the API and repositories. No commits, no changes.
- Per project: support sees the app, leadership also sees the back office, nobody sees the infrastructure. Each project opens its own tools.
- One branch followed per project, re-synced about every 10 minutes, with its last 500 commits.
EXAMPLES
What your team can ask
Why does a customer no longer get the payment reminder?
Since October 3, reminders are no longer sent to customers on direct debit: the condition is in services/reminders/payment_reminder.ts, line 27, added by the commit “No reminder for direct debit customers”. If this customer switched to direct debit, that is the expected behavior.
Sources consulted
- platform project · read
- Git history · read
Where is the 50-user-per-account limit?
It is set in config/plans.ts: 50 users for the Team plan, no limit for the Enterprise plan. It is checked when a member is invited, in services/invitations/create.ts.
Sources consulted
- platform project · read
HOW IT WORKS
GitLab in your AI, in three steps
Connect GitLab
In Data sources, an administrator authorizes Persyst on gitlab.com with an account that can access the projects to share, then picks the group. Persyst only asks to read the API and repositories.
Open projects to each team
In Repositories, the administrator adds the useful projects and the branch to follow. In Access management, they open each project, and its tools, to the relevant teams or members: support, product, leadership. Access can be changed at any time.
Ask from the assistant
The member asks in ChatGPT, Claude or Copilot: “is this behavior intended?”, “what changed?”, “where is this case handled?”. The assistant searches the open projects, reads the files and the history, and answers with its sources. The history keeps track of who read which project, and when.
TOOLS
What your assistant can do
GitLab· 9 tools
Opened team by teamReads a file from an open project, as of the last sync.
read_fileSearches the code of the open projects for a word or pattern, 50 matches at most.
grepLists the files whose path matches a pattern, 200 at most.
globLists a folder; each open project appears as a folder.
list_dirLists the latest commits of a project, 50 at most.
git_logShows one commit in detail: message, author, files changed.
git_showCompares two versions of a project to show what changed.
git_diffShows, for each line of a file, the commit that last changed it.
git_blameGives a temporary download link to one file of the project, up to 25 MB, valid for 15 minutes.
download_file
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 GitLab MCP server?
| Criterion | Persyst | Vendor’s GitLab MCP server |
|---|---|---|
| Who authenticates | The company, once, through an administrator. | Each member, with their vendor account. |
| Installation | None: a remote MCP server, authorized from the assistant. | None. |
| Where credentials live | Encrypted in Persyst, never in the assistant. | One token per member, managed by the assistant. |
| 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. | Depends on the vendor. |
| When a member leaves | One-click revocation, in every AI. | An account to disable at the vendor. |
What this connector does not do
- No writes: no commits, no branches, no changes to the project.
- Code and its history only: GitLab issues, merge requests and pipelines are not read.
- gitlab.com only: a self-managed GitLab instance cannot be connected.
- One branch per project, as of the last sync: a change pushed five minutes ago may not show yet.
- No personal connection: GitLab is connected at the organization level, by an administrator.
Questions
Frequently asked questions
Is there an official GitLab MCP server?
Yes. GitLab offers an MCP server that acts with each user’s account and permissions: it is meant for people who have a GitLab account. Persyst serves people who don’t: an administrator opens specific projects, read-only, to a team.
Does every member need a GitLab account?
No. An administrator authorizes Persyst once on GitLab and picks a group. Members ask about the projects open to them from their assistant, with no GitLab account.
Can a non-technical person really make use of the code?
They ask their question in plain language, as they would ask a developer. The assistant searches the code, reads the relevant files and answers clearly, citing files and commits so a developer can check.
Can several GitLab groups be connected?
Yes. Each group is connected as a separate connection. Name them so they are easy to tell apart, then set the projects open to each team.
Does the data stay with Persyst?
The code is synced to Persyst’s servers, hosted in the European Union. The excerpts read to answer are passed to the assistant of the person asking, like anything else they share with it.
