@knip/mcp

What it does

Knip identifies unused dependencies, exports, and files in JavaScript and TypeScript projects through static analysis. The MCP server wraps Knip's capabilities, letting you audit your codebase directly from Claude conversations. Reducing unused code and dependencies improves performance, reduces maintenance burden, and simplifies refactoring.

Who it's for

JavaScript and TypeScript developers and engineering teams managing projects of any size who want to understand their dependency footprint and eliminate dead code. Particularly useful during refactoring cycles, version upgrades, or when modernizing inherited codebases.

Common use cases

• Identify unused npm dependencies that can be safely removed
• Find unreferenced exports and dead code within modules
• Analyze dependency health before a major version upgrade
• Scan inherited codebases to understand maintenance burden
• Generate reports on code bloat for code review discussions

Setup pitfalls

• Filesystem access: Knip reads your entire project structure and can apply fixes; requires read and write permissions on your source tree
• Network connectivity: Needs npm registry access for dependency graph resolution
• Monorepo configuration: Complex monorepos may require explicit Knip configuration for accurate cross-workspace analysis
• Breaking changes: Auto-fixing can remove imports and exports; review all changes before committing