electrobun-dev vs Codebase
electrobun-dev is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑20.
electrobun-dev is a plugin bundle for AI coding tools published by Dexploarer. No marketplace we read lists it any more. Codebase is an MCP server published by codebase.design. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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 |  Codebase | |
|---|---|---|
| Community marketplace dexploarer/plugin-electrobun-dev | Removed on 2026-10-20 Version: 1.0.0 Forks (GitHub): 1 Stars (GitHub): 5 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 No figure published 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 | electrobun-devno longer listed · | Codebase |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 5 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (codebase.design/api/mcp) |
| 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) | 40 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dexploarer/plugin-electrobun-dev | Not stated |
| Changes in the last 7 days (differs) | 4 | 2 |
| First seen (differs) | 2026-10-16 | 2026-10-14 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 31 h 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 electrobun-dev
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Assist with Claude Code plugin development: scaffold, validate, review, and team-ready distribution
-
Skills for building on the Cursor Origin API. Fetch the live spec first, then follow the Origin rules for credentials, scopes, webhooks, paging, and errors. Includes a skill that…
-
otakit io.github.OtaKit/otakit
Inspect, upload, release, monitor, and revert OtaKit Capacitor OTA updates.
-
Bun runtime patterns, bunx, shell scripting, lockfile, and testing
-
Model, visualize, and deploy applications with Radius from the GitHub Copilot app and CLI.
-
True Claude Code plugins for Breezeware development — auto-detecting, hook-powered, with skills and code review.
What each says it does
electrobun-dev
Agentic development companion for Electrobun desktop apps — skills, commands, agents, and hooks for the full development lifecycle
Codebase
Let your AI agent build, preview and update web apps, download source and publish when you allow it.
How to run each
electrobun-dev
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Codebase As a remote MCP server
claude mcp add --transport http codebase https://codebase.design/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Codebase 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: electrobun-dev · What it can do: Codebase · 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.