Think inside your AI world.
How do I connect GitHub to Claude?
GitHub's official MCP server is the ecosystem's heavyweight — 105+ tools across repos, PRs, Actions and security alerts, with a read-only mode when that is all you want.
Direct answer: connect GitHub's official MCP server in Claude — Settings → Connectors, authorise; in Claude Code, 'claude mcp add' (where much of the surface also overlaps native git tooling). Claude then reads repos and code, issues, pull requests with diffs, reviews and comments, commits, Actions runs with logs, code-scanning and Dependabot alerts, and notifications. A read-only mode is available. One practical caveat from the field: very large PR payloads have been known to overwhelm IDE clients — scope big-diff questions accordingly.
The repository, conversational
Why did the nightly workflow fail, what does the open PR actually change, which Dependabot alerts are critical, what merged since the tag — answered from the source of truth with logs and diffs attached. For review work, the PR-with-comments read alone changes the rhythm of the day.
The bar the repo displays but doesn't hold
Worked case: you ratified a merge bar — green CI plus one human review, no exceptions, priced by a hotfix that skipped review and cost a weekend. GitHub renders both status checks and approvals; treating them as a single non-negotiable gate is your policy, and branch-protection settings encode the what without ever carrying the why.
The repo read with the bar attached
Through Unl the PR read arrives judged: CI green, review missing — short of your bar, the one priced by the lost weekend. When someone argues urgency, the rule defends itself with its own history. Same repo, same checks; the standing is what changed.
GitHub to Claude reads the repository in depth; GitHub through Unl reads it against the engineering bars you ratified — the gate arrives carrying the incident that made it a gate.
Reads through Unl arrive with measured context — in the presence of the decisions you’ve already settled. The reach lane is live: one box, paste anything. If it speaks MCP, Unl can reach it. Readings arrive unprompted, the data beside the criterion; Unl is a courier, not a warehouse, and keeps only your keys and the frame.
Read further
Questions people ask
What does the GitHub MCP server expose?
105+ tools: repos and code, issues, PRs (diffs, reviews, comments), commits, Actions runs and logs, code-scanning and Dependabot alerts, notifications. A read-only mode restricts the whole surface to observation.
Is it the same setup for ChatGPT or Cursor?
Yes — 'github mcp' is one official server speaking a shared protocol; every MCP-capable client adds it through its own connector flow.
Branch protection already enforces our merge rules — what does Unl add?
Branch protection enforces mechanics inside GitHub. Unl carries the judgement layer — why the bar exists, when you agreed exceptions are refused — and serves it in any conversation that touches the merge, including the ones where someone proposes disabling the protection.
What if the bar we set no longer fits the code it governs?
Retire it deliberately. Because the bar carries the incident that made it a bar, you can check whether that failure is still possible in the current architecture before you drop it — which is the question that actually decides it, and the one a rule in a wiki cannot answer.
What this is
Think inside your AI world — you stay in command
Save the thoughts, decisions and targets worth keeping, each with its reasoning, carried into every AI session the moment they matter. A new unit of exchange between you and your AI: the Settled Why with standing that travels. Unprompted.
Your whole AI world. What you decided at the epicentre. It plugs into Claude, Claude Code, ChatGPT and Cursor as an MCP connector — quick to connect, in a couple of steps.
MCP native·Human settled·Model agnostic·Your data
Measured Context
Connect Unl to bring the right information into the moment.
Your sources, read against the criteria you set.
The full product, open. Free at launch.