intlayer-lsp vs jCodeMunch MCP
intlayer-lsp is a plugin bundle for AI coding tools published by Intlayer. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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). As of our marketplace pass on 2026-10-29. 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
| Marketplace |  jCodeMunch MCP | |
|---|---|---|
| Community marketplace aymericzip/intlayer | Listed Version: 9.7.0 Forks (GitHub): 128 Stars (GitHub): 862 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.108.402 Downloads/month (PyPI): 29 414 Downloads/week (PyPI): 24 526 Forks (GitHub): 372 Stars (GitHub): 2 817 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 1.108.402 Downloads/month (PyPI): 29 414 Downloads/week (PyPI): 24 526 Forks (GitHub): 372 Stars (GitHub): 2 817 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
| Fact | intlayer-lsp | jCodeMunch MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 862 (worse) | 2 817 (better) |
| Forks (GitHub) (differs) | 128 (worse) | 372 (better) |
| Last release (differs) | Not published | 2026-10-29 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (jcodemunch-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Parts of the bundle (differs) | 1 | 2 |
| Licence (differs) | Not stated | LicenseRef-jCodeMunch-Dual-Use-1 |
| Repository (differs) | github.com/aymericzip/intlayer | github.com/jgravelle/jcodemunch-mcp |
| Changes in the last 7 days (differs) | 0 | 20 or more |
| First seen (differs) | 2026-10-15 | 2026-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
intlayer-lsp
Intlayer language server: Go-to-Definition for useIntlayer / getIntlayer / useDictionary / getDictionary keys across all *-intlayer packages
jCodeMunch MCP
Retrieves code by symbol via tree-sitter, so an agent reads the function it needs, not the file.
How to run each
intlayer-lsp As a Claude Code plugin
/plugin marketplace add aymericzip/intlayer
/plugin install intlayer-lsp@intlayerjCodeMunch MCP As a local MCP server: PyPI package
claude mcp add --transport stdio jcodemunch-mcp -- uvx jcodemunch-mcpCommands 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 intlayer-lsp publish no settings it asks for, so we do not compare settings.
What it can do: intlayer-lsp · What it can do: jCodeMunch MCP · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.