AnyCloud vs Eco Router
AnyCloud is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.
AnyCloud is a plugin bundle for AI coding tools published by anycloud. No marketplace we read lists it any more. Eco Router is an MCP server published by stevensu04. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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 |  Eco Router | |
|---|---|---|
| Community marketplace anycloud-sh/anycloud-skills | Removed on 2026-10-16 Version: 0.1.70 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.1 Downloads/month (npm): 152 Downloads/week (npm): 51 Forks (GitHub): 0 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
| Fact | AnyCloudno longer listed · | Eco Router |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) | 1 | 1 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (eco-router-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/anycloud-sh/anycloud-skills | github.com/stevensu04/eco-router-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 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 AnyCloud
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
SkyPilot agent skill for launching cloud VMs, Kubernetes pods, and Slurm jobs across 25+ clouds
-
Deploy and run apps in your own AWS, Google Cloud, Azure or DigitalOcean account from any AI agent.
-
Unified API to query AWS, GCP, Azure and generate Terraform/CLI execution kits for AI agents.
-
Synlake — Cloud Infrastructure for AI Agents
Compare, estimate, and deploy cloud infrastructure across AWS, GCP, and Azure for AI agents.
-
infrastructure
GPU cloud and compute orchestration including Modal, Lambda Labs, and SkyPilot. Use when deploying training jobs or managing GPU resources.
-
Plan a move from AWS, GCP or Azure to Hetzner, DigitalOcean or Vultr with a cost report and draft ru
What each says it does
AnyCloud
Run containerized Jobs, long-running HTTP Services, and persistent VMs across your own AWS, Azure, GCP, and Lambda accounts. Operate workloads, compare GPU prices, recover checkpointed Jobs on spot, and track agent-session spend.
Eco Router
Rank AWS, Google Cloud and Azure regions by grid carbon intensity and latency.
How to run each
AnyCloud
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Eco Router As a local MCP server: npm package
claude mcp add --env "ELECTRICITY_MAPS_API_TOKEN=<YOUR_ELECTRICITY_MAPS_API_TOKEN>" --transport stdio eco-router-mcp -- npx -y eco-router-mcpRequires: ELECTRICITY_MAPS_API_TOKEN (secret)
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 AnyCloud publish no settings it asks for, so we do not compare settings.
What it can do: AnyCloud · What it can do: Eco Router · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.