Persyst connector
GitHub MCP connector: code the whole team can ask about
A product owner, support or leadership get an answer drawn from the code, with no GitHub account and no repository 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: the Persyst GitHub app only asks to read repository contents. No commits, no changes.
- Per repository: support sees the app, leadership also sees the back office, nobody sees the infrastructure. Each repository opens its own tools.
- One branch followed per repository, re-synced about every 10 minutes, with its last 500 commits.
EXAMPLES
What your team can ask
A customer says the CSV export leaves out cancelled invoices. Is that intended?
Yes. Since August 14 the export filters out invoices with the “cancelled” status: the filter is in app/exports/invoices_csv.rb, line 42, added by the commit “Exclude cancellations from the accounting export”. The customer can find them in the Credit notes screen.
Sources consulted
- app repository · read
- Git history · read
What changed in billing since the last release?
Three changes since October 2: VAT is now rounded per line, reminders go out at D+7 instead of D+10, and a new “customer reference” field appears on the PDF. Nothing affects amounts already invoiced.
Sources consulted
- app repository · Git history
HOW IT WORKS
GitHub in your AI, in three steps
Connect GitHub
In Data sources, an administrator installs the Persyst GitHub app on the GitHub account or organization, then picks the allowed repositories. No personal key to copy. The app only asks to read contents.
Open repositories to each team
In Repositories, the administrator adds the useful repositories and the branch to follow. In Access management, they open each repository, 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 repositories, reads the files and the history, and answers with its sources. The history keeps track of who read which repository, and when.
TOOLS
What your assistant can do
GitHub· 9 tools
Opened team by teamReads a file from an open repository, as of the last sync.
read_fileSearches the code of the open repositories 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 repository appears as a folder.
list_dirLists the latest commits of a repository, 50 at most.
git_logShows one commit in detail: message, author, files changed.
git_showCompares two versions of a repository 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 repository, 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 GitHub MCP server?
| Criterion | Persyst | Vendor’s GitHub 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 repository.
- Code and its history only: GitHub issues, pull requests and Actions workflows are not read.
- One branch per repository, as of the last sync: a change pushed five minutes ago may not show yet.
- No personal connection: GitHub is connected at the organization level, by an administrator.
Questions
Frequently asked questions
Is there an official GitHub MCP server?
Yes. GitHub publishes an MCP server that acts with each user’s account and permissions, issues and pull requests included: it is meant for people who have a GitHub account. Persyst serves people who don’t: an administrator opens specific repositories, read-only, to a team.
Does every member need a GitHub account?
No. The Persyst GitHub app is installed once by the company. Members ask about the repositories open to them from their assistant, with no GitHub account and no access to the organization.
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.
How do I keep a sensitive repository out?
Don’t add it, or open it to nobody. The repositories Persyst can offer depend on the GitHub installation; the ones each team can read depend on the access set in Persyst.
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.
