Ext Ops Panel
Open dashboard
Comparison

io.github.Dave-London/github vs GitHub PR Context

io.github.Dave-London/github is an MCP server published by Dave-London. Marketplaces we read that list it: 1 (Official MCP Registry). GitHub PR Context is an MCP server published by paarths-collab. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.Dave-London/githubGitHub PR Context
Official MCP Registry Listed
Version: 0.7.1
Downloads/month (npm): 350
Downloads/week (npm): 65
Forks (GitHub): 14
Stars (GitHub): 139
Not marked · First seen
Listed
Version: 0.3.3
Forks (GitHub): 0
Stars (GitHub): 7
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.github.Dave-London/github vs GitHub PR Context
Factio.github.Dave-London/githubGitHub PR Context
Marketplaces that list it11
Stars (GitHub) (differs)139 (better)7 (worse)
Forks (GitHub) (differs)14 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@paretools/github)Not stated
Transport (differs)stdioNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/dave-london/paregithub.com/paarths-collab/github-pr-context-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.Dave-London/github

In its own words, on Official MCP Registry:

MCP server for GitHub operations (PRs, issues, actions) with structured, token-efficient output

GitHub PR Context

In its own words, on Official MCP Registry:

Retrieves GitHub PR history as context material; the connected IDE agent does the reasoning.

How to run each

io.github.Dave-London/github As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio github -- npx -y @paretools/github

GitHub PR Context

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: io.github.Dave-London/github · What it can do: GitHub PR Context · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built