Ext Ops Panel
Open dashboard
Comparison

doit-cloud-intelligence vs cloudcostwise

doit-cloud-intelligence is a plugin bundle for AI coding tools published by doitintl. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). cloudcostwise is an MCP server published by cloudwise-app. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
Marketplacedoit-cloud-intelligencecloudcostwise
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 1
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.12
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

doit-cloud-intelligence vs cloudcostwise
Factdoit-cloud-intelligencecloudcostwise
Marketplaces that list it11
Stars (GitHub)11
Forks (GitHub)11
Last release (differs)Not published2026-10-16
Where it runs (differs)Remote server (mcp.doit.com/sse)On your machine (cloudcostwise)
Transport (differs)SSEstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Parts of the bundle (differs)5Not a bundle
Licence (differs)MITFSL-1.1-ALv2
Repository (differs)github.com/doitintl/doit-mcp-skillsgithub.com/cloudwise-app/cloudcostwise
Changes in the last 7 days (differs)010
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 2 days ago, requires a keyno remote endpoint we check

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

doit-cloud-intelligence

In its own words, on Claude Code: claude-plugins-community:

Query cloud costs, investigate spending anomalies, and generate reports across AWS, GCP, Azure, Snowflake, and more powered by 40+ DoiT MCP tools with natural language.

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

doit-cloud-intelligence As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install doit-cloud-intelligence@claude-community

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.

Only doit-cloud-intelligence has a remote endpoint we check. How we check endpoints

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 doit-cloud-intelligence publish no settings it asks for, so we do not compare settings.

What it can do: doit-cloud-intelligence · What it can do: cloudcostwise · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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