Ext Ops Panel
Open dashboard
Comparison

@tkflyc/ai-cli-mcp vs jCodeMunch MCP

@tkflyc/ai-cli-mcp is an MCP server published by @tkflyc. Marketplaces we read that list it: 1 (npm registry (MCP servers)). 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-11-07. 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
Marketplace@tkflyc/ai-cli-mcpjCodeMunch MCP
npm registry (MCP servers) Listed
Version: 6.9.1
Downloads/month (npm): 1 302
Downloads/week (npm): 1 004
Forks (GitHub): 3
Stars (GitHub): 7
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.108.423
Downloads/month (PyPI): 29 414
Downloads/week (PyPI): 16 534
Forks (GitHub): 373
Stars (GitHub): 2 835
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 1.108.422
Downloads/month (PyPI): 29 414
Downloads/week (PyPI): 16 534
Forks (GitHub): 373
Stars (GitHub): 2 835
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

@tkflyc/ai-cli-mcp vs jCodeMunch MCP
Fact@tkflyc/ai-cli-mcpjCodeMunch MCP
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)7 (worse)2 835 (better)
Forks (GitHub) (differs)3 (worse)373 (better)
Last release (differs)2026-10-20 (worse)2026-11-07 (better)
Where it runs (differs)On your machine (@tkflyc/ai-cli-mcp)On 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
Parts of the bundle (differs)Not a bundle2
Licence (differs)Apache-2.0LicenseRef-jCodeMunch-Dual-Use-1
Repository (differs)github.com/moerasermax/tkflyc-ai-cligithub.com/jgravelle/jcodemunch-mcp
Changes in the last 7 days (differs)020 or more
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

@tkflyc/ai-cli-mcp

In its own words, on npm registry (MCP servers):

Run Claude, Codex, Grok, Antigravity (agy), and any third-party OpenAI-compatible API through MCP with background jobs. Self-maintained, registry-based architecture.

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.

How to run each

@tkflyc/ai-cli-mcp

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

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 @tkflyc/ai-cli-mcp publish no settings it asks for, so we do not compare settings.

What it can do: @tkflyc/ai-cli-mcp · What it can do: jCodeMunch MCP · Compare two other plugins

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). 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