Ext Ops Panel
Open dashboard
Comparison

io.github.MukundaKatta/jmespath-mcp vs csvql

io.github.MukundaKatta/jmespath-mcp is an MCP server published by MukundaKatta. Marketplaces we read that list it: 1 (Official MCP Registry). csvql is an MCP server published by melihbirim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
Marketplaceio.github.MukundaKatta/jmespath-mcpcsvql
Official MCP Registry Listed
Version: 0.1.0
Downloads/month (npm): 253
Downloads/week (npm): 131
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 2.9.0
Forks (GitHub): 6
Stars (GitHub): 30
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

io.github.MukundaKatta/jmespath-mcp vs csvql
Factio.github.MukundaKatta/jmespath-mcpcsvql
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)30 (better)
Forks (GitHub) (differs)0 (worse)6 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@mukundakatta/jmespath-mcp)On your machine (https://github.com/melihbirim/csvql/releases/download/v2.9.0/csvql-macos-aarch64.mcpb)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/mukundakatta/mcp-stackgithub.com/melihbirim/csvql
Changes in the last 7 days00
First seen2026-10-112026-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

io.github.MukundaKatta/jmespath-mcp

In its own words, on Official MCP Registry:

Run JMESPath queries against JSON. Pure JS, no native binary needed.

csvql

In its own words, on Official MCP Registry:

Query CSV files with SQL via MCP. Fast, local, zero-config, read-only, sandboxable with --root.

How to run each

io.github.MukundaKatta/jmespath-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio jmespath-mcp -- npx -y @mukundakatta/jmespath-mcp

csvql

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

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

Neither one's marketplaces publish the settings it asks for.

What it can do: io.github.MukundaKatta/jmespath-mcp · What it can do: csvql · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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