Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
That matters because GitHub MCP is much more useful when a developer can stand it up quickly with the credentials they already use, rather than hunting down and managing separate personal access tokens for every test.
Where this stands now
shuymn/gh-mcp ranks #169 of 2770 tracked Radar items by composite score (8.5 against a section median of 4.9). The section currently carries 1659 Bronze, 645 Gold, 466 Silver. RepoRadar has retained observations for this record since 2026-06-19 (106 days in the current window). Signal extremes versus the section: momentum at the 72th percentile.
Who should use it
Who should skip it
Pass on shuymn/gh-mcp if its scope or audience does not match what your team is building right now.
About this signal
shuymn/gh-mcp is tracked by RepoRadar as a developer tool in the Radar section. First seen 2026-06-19; the source record was last checked on 2026-06-19. The current verdict is 'try now' with a Gold tier and easy setup difficulty. shuymn/gh-mcp leads on workflow potential (10.0) and practical usefulness (9.0); its lowest signal is momentum (7.0), so factor that in before investing setup time. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The shuymn/gh-mcp record combines a 8.5/10 composite score with separate popularity (66.0), risk (conditional), and setup (easy) signals. See the scoring methodology for the current weights and evidence definitions.
Questions worth asking before you adopt this
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
This extension reuses your authenticated GitHub CLI session, so verify which account and repo permissions are active before letting an agent use it for write actions.