Audit a codebase for redundant dependencies and polyfills
The official e18e MCP server, advising agents on modern and performant JavaScript practices. Task: The official e18e MCP server, advising agents on modern and performant JavaScript practices. It flags inefficient or outdated npm packages and serves migration guides for moving off them. The server is hosted over streamable HTTP at: https://mcp.e18e.dev/mcp Configure your agent Claude Code Run the following command, where [scope] is one of user, project or local: Other clients Refer to your client's documentation for remote (streamable HTTP) servers and use the URL above. Most clients accept a config of this shape: A local stdio version is also available on npm as @e18e/mcp, with per-client setup instructions in the README. What it exposes npm-i-checker: checks an install command (npm i, pnpm add, yarn add, bun i) for packages with better alternatives. code-checker: parses a source file and suggests replacements for the modules it imports. lookup-replacement: looks up replacements by package name, replacement text or topic. replacement-docs: a resource template (e18e://docs/{slug}) serving curated migration guides.; tools: custom-built or unnamed agent. Human role: The original post does not say how a person stayed involved.; limitations: The source does not specify operational costs, latency, or integration constraints beyond the configuration steps. Reliability of the replacement suggestions is not guaranteed, requiring human validation. The server's availability and the accuracy of its curated migration guides are assumed but not independently verified. Users must handle potential false positives in dependency flags..
Tools
custom-built or unnamed agent
Published on Agent Work Atlas:
Overview
The official e18e MCP server, advising agents on modern and performant JavaScript practices.
Workflow
The official e18e MCP server, advising agents on modern and performant JavaScript practices. It flags inefficient or outdated npm packages and serves migration guides for moving off them. The server is hosted over streamable HTTP at: https://mcp.e18e.dev/mcp Configure your agent Claude Code Run the following command, where [scope] is one of user, project or local: Other clients Refer to your client's documentation for remote (streamable HTTP) servers and use the URL above. Most clients accept a config of this shape: A local stdio version is also available on npm as @e18e/mcp, with per-client setup instructions in the README. What it exposes npm-i-checker: checks an install command (npm i, pnpm add, yarn add, bun i) for packages with better alternatives. code-checker: parses a source file and suggests replacements for the modules it imports. lookup-replacement: looks up replacements by package name, replacement text or topic. replacement-docs: a resource template (e18e://docs/{slug}) serving curated migration guides.
Reported result
No measured outcomes or success metrics are reported in the source material. The effectiveness of the dependency audits and the accuracy of suggested replacements remain unverified. A proposed acceptance check would be to measure the reduction in bundle size or the number of deprecated packages removed after applying the agent's suggestions in a controlled test environment.
Human role
The original post does not say how a person stayed involved.
Limitations
The source does not specify operational costs, latency, or integration constraints beyond the configuration steps. Reliability of the replacement suggestions is not guaranteed, requiring human validation. The server's availability and the accuracy of its curated migration guides are assumed but not independently verified. Users must handle potential false positives in dependency flags.
Try it
Act as a JavaScript developer using an agent connected to the e18e MCP server. My goal is to audit a specific project for redundant dependencies. 1. Connect to the e18e MCP server at https://mcp.e18e.dev/mcp using streamable HTTP. 2. Use the `npm-i-checker` tool on the following install command: [replaceable input: e.g., 'npm i lodash moment jquery']. 3. Use the `code-checker` tool on this source file content: [replaceable input: paste relevant JS/TS code snippet]. 4. Retrieve migration guides for flagged packages using `replacement-docs`. 5. Output a report listing: - Original packages flagged. - Suggested modern alternatives. - Specific code changes required. - Links to migration guides. 6. Do NOT apply any changes automatically. Present the report to me for review. 7. Wait for my explicit confirmation before proceeding with any file modifications or package installations. If the server is unreachable, report the error immediately. If a package has no alternative, state 'No replacement found'.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.