GitHub Connector

Updated November 2, 2026. Le Chat is now Vibe (still at chat.mistral.ai): a single agent for work and code, carrying over your conversations, settings, and subscriptions. The legacy Le Chat experience remains accessible in Chat mode; in Work mode, agents are now skills (invoked with @), memories are the knowledge base, and deep search is the Deep Research skill. Plans are now called Mistral Free, Pro, Team, and Enterprise. This lesson uses the name Vibe; some menus described here may have changed names or locations.

GitHub Directly from Vibe

GitHub is one of the most powerful MCP integrations in the Vibe directory. It gives you access to your repositories, issues, pull requests, and branches without leaving the conversation. For a development team, the efficiency gain is significant: routine tasks—triaging issues, opening a PR, checking a file on a branch—no longer require switching back and forth to the web interface or recalling the right Git command.

Connection and Authentication

The connector authenticates via Personal Access Token (PAT). Configuration takes four steps:

1. Go to GitHub in Settings > Developer settings > Personal access tokens
2. Create a new token by selecting the required scopes (repositories, issues, pull requests, etc.)
3. In Vibe, open the Connectors tab and select GitHub
4. Paste your token and confirm

The token is stored securely and tied to your user account only. If you belong to an organization on Vibe, your colleagues cannot see or use it: everyone connects with their own credentials, and the scope visible to Vibe matches exactly what the connected person can access.

The scope selection is worth a few seconds of thought. Here are the main ones:

• repo: full access to repositories (read, write, create branches and PRs)
• read:org: read organization information
• write:discussion: participate in discussions
• admin:repo_hook: manage webhooks (rarely needed)

Apply the principle of least privilege: start with limited rights, and regenerate a broader token later if a specific use case justifies it. A full repo PAT granted just to consult issues is an unnecessary risk.

What the Connector Can Do

Once connected, Vibe covers four domains. First, consultation: it lists your repositories and their branches, displays the content of a given file, browses commit history, and checks CI/CD status. On issues, it lists open ones, creates new ones with title, description, and labels, comments on existing ones, and changes their status.

Work on pull requests follows the same logic: list open PRs, create one from a branch, consult diffs and review comments, then merge. Finally, on the code itself, Vibe creates a branch from another, creates or modifies a file on a specific branch, and pushes changes. This last category requires the most caution, since it writes to the repository.

Three Worked Examples

Take an ordinary morning. You want to check pending tasks:

“Show me open issues on the company/backend repo that have the ‘bug’ label and are unassigned.”

Vibe calls the connector, applies the filters, and presents a summarized list. You follow up in the same conversation to assign, label, or comment, without ever opening GitHub.

Second situation: you spot a gap in the documentation and dictate the work:

“Create a file docs/guide-migration.md on the docs/migration branch of the company/documentation repo with a guide explaining how to migrate from v2 to v3.”

The file is created on the indicated branch, and you immediately request the associated pull request. Third situation: you prepare for a code review and want an overview before diving into details:

“What are the open pull requests on company/frontend? Give me a summary of changes for each.”

Vibe lists the PRs, reads the diffs, and produces a structured summary that tells you where to focus your attention.

Two Habits to Build

The first concerns activation. The GitHub connector exposes many tools; in a conversation that isn’t about code, disable it. You will find the model selects the right tool more reliably when the list is short—this applies to any agent system.

The second concerns writes. Whenever Vibe proposes creating a file, branch, or pull request, the interface displays the JSON arguments before execution. Read them. Check the target branch name in particular, since confusing main with a work branch leads to costly mistakes; then verify the content of the created or modified file, followed by the PR title and description.

The Connector in a Workflow

GitHub shows its full potential when combined with other MCP connectors. A typical sequence involves scanning a support tool to spot a bug reported by a user, checking GitHub to see if a ticket already exists, creating the issue if not, then creating a branch, pushing a fix, and opening the pull request. You manage the whole flow from Vibe, with every write action subject to your validation.

Key Takeaways

• The GitHub connector uses a Personal Access Token with configurable scopes
• You can consult, create, and modify repositories, issues, and pull requests
• Every write action requires your explicit approval in the interface
• Disable the connector when not in use to improve model accuracy
• Combining it with other MCP connectors creates powerful automated workflows