This ships the project's actual licence
Every artifact published before this one — 0.3.0, 0.3.1 and 0.3.2 — bundled the upstream Model Context Protocol project's LICENSE instead of this project's. They carry the Apache-2.0 text and a licensing-transition notice about a different project, while the README says MIT.
It arrived by accident: the correct MIT licence was added in f78e00c and overwritten by the v0.3.0 release commit 6561a8e. This restores that exact file, so it is a correction, not a relicence.
PyPI releases are immutable, so a new version is the only way to get the correct licence to users. If you installed 0.3.2 or earlier, the LICENSE on your disk is wrong — upgrade.
Licence metadata
The package previously declared no licence at all, which is why PyPI showed none. It now ships PEP 639 metadata:
License-Expression: MIT
License-File: LICENSE
Documentation
The README is a landing page rather than the whole manual — 417 words and two diagrams, down from 853 words and thirteen. Detail moved to the page that already owned each subject:
| Page | Covers |
|---|---|
| Architecture | Retrieval/reasoning split, what gets indexed, trust boundary |
| Authentication | Device Flow handshake, connection state machine |
| Indexing and storage | Job states, page caps, webhook, storage modes, limits |
| Tools | Tool surface and when to reach for each |
Removed
The benchmarks/ directory and its replay harness. The benchmark found no statistically demonstrated effect across ten merged PRs — too little to conclude anything either way — so keeping the apparatus implied a claim the data did not support.
Upgrade
uvx github-pr-context-mcpNothing to reconfigure. If you are coming from 0.2.x, note that 0.3.2 was the first release in which PR indexing worked at all; earlier versions shipped a GraphQL query GitHub rejected outright.
Full changelog: https://github.com/paarths-collab/github-pr-context-mcp/blob/main/CHANGELOG.md