There are three ways to connect Claude to a GitHub repo: Claude's own GitHub integration, which syncs the files of one branch; GitHub's MCP server, which gives Claude tools over the GitHub API; and an MCP server that answers from the code, such as DeployIt. Setup takes minutes in each case. What separates them is who sees what: what Claude can read, and who has to hold access to the repository.
This comparison is for the CTO who hears “can we plug Claude into the repo?” and has to answer for the whole company, not only for the developers. The step-by-step procedure for a private repository has its own guide: how to connect Claude to a private GitHub repo without sharing the code.
Start from the result you want. Here is someone in support, with no access to GitHub, asking Claude about the product through the third route.
A customer says their discount code was dropped at renewal. Is that expected?
Yes. A discount code only applies to the first subscription period: at renewal, the plan price comes back. Nothing tells the customer before the charge.
Who sees what when you connect Claude to a GitHub repo?
| Claude's GitHub integration | GitHub MCP server | DeployIt | |
|---|---|---|---|
| What Claude receives | The names and contents of the files you select, on one branch | What the GitHub API returns to your token: files, commits, pull requests, issues | An answer written from the code; excerpts for the Developers profile only |
| History | Not retrieved | Commits listed; diffs one commit or one pull request per call | What landed over 1 to 90 days, grouped into deliveries |
| Who needs GitHub access | The person who adds the repository | Every person who asks | Nobody who asks; an administrator connects the repositories once |
| What the asker sees | The files themselves | The files themselves | By profile: no code and no file path for Everyone and Leadership (filtered and tested; no filter is infallible), excerpts for Developers |
| How it stays current | A manual sync | Read from the API at each question | Updated after each push to the tracked branch |
Sources for the first two columns: Claude Help Center and the github/github-mcp-server repository, checked on 17 November 2026.
Route 1: what does Claude's GitHub integration see?
It is the simplest route, built into Claude. In a chat, the “+” button offers “Add from GitHub”; in a project, the “+” of the project knowledge offers “GitHub”. You pick a repository, then the files and folders to include. For a private repository, a GitHub administrator first authorises the Claude GitHub app, on all repositories or on selected ones.
Claude then reads the files as they are on that branch. The Help Center is explicit about the rest: “We do not retrieve commit history, PRs, or other metadata.”
Two practical consequences follow. The selection has to fit in Claude's context window, so on a large repository you choose folders. And nothing follows your pushes: you click “Sync now” to fetch the latest state.
Take a configuration file that says retry_limit: 3. Claude will tell you the limit is 3, and where it applies. Ask since when, or why it changed, and it has nothing to read. That lives in the history.
Who sees what: the person who connects sees the code itself. That suits a developer who wants to understand the repository as it stands today. It suits neither a colleague who should not see code, nor a question about what changed.
Route 2: what does the GitHub MCP server see?
The GitHub MCP server gives Claude tools over the GitHub API: list commits, read a pull request, search the code. The history becomes reachable. It comes one piece at a time, though: a commit's diff is one call, a pull request's diff another, and nothing adds forty of them up into “what changed this week”. Our guide to the GitHub MCP server follows those calls one by one.
Who sees what: everything the token can reach, as raw files and diffs. The server acts with the rights of the person who set it up, so every person who asks needs GitHub credentials. For a team of developers, that is acceptable. For support or sales, it means opening the repository to answer questions about the product.
Route 3: what does an MCP server that answers from the code show?
The third route changes what travels. The people who ask receive answers, not files.
DeployIt is an MCP server. Your company gets one link, https://mcp.deployit.ai/<company>/<code>; each person adds it to Claude (on the web, on the desktop or in Claude Code) and signs up with a name and an email, which is not verified; their questions are logged under that name. Everyone starts with the Everyone profile: questions about the product, answered from the code; a filter removes the code, the file paths and the names of team members it recognises from the answers, without proving their absence, and a leak test tells you what still gets through. An administrator gives the Developers profile (excerpts) or the Leadership profile (developer statistics) to whoever needs it. Repositories are connected from GitHub or GitLab; DeployIt makes no commit, branch or pull request, and only adds one webhook per repository.
Nobody who asks receives a credential on the repository. Each person holds their own token, issued at sign-up, and removing the person cuts their access without touching anyone else's. What gets out depends on the profile, not on the question: the security page lists it, profile by profile.
DeployIt does read your repositories, and you should know on what terms. A working copy of the code is kept while a repository is connected, hosted by DigitalOcean in London (UK); at indexing, each source file is sent to the model to be summarised, then the passages needed for an answer and the diffs of the commits that are scored; OpenAI's models by default, or the provider whose key you bring. Removing a repository from DeployIt erases its copy.
Which route for whom?
- One developer, the code as it stands today: Claude's GitHub integration. Nothing to install, and it stays inside permissions you already manage.
- Developers who want commits, pull requests and issues in their agent: the GitHub MCP server, in read-only mode.
- Support, product, sales and leadership, who ask how the product behaves: an MCP server that answers from the code. Nobody outside engineering gets access to the repository.
The routes combine. A developer keeps the first two; the rest of the company gets the company link. Two questions decide: who will ask, and should that person see code?
One family of questions tips the choice: “What changed since the last release?”, “Why did this behaviour change?”, “Does this week's update affect my integration?”. The first route cannot answer them, and the second answers them commit by commit. With DeployIt, asking what changed this week goes to the recent_changes tool, with no person's name in the answer.
Before you open anything, read how to give AI access to your code safely. The whole product, developer statistics included, is in DeployIt: ask your code from Claude.
To see the third route without connecting anything, add the demo address below to your Claude connectors and ask “What does this product do?”. The table of who sees what, profile by profile, is on the home page.
Price. Free plan: 15 questions a week for the whole company. A 30-day trial, no card. Plans from €290 a month excluding tax for up to 25 tracked developers: see pricing.
Ask your code from Claude
30-day trial, no card. Or try the demo first: add https://mcp.deployit.ai/demo to your Claude connectors.
Frequently asked questions
How do I connect Claude to a GitHub repo?
There are three ways. Claude's GitHub integration syncs the files of one branch into a chat or a project; GitHub's MCP server gives Claude tools over the GitHub API; an MCP server such as DeployIt answers from the code without handing over the repository. Which one fits depends on who will ask, and on what that person should see.
Can Claude read a private GitHub repository?
It can, once access is granted. With Claude's GitHub integration, a GitHub administrator authorises the Claude GitHub app on all repositories or on selected ones; with the GitHub MCP server, Claude acts with the token you give it. With DeployIt, an administrator connects the repositories once, and the people who ask need no GitHub access (checked on 17 November 2026).
Does Claude's GitHub integration read commit history?
It does not. Claude's Help Center states that only the names and contents of the files on a specific branch are synced, without commit history, pull requests or other metadata (checked on 17 November 2026). For questions about what changed, you need a route that reads the history.
Can people who are not developers ask Claude about the repo without seeing the code?
Not through the first two routes: both put file contents in front of the person and assume GitHub access. With DeployIt, they sign up through the company link with the Everyone profile and get answers written from the code; a filter removes the code, the file paths and the names it recognises, and a leak test tells you what still gets through. No filter is infallible.
Does Claude stay up to date when the repo changes?
With Claude's GitHub integration, you click “Sync now” to fetch the latest state of the branch (Claude's help centre, checked on 17 November 2026). The GitHub MCP server reads the API at the time of the question. DeployIt's working copy is updated after each push to the tracked branch.
Continue reading
How to connect Claude to a private GitHub repo without sharing the code
For a CTO: two ways to connect Claude to a private GitHub repo. Claude's own connector hands the files to whoever connects, with that person's GitHub access; one company link gives each person a profile and, with the Everyone profile, answers from which a filter removes the code (filtered and tested). The steps, in order.
MCP server security testing: how a leak test works, and how to read it
For a security lead or a CTO: most MCP server security testing checks who gets in. A leak test checks what gets out: trap questions fired at each profile that must not see code, a sorted report, and a warning that blocks nothing.
DeployIt: ask your code from Claude, and follow each developer's work
For the person who decides, CTO, CEO or head of product: the whole of DeployIt in one read. One link for your company's Claude, answers from the code without giving access to it, statistics on each developer, what happens to your code, and the price.