GitHub MCP: connect GitHub to Claude and ChatGPT
Ask Claude or ChatGPT whether the bug a customer reported already has an issue, what’s waiting for your review, or where pull request 412 stands. The answer comes straight from GitHub, with a link to every issue and pull request.
GitHub isn’t only for developers. With Deployed OS everyone connects their own GitHub account, so product, support and management can follow the work from the assistant they already use. The AI reads issues, pull requests, comments and reviews in your company’s organisations, never code, and writes nothing to GitHub.
4 read actions · read-only · Works in Claude, ChatGPT and Copilot
What your team can do with GitHub in Claude and ChatGPT
Is it a known bug?
Follow the work without opening GitHub
Your review queue in one question
Where a release stands, in plain words
Ask it like this
“What’s waiting for my review, and which of my own pull requests are still open?”
“Is there already an issue about the CSV export timing out? If so, what does the latest comment say?”
“Summarise pull request 412 in acme/web-app: the description, who has approved it and who asked for changes.”
“List the open issues labelled customer-request in acme/platform, latest change first.”
“Which pull requests in acme/web-app were closed recently, and were they merged?”
“Find the repository for the customer portal and give me the link.”
What the GitHub MCP connector does today
- Reads
github_searchSearch the issues or the pull requests in your company’s GitHub organisations by words and filters: state, repository, author, assignee and label, with yourself as author or assignee if you like. Latest change first, up to 25.
- Reads
github_get_issueRead one issue or pull request by its repository and number: its text and latest 10 comments. A pull request also comes with its state, branches, change counts, review requests and latest 10 reviews.
- Reads
github_list_my_workList your own open work in your company’s GitHub organisations: issues and pull requests assigned to you, pull requests waiting for your review (through your teams too), and the ones you opened.
- Reads
github_list_repositoriesList the repositories you can see in your company’s GitHub organisations, latest push first, or find them by words in their name, description or topics. Up to 50.
Need it to do more? We extend connectors for the companies that use them.
Who sees what
- Read-only, never code
- The connector reads issues, pull requests, comments, reviews and the list of repositories. It never reads files, diffs or commits, and it cannot comment, review, label, assign or merge.
- Only your organisations
- An admin names your company’s GitHub organisations, up to five, and the AI reads only inside them. Personal repositories and other organisations never reach the AI.
- Each person’s own rights
- Everyone connects their own GitHub account, so the AI sees what that person can see in GitHub. To see private repositories, people need to be members of your organisation.
- You choose who gets it
- Admins decide which groups at the company can use the GitHub connector at all. Everyone else never sees it.
- Every call logged
- Who asked, which connector, when. Deployed OS shows reads per connector and per person, the log can be exported, and access is revoked centrally the day someone leaves.
Set up the GitHub connector in three steps
GitHub’s own MCP server or Deployed OS?
GitHub has its own MCP server, hosted by GitHub or run locally. It covers repositories, code, issues, pull requests, Actions and more, can both read and write, and signs in with OAuth or a personal access token. For a developer who wants GitHub in their editor or assistant, it is a good fit.
Deployed OS is built for the whole team, not only developers. One company connection for GitHub and your other tools, kept to your organisations and to issues and pull requests, with each person on their own GitHub login, admins choosing which groups get GitHub, and a log of every call. The same connection works in Claude, ChatGPT and Copilot, next to your company’s skills and guardrails.
GitHub MCP: common questions
Yes. GitHub has its own MCP server, and it suits a developer well. Deployed OS gives the whole company one connection for GitHub and your other tools, kept to your organisations, with each person’s own login, access per group and a log of every call.
No. The connector only reads: no comments, reviews, labels, assignments or merges. GitHub’s OAuth apps have no read-only permission for private repositories, so the app asks for repo access, but the connector never sends anything other than reads. If you want it to do more, for example comment on issues, we can extend it for you.
No. It reads issues and pull requests with their text, comments and reviews, a pull request’s branches and change counts, and the list of repositories. Files, diffs, commits and inline review comments are never read.
Your admin sets up GitHub in Deployed OS once. You add your company’s Deployed OS connection in Claude, sign in to GitHub with your own account and start asking. The same connection works in ChatGPT and Copilot.
No. The AI uses each person’s own GitHub login, so it sees what they can see in GitHub, and only inside the organisations your admin has named.
Deployed is an EU company and fully GDPR compliant, and you choose where your data is stored, down to the city. GitHub data is fetched when someone asks for it.
It depends on the size of your team. Get in touch and we will walk you through it.
See it on your own tools.
Tell us which systems your company runs on. We’ll show you what your team can ask, and what IT gets to control.
