Item detail

github.com

github/github-mcp-server

github/github-mcp-server is a developer tool in RepoRadar's Radar section, holding Gold tier and a 'try now' verdict. Its strongest signal is workflow potential, scored 10.0 out of 10.

Open on GitHub →Back to radar

Score9.0

Popularity86.0

Risknone

TierGold

Score breakdown

Usefulness9.0

Novelty8.0

Momentum9.0

Maturity8.7

Open-source/build8.4

Evidence7.2

Workflow potential10.0

Setup ease6.4

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.

Who should use it

engineering teams that already authenticate against GitHub agent builders that need issue/repo/workflow context teams building custom AI assistants with enterprise GitHub permissions

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. It was first seen on 2026-06-17 and last updated 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. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.

How this item is evaluated

RepoRadar assigned github/github-mcp-server a composite score of 9.0 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 86.0 and never affects the composite score or tier. The risk label of 'none' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.

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.

Evidence links

github.com

Closest alternatives / related signals

mcp github official-server agent-tools automation workflows

Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-08-03T18:56:10Z.

No editorial or hands-on review is claimed. This record remains at Discovered.

Verification sources

Official source ↗ · checked 2026-08-03

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

38 dated snapshots retained from 2026-06-17 through 2026-08-03; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score9.0 current · +0.0 net

Repository momentum9.6 current · +0.6 net

GitHub stars (observed)31,920 current · +518 net

GitHub stars31,920 exact observation

Versionv1.8.0

Last release2026-07-30T13:36:22Z

Maintenanceactive

Current risknone

Current verdicttry now

Pricing baselineNo structured commercial pricing baseline

Pricing checkedNot applicable or not recorded

Pricing freshnessNo dated commercial pricing review

Integrations baselineModel Context Protocol

Recent dated points

Date	Score	Momentum	Stars	Risk	Verdict	Maintenance
2026-08-03	9.0	9.6	31,920	none	try now	active
2026-08-02	9.0	9.6	31,897	none	try now	active
2026-08-01	9.0	9.0	31,881	none	try now	active
2026-07-31	9.0	9.0	Not recorded	none	try now	not recorded
2026-07-30	9.0	9.0	Not recorded	none	try now	not recorded
2026-07-29	9.0	9.6	31,816	none	try now	active
2026-07-28	9.0	9.0	31,786	none	try now	active
2026-07-21	9.0	9.0	31,509	none	try now	active
2026-07-20	9.0	9.0	31,509	none	try now	active
2026-07-19	9.0	9.0	31,509	none	try now	active
2026-07-18	9.0	9.0	31,509	none	try now	active
2026-07-17	9.0	9.0	31,509	none	try now	active

Why the record changed

stars changed2026-08-03

Stars changed: 31897 → 31920.

stars changed2026-08-02

Stars changed: 31881 → 31897.

stars changed2026-08-01

Source-observed stars changed: 31873 → 31881. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed2026-08-01

Source-observed stars changed: 31872 → 31873. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed2026-07-29

Stars changed: 31786 → 31816.

stars changed2026-07-28

Source-observed stars changed: 31779 → 31786. This reports the retained observation delta and does not infer why the upstream change occurred.

version changed2026-07-28

Version changed: v1.6.0 → v1.7.0.

stars changed2026-07-28

Stars changed: 31509 → 31779.

stars changed2026-07-17

Source-observed stars changed: 31508 → 31509. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed2026-07-17

Source-observed stars changed: 31509 → 31508. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed2026-07-17

Stars changed: 31402 → 31509.

version changed2026-07-17

Version changed: v1.5.0 → v1.6.0.