Ext Ops Panel
Open dashboard
Comparison

Next.js DevTools vs Chrome Extension Builder

Next.js DevTools is an MCP server published by kgprs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Chrome Extension Builder is a plugin bundle for AI coding tools published by harry-harish. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-13. 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
MarketplaceNext.js DevToolsChrome Extension Builder
Docker MCP Catalog Listed
Version: sha256:3064e349c266
Forks (GitHub): 1
Pulls (Docker Hub): 54 646
Stars (Docker Hub): 0
Stars (GitHub): 7
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.4.0
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

Next.js DevTools vs Chrome Extension Builder
FactNext.js DevToolsChrome Extension Builder
Marketplaces that list it11
Stars (GitHub) (differs)7 (better)1 (worse)
Pulls (Docker Hub) (differs)54 646No figure on Docker Hub
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/next-devtools-mcp)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)5Not published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)Not published3
Parts of the bundle (differs)Not a bundle19
Licence (differs)Not statedMIT
Repository (differs)github.com/kgprs/next-devtools-mcpgithub.com/harry-harish/chrome-extension-builder
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

Next.js DevTools

In its own words, on Docker MCP Catalog:

next-devtools-mcp is a Model Context Protocol (MCP) server that provides Next.js development tools and utilities for AI coding assistants.

Chrome Extension Builder

In its own words, on Claude Code: claude-plugins-community:

Use when scaffolding, validating, testing, or publishing a Manifest V3 Chrome/Edge/Firefox extension. Builds end-to-end with WXT, Plasmo, or CRXJS — service-worker dispatcher, typed message passing, strict CSP, _locales/ i18n, Playwright smoke harness, Chrome Web Store submission prep.

How to run each

Next.js DevTools As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio next-devtools-mcp -- docker run -i --rm mcp/next-devtools-mcp

Chrome Extension Builder As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install chrome-extension-builder@claude-community

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

Tools each declares

The marketplaces of Chrome Extension Builder publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Next.js DevTools · What it can do: Chrome Extension Builder · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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