Ext Ops Panel
Open dashboard
Comparison

jCodeMunch MCP vs sessionwiki

jCodeMunch MCP is an MCP server published by jgravelle. Marketplaces we read that list it: 3 (Official MCP Registry, PyPI (MCP servers), Community GitHub marketplaces). sessionwiki is an MCP server published by necroz. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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
MarketplacejCodeMunch MCPsessionwiki
Official MCP Registry Listed
Version: 1.108.426
Downloads/month (PyPI): 29 414
Downloads/week (PyPI): 16 534
Forks (GitHub): 373
Stars (GitHub): 2 836
Not marked · First seen
Listed
Version: 2.0.5
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
PyPI (MCP servers) Listed
Version: 1.108.424
Downloads/month (PyPI): 29 414
Downloads/week (PyPI): 16 534
Forks (GitHub): 373
Stars (GitHub): 2 836
Not marked · First seen
Not listed

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

jCodeMunch MCP vs sessionwiki
FactjCodeMunch MCPsessionwiki
Marketplaces that list it (differs)3 (better)1 (worse)
Stars (GitHub) (differs)2 836 (better)0 (worse)
Forks (GitHub) (differs)373 (better)0 (worse)
Last release (differs)2026-11-08 (better)2026-11-06 (worse)
Where it runs (differs)On your machine (jcodemunch-mcp)On your machine (sessionwiki)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for1, secrets among them: 01, secrets among them: 0
Parts of the bundle (differs)2Not a bundle
Licence (differs)LicenseRef-jCodeMunch-Dual-Use-1Not stated
Repository (differs)github.com/jgravelle/jcodemunch-mcpgithub.com/necroz/sessionwiki
Changes in the last 7 days (differs)20 or more4
First seen (differs)2026-10-112026-11-06

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

jCodeMunch MCP

In its own words, on Official MCP Registry:

Gives AI agents the function they asked for, not the file. Commercial use needs a license.

sessionwiki

In its own words, on Official MCP Registry:

Search a local wiki compiled from your Claude Code, Codex, Cursor and other AI coding sessions.

How to run each

jCodeMunch MCP As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio jcodemunch-mcp -- uvx jcodemunch-mcp

sessionwiki As a local MCP server: PyPI package

Claude Code
claude mcp add --env "SESSIONWIKI_HOME=<YOUR_SESSIONWIKI_HOME>" --transport stdio sessionwiki -- uvx sessionwiki mcp

Requires: SESSIONWIKI_HOME

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

Only jCodeMunch MCP asks for

  • JCODEMUNCH_SHARE_SAVINGS

Only sessionwiki asks for

  • SESSIONWIKI_HOME

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: jCodeMunch MCP · What it can do: sessionwiki · Compare two other plugins

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