mcpbeat Sign in

Dev error explainers MCP Server

local only

Dev error explainers runs on your own machine — the client starts it, so there is no endpoint to ping. 27 installs a week from npm. Last commit 21 Oct 2026.

Offline, deterministic cause and fix for Node, npm, Next.js, CORS and Postgres URL errors.

Installs per day peak 298 · avg 9
a month agotoday
27
Installs / week
npm · dev-error-explainers
0
Stars
2 open issues
21 Oct 2026
Last commit
3 releases in 90 days
MIT
License
JavaScript

What the code does

We read the source, 4 d ago · rules 995398eba69f

Evidence

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

    fix: `rm -rf .next

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

We found things in this code

Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Dev error explainers and you get told the day something new turns up.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add dev-error-explainers -- npx -y dev-error-explainers
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "dev-error-explainers": {
      "command": "npx",
      "args": [
        "-y",
        "dev-error-explainers"
      ]
    }
  }
}
~/.codex/config.toml
[mcp_servers.dev-error-explainers]
command = "npx"
args = ["-y", "dev-error-explainers"]
.cursor/mcp.json
{
  "mcpServers": {
    "dev-error-explainers": {
      "command": "npx",
      "args": [
        "-y",
        "dev-error-explainers"
      ]
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "dev-error-explainers": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "dev-error-explainers"
      ]
    }
  }
}

Alternatives to Dev error explainers

same job, measured the same way
MCP Database Doctor
by petrovicistefan

Offline PostgreSQL query, migration and EXPLAIN diagnostics for AI agents.

44 installs/wk local only
D
Dataxplan MCP
by arikanatakan

Read PostgreSQL EXPLAIN plans for AI agents: bottlenecks, estimation errors, fixes, charts.

96 installs/wk local only
Sqlfmt MCP
by mukundakatta

Deterministic SQL formatting across 19 dialects (postgres, mysql, snowflake, bigquery, etc.).

15 installs/wk local only
pgops
by arzharch

Safe, audited PostgreSQL operations for AI agents: queries, migrations, EXPLAIN, containers

201 installs/wk local only
Veto — SQL Safety & Cost Oracle
by vetosql

Deterministic safety, correctness & cost gate that vets Postgres SQL before your AI agent runs it.

3 tools answering
NeoSQL MCP
by unvus

Schemas, SQL, ERDs, and codegen for PostgreSQL, MySQL, Oracle, SQLite, and more via NeoSQL Desktop.

284 installs/wk local only
WebBase
by webbase

Web hosting your AI runs itself over MCP: deploy sites, Next.js, Postgres, domains. EU servers.

answering
nlqdb — analytical memory for AI agents
by nlqdb

Analytical memory for AI agents: a real Postgres queried in plain English over MCP. One command.

answering

Dev error explainers — questions

Answers built from our own checks of this server.

Why is there no uptime for Dev error explainers?
Dev error explainers runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package dev-error-explainers was installed 27 times last week.
How do I connect Dev error explainers?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls dev-error-explainers straight from npm; nothing to host, nothing to sign up for.
How many people use Dev error explainers?
The npm package dev-error-explainers was installed 27 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Dev error explainers open source?
Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 2 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.