Ext Ops Panel
Open dashboard
Comparison

io.github.codespar/mcp-chargebee vs Sherweb

io.github.codespar/mcp-chargebee is an MCP server published by codespar. Marketplaces we read that list it: 1 (Official MCP Registry). Sherweb is an MCP server published by wyre-technology. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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.codespar/mcp-chargebeeSherweb
Official MCP Registry Listed
Version: 0.1.2
Downloads/month (npm): 92
Downloads/week (npm): 21
Forks (GitHub): 51
Stars (GitHub): 274
Not marked · First seen
Listed
Version: 1.4.3
Forks (GitHub): 1
Stars (GitHub): 0
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.codespar/mcp-chargebee vs Sherweb
Factio.github.codespar/mcp-chargebeeSherweb
Marketplaces that list it11
Stars (GitHub) (differs)274 (better)0 (worse)
Forks (GitHub) (differs)51 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@codespar/mcp-chargebee)On your machine (ghcr.io/wyre-technology/sherweb-mcp:v1.4.3)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 16, secrets among them: 2
LicenceNot statedNot stated
Repository (differs)github.com/codespar/mcp-dev-latamgithub.com/wyre-technology/sherweb-mcp
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.codespar/mcp-chargebee

In its own words, on Official MCP Registry:

MCP server for Chargebee — global subscription billing, recurring revenue orchestration

Sherweb

In its own words, on Official MCP Registry:

MCP server for Sherweb — billing, subscriptions, customers, and product catalog.

How to run each

io.github.codespar/mcp-chargebee As a local MCP server: npm package

Claude Code
claude mcp add --env "CHARGEBEE_API_KEY=<YOUR_CHARGEBEE_API_KEY>" --env "CHARGEBEE_SITE=<YOUR_CHARGEBEE_SITE>" --transport stdio mcp-chargebee -- npx -y @codespar/mcp-chargebee

Requires: CHARGEBEE_API_KEY (secret), CHARGEBEE_SITE

Sherweb As a local MCP server: Docker image

Claude Code
claude mcp add --env "SHERWEB_CLIENT_ID=<YOUR_SHERWEB_CLIENT_ID>" --env "SHERWEB_CLIENT_SECRET=<YOUR_SHERWEB_CLIENT_SECRET>" --env "SHERWEB_SUBSCRIPTION_KEY=<YOUR_SHERWEB_SUBSCRIPTION_KEY>" --transport stdio sherweb-mcp -- docker run -i --rm -e SHERWEB_CLIENT_ID -e SHERWEB_CLIENT_SECRET -e SHERWEB_SUBSCRIPTION_KEY ghcr.io/wyre-technology/sherweb-mcp:v1.4.3

Requires: SHERWEB_CLIENT_ID, SHERWEB_CLIENT_SECRET (secret), SHERWEB_SUBSCRIPTION_KEY (secret)

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 io.github.codespar/mcp-chargebee asks for

  • CHARGEBEE_API_KEY (secret)
  • CHARGEBEE_SITE

Only Sherweb asks for

  • AUTH_MODE
  • LOG_LEVEL
  • MCP_TRANSPORT
  • SHERWEB_CLIENT_ID
  • SHERWEB_CLIENT_SECRET (secret)
  • SHERWEB_SUBSCRIPTION_KEY (secret)

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

What it can do: io.github.codespar/mcp-chargebee · What it can do: Sherweb · 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