Ext Ops Panel
Open dashboard
Comparison

Nerdio Manager MCP vs cloudcostwise

Nerdio Manager MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). cloudcostwise is an MCP server published by cloudwise-app. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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
MarketplaceNerdio Manager MCPcloudcostwise
Official MCP Registry Listed
Version: 0.1.4
Forks (GitHub): 13
Stars (GitHub): 59
Not marked · First seen
Listed
Version: 0.1.9
Downloads/month (PyPI): 420
Downloads/week (PyPI): 597
Forks (GitHub): 1
Stars (GitHub): 1
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

Nerdio Manager MCP vs cloudcostwise
FactNerdio Manager MCPcloudcostwise
Marketplaces that list it22
Stars (GitHub) (differs)59 (better)1 (worse)
Forks (GitHub) (differs)13 (better)1 (worse)
Last release (differs)Not published2026-10-15
Where it runs (differs)On your machine (https://github.com/Servosity/msp-skills/releases/download/nerdio-v0.1.4/nerdio-mcp.mcpb)On your machine (cloudcostwise)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)6, secrets among them: 51, secrets among them: 0
Parts of the bundle (differs)Not a bundle1
Licence (differs)Apache-2.0FSL-1.1-ALv2
Repository (differs)github.com/servosity/msp-skillsgithub.com/cloudwise-app/cloudcostwise
Changes in the last 7 days (differs)26
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

Nerdio Manager MCP

In its own words, on Official MCP Registry:

The first non-PowerShell client for the Nerdio Manager for MSP API - cross-account AVD fleet

cloudcostwise

In its own words, on Official MCP Registry:

Find AWS waste with your own read-only credentials. Runs locally. Nothing is sent to CloudWise.

How to run each

Nerdio Manager MCP As a Claude Code plugin

Claude Code
/plugin marketplace add servosity/msp-skills
/plugin install nerdio@msp-skills

Requires: NERDIO_BASE_URL (secret), NERDIO_CLIENT_ID (secret), NERDIO_CLIENT_SECRET (secret), NERDIO_OAUTH_SCOPE (secret), NERDIO_TOKEN_URL (secret)

cloudcostwise As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio cloudcostwise -- uvx cloudcostwise 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

Only Nerdio Manager MCP asks for

  • NERDIO_BASE_URL (secret)
  • NERDIO_CLIENT_ID (secret)
  • NERDIO_CLIENT_SECRET (secret)
  • NERDIO_NO_CONFIG_WRITE
  • NERDIO_OAUTH_SCOPE (secret)
  • NERDIO_TOKEN_URL (secret)

Only cloudcostwise asks for

  • AWS_PROFILE

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

What it can do: Nerdio Manager MCP · What it can do: cloudcostwise · Compare two other plugins

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