GitHub hosts code, pull requests, and issues for nearly every engineering team. Connecting GitHub to clariBI puts repository activity into your AI analyses for engineering velocity and code review insights.
Why connect GitHub
Engineering metrics often span Jira, Linear, GitHub, and CI tools. Pulling them together usually requires custom scripts.
With GitHub connected, you can ask "How many PRs shipped this sprint?", "Find PRs without reviews older than 3 days", or "Compare review time across teams" without leaving clariBI.
How the connection works
clariBI talks to GitHub through its hosted MCP server at https://api.githubcopilot.com/mcp. Authentication uses an OAuth flow against an OAuth app you register in the vendor's developer console. Tokens stay encrypted server-side and never leave clariBI in clear form.
sequenceDiagram
actor U as You
participant C as clariBI
participant V as GitHub
U->>C: Click Authorize with GitHub
C->>V: Open OAuth authorization
V-->>U: Grant read access?
U->>V: Approve
V-->>C: Authorization code
C->>V: Exchange code for tokens
V-->>C: Access + refresh tokens
C->>C: Encrypt and store credentials
C-->>U: Connection ready
Available tools
clariBI exposes the read-only GitHub tools that the vendor's MCP server publishes at connection time. Write operations (create, update, delete, send, refund) are filtered out by a name-pattern blocklist before any tool reaches the analysis engine, so connecting GitHub cannot modify data on the vendor side.
The exact tool inventory depends on the GitHub features your account has access to. After connecting, try a few natural-language questions to see what GitHub data clariBI can pull.
Data flow during analysis
When you ask a question that maps to GitHub, the AI engine routes to the right tool, reads the result, and pairs the answer with a chart you can pin to a dashboard.
sequenceDiagram
actor U as You
participant C as clariBI
participant AI as AI engine
participant V as GitHub
U->>C: Ask a question about repository and PR data
C->>AI: Plan the analysis
AI->>V: Call the right tool
V-->>AI: Tool result
AI->>AI: Summarize and chart
C-->>U: Answer plus visual
Setting up the connection
- Open Data Sources in the clariBI sidebar.
- Click Add data source.
- Open the MCP Servers tab.
- Click the GitHub card.
- Click Authorize with GitHub.
- Sign in to GitHub in the popup window and grant the requested read scopes.
- Back in clariBI, give your data source a name.
- Click Finish.
Permissions and data access
clariBI requests repo, read:org, and read:user scopes. No code can be committed or pushed, no PRs merged, and no issues modified. Disconnect from GitHub account settings or from clariBI Settings.
Troubleshooting
| Error | Cause | Fix |
|---|---|---|
| "Private repo not visible" | Your account does not have access to a referenced private repo. | Confirm repo visibility in GitHub, or use a public repo as a test. |