e18e

dev.e18ePublished by e18e.devOfficial publisherv0.0.11Updated Nov 2, 2026

The official e18e MCP server keeping your agent in check from installing bloated dependencies.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Official e18e MCP server that lets an assistant flag bloated, outdated or insecure npm packages and suggest lighter alternatives.

What you can do
  • Check install commands (npm i, pnpm add, yarn add, bun i) for packages with better-native or better-maintained alternatives
  • Parse imports in JS/TS/JSX/TSX source files and flag modules that should be replaced
  • Look up replacements for a package by name, replacement text or topic, with descriptions and documentation links
  • List and read curated migration guides for moving away from specific packages
  • Provide a task-oriented prompt that reminds the model to run the checks before replying
When to use it
Useful when an assistant writes or reviews JavaScript/TypeScript code and install commands and you want it to avoid heavy or unmaintained dependencies and suggest leaner replacements.
Requirements
Remote endpoint at mcp.e18e.dev, or a local process via the npm package @e18e/mcp run with npx; Node.js 18 or newer. No authentication, environment variables or headers declared.
Before you install
The code-checker takes a full source file as input, so code is sent to the server for analysis. Suggestions are advisory; review replacements before changing dependencies.

Installation

In SourceWeft

  1. Open e18e in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.e18e%2Fe18e/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "e18e": {
      "type": "http",
      "url": "https://mcp.e18e.dev/mcp"
    }
  }
}

README

@e18e/mcp (STDIO)

MCP server that flags inefficient or outdated npm packages and serves migration docs. It exposes tools for checking install commands or source files, a resource template with curated replacement guides, and a helper prompt for task-oriented workflows.

Capabilities

  • Tools
    • npm-i-checker: Input an install command (npm i, pnpm add, yarn add, bun i). Returns suggestions[] for packages that have better-native or better-maintained alternatives.
    • code-checker: Input a full source file (JS/TS/JSX/TSX). Parses imports and returns suggestions[] when a listed module should be replaced.
  • Resources
    • replacement-docs (template): URI e18e://docs/{slug}. Lists/reads text guides for migrating away from specific packages (auto-complete on slug; list returns all available docs).
  • Prompts
    • task: Returns a task-focused system prompt that reminds the model to run npm-i-checker for installs and code-checker on code before replying.

Quick start

Prereqs: Node.js ≥18 and npm/pnpm (build uses pnpm, runtime works via npx/pnpm dlx/bunx).

The local (or stdio) version of the MCP server is available via the @e18e/mcp npm package. You can either install it globally and then reference it in your configuration or run it with npx:

bash
npx -y @e18e/mcp

Here's how to set it up in some common MCP clients:

Claude Code

To include the local MCP version in Claude Code, simply run the following command:

bash
claude mcp add -t stdio -s [scope] e18e -- npx -y @e18e/mcp

The [scope] must be user, project or local.

Claude Desktop

In the Settings > Developer section, click on Edit Config. It will open the folder with a claude_desktop_config.json file in it. Edit the file to include the following configuration:

json
{	"mcpServers": {		"e18e": {			"command": "npx",			"args": ["-y", "@e18e/mcp"]		}	}}

Codex CLI

Add the following to your config.toml (which defaults to ~/.codex/config.toml, but refer to the configuration documentation for more advanced setups):

toml
[mcp_servers.e18e]command = "npx"args = ["-y", "@e18e/mcp"]

Gemini CLI

To include the local MCP version in Gemini CLI, simply run the following command:

bash
gemini mcp add -t stdio -s [scope] e18e npx -y @e18e/mcp

The [scope] must be user, project or local.

OpenCode

Run the command:

bash
opencode mcp add

and follow the instructions, selecting 'Local' under the 'Select MCP server type' prompt:

bash
opencode mcp add
┌  Add MCP server│◇  Enter MCP server name│  e18e│◇  Select MCP server type│  Local│◆  Enter command to run│  npx -y @e18e/mcp

VS Code

  • Open the command palette
  • Select "MCP: Add Server..."
  • Select "Command (stdio)"
  • Insert npx -y @e18e/mcp in the input and press Enter
  • When prompted for a name, insert e18e
  • Select if you want to add it as a Global or Workspace MCP server

Cursor

  • Open the command palette
  • Select "View: Open MCP Settings"
  • Click on "Add custom MCP"

It will open a file with your MCP servers where you can add the following configuration:

json
{	"mcpServers": {		"e18e": {			"command": "npx",			"args": ["-y", "@e18e/mcp"]		}	}}

Zed

  • Open the command palette
  • Search and select "agent:open settings"
  • In settings panel look for Model Context Protocol (MCP) Servers
  • Click on "Add Server"
  • Select: "Add Custom Server"

It will open a popup with MCP server config where you can add the following configuration:

json
{	"e18e": {		"command": "npx",		"args": ["-y", "@e18e/mcp"]	}}

Other clients

If we didn't include the MCP client you are using, refer to their documentation for stdio servers and use npx as the command and -y @e18e/mcp as the arguments.

Source: packages/stdio/README.md at commit afef52f

Tools

3

code-checker

Check if the code contains some inefficient or outdated packages imported and suggests alternatives.

Check if the code contains some inefficient or outdated packages imported and suggests alternatives.

Parameterscoderequired

lookup-replacement

Check if a package has a more performant, maintained or efficient replacement by package name, replacement text, or topic. Returns a list of suggestions with descriptions and documentation links.

Check if a package has a more performant, maintained or efficient replacement by package name, replacement text, or topic. Returns a list of suggestions with descriptions and documentation links.

Parametersqueryrequired

npm-i-checker

Check for outdated or insecure npm packages in an install script like `npm i` or `pnpm add` or `yarn add` or `bun i`.

Check for outdated or insecure npm packages in an install script like `npm i` or `pnpm add` or `yarn add` or `bun i`.

Parameterscommandrequired

Version history

1
  1. v0.0.11LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts