Ext Ops Panel
Open dashboard
Comparison

Next.js DevTools vs web3ctx

Next.js DevTools is an MCP server published by kgprs. Marketplaces we read that list it: 1 (Docker MCP Catalog). web3ctx is an MCP server published by FarseenSh. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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 DevToolsweb3ctx
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
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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 web3ctx
FactNext.js DevToolsweb3ctx
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)7 (better)0 (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)Remote server (mcp.scarai.xyz/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)5Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle2
Licence (differs)Not statedMIT
Repository (differs)github.com/kgprs/next-devtools-mcpgithub.com/farseensh/web3ctx
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-13

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.

web3ctx

In its own words, on Official MCP Registry:

Version-true web3 docs, ABIs and human-validated integration recipes over MCP.

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

web3ctx As a remote MCP server

Claude Code
claude mcp add --transport http web3ctx https://mcp.scarai.xyz/mcp

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

Only web3ctx has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of web3ctx 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: web3ctx · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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