clerk-integration vs CloudBase
clerk-integration is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
clerk-integration is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. 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-10-27. 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 |   CloudBase | |
|---|---|---|
| Community marketplace barnburner121/claude-plugin-marketplace | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.36.1 Downloads/month (npm): 78 741 Downloads/week (npm): 17 379 Forks (GitHub): 148 Stars (GitHub): 1 150 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 2.36.1 Downloads/month (npm): 78 741 Downloads/week (npm): 17 379 Forks (GitHub): 148 Stars (GitHub): 1 150 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 | clerk-integrationno longer listed · | CloudBase |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 3 | 1 150 |
| Forks (GitHub) (differs) | 0 | 148 |
| Last release (differs) | Not published | 2026-10-21 |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| 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 | MIT | MIT |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | github.com/tencentcloudbase/cloudbase-ai-toolkit |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days ago |
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 clerk-integration
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Add authentication and user management with Clerk. Skills for setup, framework patterns, organizations, billing, webhooks, and testing, plus the Clerk MCP server.
-
Comprehensive Clerk authentication expertise across Next.js, React, JavaScript, Node/Express/Fastify, Go, Ruby, Python, Java, .NET, PHP, sessions, JWT templates, organizations…
-
Enterprise-grade auth, easy to implement. Add login, SSO, MFA, and access control to any app with framework-aware guidance.
-
Verify Clerk webhook signatures (Standard Webhooks/Svix), handle user, session, and organization events.
-
WorkOS integration skills for AuthKit, SSO, Directory Sync, RBAC, Vault, Audit Logs, migrations, and API references.
-
Dodo Payments plugin for Better Auth (@dodopayments/better-auth) covering customer sync on signup, authenticated checkout, customer portal, usage ingestion, and verified webhooks…
What each says it does
clerk-integration
Generate Clerk authentication integration
CloudBase
CloudBase MCP: DB, functions, storage, hosting via @cloudbase/cloudbase-mcp
How to run each
clerk-integration
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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: clerk-integration · 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.