cloudxray vs nable
cloudxray is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
cloudxray is a plugin bundle for AI coding tools published by CloudXray AI. No marketplace we read lists it any more. nable is an MCP server published by chaandannn. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-25. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |   nable | |
|---|---|---|
| Community marketplace cloudxrayai/cloudxray-ai | Removed on 2026-10-15 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.8.176 Downloads/month (PyPI): 2 388 Downloads/week (PyPI): 509 Forks (GitHub): 1 Stars (GitHub): 19 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.12.0 Downloads/month (PyPI): 2 388 Downloads/week (PyPI): 509 Forks (GitHub): 1 Stars (GitHub): 19 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
| Fact | cloudxrayno longer listed · | nable |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 0 | 19 |
| Forks (GitHub) (differs) | 0 | 1 |
| Last release (differs) | Not published | 2026-10-18 |
| Where it runs (differs) | Remote server (cloudxray.ai/mcp) | On your machine (finops-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/cloudxrayai/cloudxray-ai | github.com/chaandannn/finopsmcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of cloudxray
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Search and compare 290+ FinOps and cloud cost vendors from the CloudXray AI directory.
-
Cloud cost optimization and FinOps strategies expert
-
FinOps agent MCP: one allocated view of cloud, AI and data costs for your team. Starter $300/mo
-
Prices what your coding agent is about to do before it runs: asks before costly launches and destroys, tracks AI spend, and answers cost questions across AWS, Azure, GCP…
-
Multi-cloud cost, inventory and waste analysis over MCP: AWS, GCP, Cloudflare and OVH.
-
Ask about AWS, Azure, GCP, OpenAI, Anthropic and Snowflake costs, budgets, and anomalies.
What each says it does
cloudxray
Search, compare and shortlist FinOps vendors from the CloudXray AI directory, with a guided vendor-selection skill
nable
Local-first FinOps copilot: ask AWS, Azure, GCP, Kubernetes and SaaS cost questions in your editor.
How to run each
cloudxray
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
nable As a local MCP server: PyPI package
claude mcp add --transport stdio finops-mcp -- uvx finops-mcpCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: cloudxray · What it can do: nable · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.