e18e — MCP server for Claude Code: npm dependency checking
Keeps your agent from pulling bloated or dated npm packages: it inspects install commands and imports, then points to replacements.
claude mcp add --transport http e18e https://mcp.e18e.dev/mcpWhat e18e does
The server runs locally over stdio from the @e18e/mcp package and hands the agent two tools. npm-i-checker takes an install line (npm i, pnpm add, yarn add, bun i) and answers with suggestions[] showing which packages have a more native or better maintained option. code-checker takes a whole JS/TS/JSX/TSX file, parses the imports and returns the same list when a module it knows should go.
A resource template called replacement-docs sits alongside, with the URI e18e://docs/{slug}. Give it a slug and you get a text guide for moving off that package; list shows every guide available. There is also a task prompt, a system reminder telling the model to call npm-i-checker for installs and code-checker on code before answering.
Node.js ≥18 is required. Run it through npx (pnpm dlx and bunx work too), though building the package uses pnpm. Claude users can pick a remote endpoint: claude mcp add --transport http e18e https://mcp.e18e.dev/mcp. The stdio route is claude mcp add stdio -- npx -y @e18e/mcp, and you can pass a scope (user, project or local).
What it helps with
- flag a bloated npm package before it lands in dependencies
- spot an outdated module in a file's imports and get a replacement
- read a migration guide for leaving a specific package
- make the agent check installs and code before it replies
Example prompts for the agent
- Run npm-i-checker on
npm i lodash axiosand tell me what should change - Run code-checker over
src/app.tsand name the imports worth replacing - List
e18e://docsand open the migration guide for this package
How to install e18e
1Platform CLI: remote server
claude mcp add --transport http e18e https://mcp.e18e.dev/mcp2Platform CLI
claude mcp add stdio -- npx -y @e18e/mcp1Platform CLI: remote server
codex mcp add stdio --url https://mcp.e18e.dev/mcp2Platform CLI
codex mcp add stdio -- npx -y @e18e/mcpConfig file
{
"mcpServers": {
"stdio": {
"url": "https://mcp.e18e.dev/mcp"
}
}
}{
"mcpServers": {
"stdio": {
"command": "npx",
"args": [
"-y",
"@e18e/mcp"
]
}
}
}Config file
{
"servers": {
"stdio": {
"type": "http",
"url": "https://mcp.e18e.dev/mcp"
}
}
}{
"servers": {
"stdio": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@e18e/mcp"
]
}
}
}1Platform CLI: remote server
gemini mcp add -t http stdio https://mcp.e18e.dev/mcp2Platform CLI
gemini mcp add stdio npx -y @e18e/mcpStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about e18e
How do I install e18e in Claude Code?
For the local stdio server run claude mcp add stdio -- npx -y @e18e/mcp. For the remote endpoint run claude mcp add --transport http e18e https://mcp.e18e.dev/mcp.
What does e18e do?
It reviews npm install commands and imports in JS/TS files, then suggests packages that are more native or better maintained. It also serves migration guides as text.
What do I need to run it?
Node.js ≥18. It starts with npx -y @e18e/mcp, so you do not have to install it globally.