@knip/mcp

What it does

Knip analyzes JavaScript and TypeScript codebases to identify unused dependencies, exports, and files that can be safely removed. This analysis helps reduce bundle size, simplify maintenance, and make future refactorings easier. The MCP server integration lets Claude query your project's code analysis and provide recommendations for cleanup opportunities.

Who it's for

Frontend and backend engineers managing dependencies in production JavaScript or TypeScript codebases. Especially valuable for teams maintaining monorepos, planning major dependency upgrades, or conducting periodic code audits.

Common use cases

• Identify unused npm dependencies before upgrading package versions
• Find dead code exports and re-export chains across monorepo packages
• Locate orphaned source files no longer imported anywhere in the project
• Verify whether listed dependencies are actually used or can be removed
• Plan removal of transitive dependencies ahead of major version bumps

Setup pitfalls

• Requires filesystem read and write permissions; ensure appropriate sandboxing based on your security model
• May report false positives for dynamic imports, computed require() calls, or plugin systems; manual review of findings is recommended
• Analysis of large monorepos can be time-consuming; test on a subset of packages first
• Requires valid Knip configuration (knip.config.ts or a knip field in package.json) for accurate results