Ext Ops Panel
Open dashboard
Comparison

OpenAPI Swagger MCP vs io.github.vish288/mcp-argocd

OpenAPI Swagger MCP is an MCP server published by nhan7777. 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: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-27. 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
MarketplaceOpenAPI Swagger MCPio.github.vish288/mcp-argocd
Official MCP Registry Listed
Version: 0.1.2
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.5.3
Downloads/month (PyPI): 0
Downloads/week (PyPI): 475
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 0.5.3
Downloads/month (PyPI): 0
Downloads/week (PyPI): 475
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

OpenAPI Swagger MCP vs io.github.vish288/mcp-argocd
FactOpenAPI Swagger MCPio.github.vish288/mcp-argocd
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)2026-10-21 (worse)2026-10-23 (better)
Where it runs (differs)On your machine (@nhan7777/openapi-swagger-mcp)On your machine (mcp-argocd)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published5, secrets among them: 2
Licence (differs)Not statedMIT
Repository (differs)github.com/nhan7777/openapi-swagger-mcpgithub.com/vish288/mcp-argocd
Changes in the last 7 days (differs)32
First seen (differs)2026-10-212026-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

OpenAPI Swagger MCP

In its own words, on Official MCP Registry:

Discover Swagger/OpenAPI operations and call configured dev/UAT APIs through 10 fixed tools.

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

OpenAPI Swagger MCP As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio openapi-swagger-mcp -- npx -y @nhan7777/openapi-swagger-mcp --config "<YOUR_CONFIG>"

Requires: --config

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

The marketplaces of OpenAPI Swagger MCP publish no settings it asks for, so we do not compare settings.

What it can do: OpenAPI Swagger MCP · 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. 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