Ext Ops Panel
Open dashboard
Comparison

Next.js DevTools vs ts-react-linter-driven-development

Next.js DevTools is an MCP server published by kgprs. Marketplaces we read that list it: 1 (Docker MCP Catalog). ts-react-linter-driven-development is a plugin bundle for AI coding tools published by Dan Mordechay. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-17. 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 DevToolsts-react-linter-driven-development
Docker MCP Catalog Listed
Version: sha256:3064e349c266
Forks (GitHub): 1
Pulls (Docker Hub): 54 917
Stars (Docker Hub): 0
Stars (GitHub): 7
Not marked · First seen
Not listed
Community marketplace buzzdan/ai-coding-rules Not listed Listed
Version: 2.0.0
Forks (GitHub): 1
Stars (GitHub): 7
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 ts-react-linter-driven-development
FactNext.js DevToolsts-react-linter-driven-development
Marketplaces that list it11
Stars (GitHub)77
Pulls (Docker Hub) (differs)54 917No figure on Docker Hub
Forks (GitHub)11
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
Parts of the bundle (differs)Not a bundle29
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/kgprs/next-devtools-mcpgithub.com/buzzdan/ai-coding-rules
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-15

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.

ts-react-linter-driven-development

In its own words, on Community GitHub marketplaces:

Rules-as-data linter-driven development workflow for TypeScript + React: the Go plugin's 12 rules, thin directional skills and hunter/skeptic/critic review, rendered with TypeScript and React knowledge — ESLint and SonarJS routing, Vitest with React Testing Library and MSW, discriminated unions and readonly types, effects and query ownership, JSDoc

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

ts-react-linter-driven-development As a Claude Code plugin

Claude Code
/plugin marketplace add buzzdan/ai-coding-rules
/plugin install ts-react-linter-driven-development@ai-coding-rules

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

Tools each declares

The marketplaces of ts-react-linter-driven-development 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: ts-react-linter-driven-development · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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