Ext Ops Panel
Open dashboard
Comparison

Jev for coding agents vs io.github.James-Chahwan/repo-graph

Jev for coding agents is a plugin bundle for AI coding tools published by François Chastel. Marketplaces we read that list it: 2 (Community GitHub marketplaces, npm registry (MCP servers)). io.github.James-Chahwan/repo-graph is an MCP server published by James-Chahwan. Marketplaces we read that list it: 3 (Official MCP Registry, PyPI (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-10-30. 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
MarketplaceJev for coding agentsio.github.James-Chahwan/repo-graph
npm registry (MCP servers) Listed
Version: 0.5.0
Downloads/month (npm): 2 766
Downloads/week (npm): 1 020
Forks (GitHub): 7
Stars (GitHub): 55
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.5.2
Downloads/month (PyPI): 1 097
Downloads/week (PyPI): 234
Forks (GitHub): 1
Stars (GitHub): 87
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 0.5.2
Downloads/month (PyPI): 1 097
Downloads/week (PyPI): 234
Forks (GitHub): 1
Stars (GitHub): 87
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

Jev for coding agents vs io.github.James-Chahwan/repo-graph
FactJev for coding agentsio.github.James-Chahwan/repo-graph
Marketplaces that list it (differs)2 (worse)3 (better)
Stars (GitHub) (differs)55 (worse)87 (better)
Forks (GitHub) (differs)7 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@french-castle/jev-code)On your machine (mcp-repo-graph)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Parts of the bundle (differs)21
LicenceMITMIT
Repository (differs)github.com/francoischastel/jev-codegithub.com/james-chahwan/repo-graph
Changes in the last 7 days00
First seen (differs)2026-10-122026-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

Jev for coding agents

In its own words, on Community GitHub marketplaces:

jev_classify, jev_check, jev_score, jev_rank, jev_ask over MCP, plus the /jev skill.

io.github.James-Chahwan/repo-graph

In its own words, on Official MCP Registry:

Structural graph map of any codebase so LLMs navigate by structure, not guesswork.

How to run each

Jev for coding agents As a Claude Code plugin

Claude Code
/plugin marketplace add francoischastel/jev-code
/plugin install jev-code@jev-code

io.github.James-Chahwan/repo-graph As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio repo-graph -- uvx mcp-repo-graph

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

The marketplaces of Jev for coding agents publish no settings it asks for, so we do not compare settings.

What it can do: Jev for coding agents · What it can do: io.github.James-Chahwan/repo-graph · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Package data comes from the public npm registry (registry.npmjs.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). 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