Ext Ops Panel
Open dashboard
Comparison

DevHelm MCP Server vs io.github.vish288/mcp-argocd

DevHelm MCP Server is an MCP server published by devhelmhq. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.vish288/mcp-argocd is an MCP server published by vish288. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
MarketplaceDevHelm MCP Serverio.github.vish288/mcp-argocd
Official MCP Registry Listed
Version: 1.0.2
Downloads/month (PyPI): 128
Downloads/week (PyPI): 120
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.5.1
Downloads/month (PyPI): 0
Downloads/week (PyPI): 616
Forks (GitHub): 0
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

DevHelm MCP Server vs io.github.vish288/mcp-argocd
FactDevHelm MCP Serverio.github.vish288/mcp-argocd
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last release (differs)Not published2026-10-14
Where it runs (differs)On your machine (devhelm-mcp-server)On your machine (mcp-argocd)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 15, secrets among them: 2
LicenceNot statedNot stated
Repository (differs)github.com/devhelmhq/mcp-servergithub.com/vish288/mcp-argocd
Changes in the last 7 days (differs)07
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

DevHelm MCP Server

In its own words, on Official MCP Registry:

Monitor uptime, manage incidents, configure alerting, and query dependency status via DevHelm

io.github.vish288/mcp-argocd

In its own words, on Official MCP Registry:

Argo CD MCP server (MCP 2026-07-28): status, sync, rollback, drift, AppSets; writes or read-only

How to run each

DevHelm MCP Server As a local MCP server: PyPI package

Claude Code
claude mcp add --env "DEVHELM_API_TOKEN=<YOUR_DEVHELM_API_TOKEN>" --transport stdio devhelm-mcp-server -- uvx devhelm-mcp-server

Requires: DEVHELM_API_TOKEN (secret)

io.github.vish288/mcp-argocd As a local MCP server: PyPI package

Claude Code
claude mcp add --env "ARGOCD_HTTP_BEARER_TOKEN=<YOUR_ARGOCD_HTTP_BEARER_TOKEN>" --env "ARGOCD_TOKEN=<YOUR_ARGOCD_TOKEN>" --env "ARGOCD_URL=<YOUR_ARGOCD_URL>" --transport stdio mcp-argocd -- uvx mcp-argocd

Requires: ARGOCD_HTTP_BEARER_TOKEN (secret), ARGOCD_TOKEN (secret), ARGOCD_URL

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 DevHelm MCP Server asks for

  • DEVHELM_API_TOKEN (secret)

Only io.github.vish288/mcp-argocd asks for

  • ARGOCD_HTTP_BEARER_TOKEN (secret)
  • ARGOCD_READ_ONLY
  • ARGOCD_TOKEN (secret)
  • ARGOCD_URL
  • MCP_READ_ONLY

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

What it can do: DevHelm MCP Server · What it can do: io.github.vish288/mcp-argocd · 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