Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams already living in GitHub who need stable MCP access to repository data and issue/workflow actions without a custom server layer.
Where this stands now
github/github-mcp-server ranks #4 of 3231 tracked Radar items by composite score (9.0 against a section median of 4.9). The section currently carries 2115 Bronze, 645 Gold, 471 Silver. RepoRadar has retained observations for this record since 2026-06-17 (115 days in the current window). Signal extremes versus the section: momentum at the 92th percentile; novelty at the 85th percentile.
Who should use it
Who should skip it
Skip github/github-mcp-server if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
github/github-mcp-server is tracked by RepoRadar as a developer tool in the Radar section. First seen 2026-06-17; the source record was last checked on 2026-06-17. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, github/github-mcp-server is strongest on workflow potential (10.0) and practical usefulness (9.0) and weakest on setup ease (6.4) — a profile worth weighing against your own priorities. 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 github/github-mcp-server record combines a 9.0/10 composite score with separate popularity (86.0), risk (none), and setup (moderate) 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
Any MCP server with write scopes can modify repo state; constrain OAuth scopes and enforce approval checks in callers.