Ext Ops Panel
Open dashboard
Comparison

edgeone-makers-tools vs CloudBase

edgeone-makers-tools is a plugin bundle for AI coding tools published by EdgeOne. Marketplaces we read that list it: 1 (Community GitHub marketplaces). CloudBase is an MCP server published by TencentCloudBase. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-10. 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
Marketplaceedgeone-makers-toolsCloudBase
Community marketplace tencentedgeone/edgeone-makers-tools Listed
Version: 2.0.0
Forks (GitHub): 141
Stars (GitHub): 1 838
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.37.5
Downloads/month (npm): 177 402
Downloads/week (npm): 77 335
Forks (GitHub): 149
Stars (GitHub): 1 164
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 2.37.5
Downloads/month (npm): 177 402
Downloads/week (npm): 77 335
Forks (GitHub): 149
Stars (GitHub): 1 164
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

edgeone-makers-tools vs CloudBase
Factedgeone-makers-toolsCloudBase
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)1 838 (better)1 164 (worse)
Forks (GitHub) (differs)141 (worse)149 (better)
Last release (differs)Not published2026-11-06
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)2Not a bundle
Licence (differs)Not statedMIT
Repository (differs)github.com/tencentedgeone/edgeone-makers-toolsgithub.com/tencentcloudbase/cloudbase-ai-toolkit
Changes in the last 7 days (differs)28
First seen (differs)2026-11-082026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 1 h ago

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

edgeone-makers-tools

In its own words, on Community GitHub marketplaces:

EdgeOne Makers platform development skills — AI Agents, Cloud Functions, Edge Functions, Storage, Middleware, and Deployment.

CloudBase

In its own words, on Official MCP Registry:

CloudBase MCP: DB, functions, storage, hosting via @cloudbase/cloudbase-mcp

How to run each

edgeone-makers-tools As a Claude Code plugin

Claude Code
/plugin marketplace add tencentedgeone/edgeone-makers-tools
/plugin install edgeone-makers-tools@edgeone-makers

CloudBase

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: X-TencentCloud-SecretId header, X-TencentCloud-SecretKey header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only CloudBase 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

Neither one's marketplaces publish the settings it asks for.

What it can do: edgeone-makers-tools · What it can do: CloudBase · 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 public npm registry (registry.npmjs.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