Expose the GitHub integration through MCP

[imshashank]

The gap

Seventy one MCP tools, and not one of them could see a repository. An agent could create a project, a sprint, an issue and a document, but could never associate the code with any of it, and could never find out which pull requests were open against an issue it was working on.

The tools

All four go through the same services the web app uses and the same integration:manage check the REST routes enforce.

Tool
list_github_repositories	Every repository the App is installed on, and what each is associated with
link_github_repository	Associate with a project, or with the workspace when no project is named
unlink_github_repository	Remove one association, leaving the others intact
list_issue_pull_requests	The branches, pull requests and checks linked to an issue

The thing the descriptions have to say out loud

Association does not route anything. applyGithubEvent never reads github_repository_link. It looks the repository up in the watch list, takes the organization off it, and resolves issue identifiers found in the pull request against that whole organization. A pull request in any watched repository links to any issue it names.

So the association is for organising the workspace, not for deciding which issues a repository's pull requests may touch. An agent reading a tool called link_github_repository would reasonably assume the opposite, so every description says which it is.

The genuinely load bearing side effect is that linking calls reconcileWatchedRepositories, and that is what makes events reach Orbit at all. Unlinking the last association stops it. Both descriptions say so.

Answers the shape questions too

github_repository_link is a join table with (repository, project) unique where the project is not null, and a second partial unique on the repository alone where it is. So a project may have many repositories, a repository may serve many projects, and projectId = null is the workspace level association. All three are covered by tests.

Tests

Nine in tests/tools/github.test.ts, including one project with two repositories, one repository in two projects, the workspace level case, that linking actually starts watching, that an unknown repository is refused rather than guessed at, and that a member without integration:manage is refused on both read and write.

Watched failing: unregistering the module fails all nine. Full MCP suite 139 pass, typecheck and every verify guard clean.

Greptile Summary

This PR exposes GitHub repository associations and issue-linked pull requests through four MCP tools.

• Adds tools to list, link, and unlink connected GitHub repositories.
• Adds issue-scoped pull-request lookup using the same authorization model as the existing web API.
• Registers the GitHub tools and adds integration, association, watch-state, and authorization coverage.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
packages/mcp-server/src/tools/github.ts	Adds four GitHub MCP tools with authorization consistent with their corresponding management and issue-reading operations.
packages/mcp-server/src/tools/index.ts	Registers the new GitHub tool module with the MCP server.
packages/mcp-server/tests/tools/github.test.ts	Covers repository discovery, association shapes, watch reconciliation, unknown repositories, unlinking, pull-request lookup, and permission behavior.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A[MCP client] --> B{GitHub tool}
  B --> C[List repositories]
  B --> D[Link repository]
  B --> E[Unlink repository]
  B --> F[List issue pull requests]
  C --> G[integration:manage]
  D --> G
  E --> G
  F --> H[issue:read and team-scoped getIssue]
  C --> I[GitHub catalogue service]
  D --> J[Repository association service]
  E --> J
  F --> K[gitLink records]

Loading

_{Reviews (2): Last reviewed commit: "fix(mcp): pin the permission for reading..." | Re-trigger Greptile}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
orbit	Ready	Preview	Aug 8, 2026 1:19pm

[coderabbitai]

Warning

Review limit reached

@imshashank, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 17 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: a175bdf4-a4fc-4820-83ab-33aa43d5429c

📥 Commits

Reviewing files that changed from the base of the PR and between 66b8f11 and a954211.

📒 Files selected for processing (3)

• packages/mcp-server/src/tools/github.ts
• packages/mcp-server/src/tools/index.ts
• packages/mcp-server/tests/tools/github.test.ts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}