Ext Ops Panel
Open dashboard
Comparison

gopls-mcp vs jCodeMunch MCP

gopls-mcp is a plugin bundle for AI coding tools published by xieyuschen. 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-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
Marketplacegopls-mcpjCodeMunch MCP
Community marketplace xieyuschen/gopls-mcp Listed
Version: 1.0.8
Forks (GitHub): 6
Stars (GitHub): 60
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

gopls-mcp vs jCodeMunch MCP
Factgopls-mcpjCodeMunch MCP
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)60 (worse)2 817 (better)
Forks (GitHub) (differs)6 (worse)372 (better)
Last release (differs)2026-10-18 (worse)2026-10-29 (better)
Where it runs (differs)Installs as a plugin bundleOn your machine (jcodemunch-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Hooks it runs (differs)1Not published
Parts of the bundle (differs)32
Licence (differs)BSD-3-ClauseLicenseRef-jCodeMunch-Dual-Use-1
Repository (differs)github.com/xieyuschen/gopls-mcpgithub.com/jgravelle/jcodemunch-mcp
Changes in the last 7 days (differs)020 or more
First seen (differs)2026-10-142026-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

gopls-mcp

In its own words, on Community GitHub marketplaces:

Semantic Go code analysis using gopls — type-aware definitions, references, implementations, and call hierarchy.

jCodeMunch MCP

In its own words, on Official MCP Registry:

Retrieves code by symbol via tree-sitter, so an agent reads the function it needs, not the file.

How to run each

gopls-mcp As a Claude Code plugin

Claude Code
/plugin marketplace add xieyuschen/gopls-mcp
/plugin install gopls-mcp@gopls-mcp-marketplace

jCodeMunch MCP As a local MCP server: PyPI package

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

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 gopls-mcp publish no settings it asks for, so we do not compare settings.

What it can do: gopls-mcp · 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.

Where the data comes from: how the catalog is built