@knip/mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @knip/mcp@0.0.38
Installing a package runs its code. Use a sandbox for anything you have not read.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
knip-run cwd, workspace
Run Knip and return configuration hints and issues. Returns: - totalIssues: Total number of issues found (0 = clean) - configurationHints: Ordered suggestions to improve configuration (address these first) - docs: Doc topics that apply to this result, some with a #section (read them with knip-docs) - knipVersion: Version of Knip that ran (bundled with the MCP Server) - projectKnipVersion: Version of knip installed in the project, if any (versionHint explains a mismatch) - counters: Per-issue-type totals - maybeUnconfigured: true when a high unused-file count suggests entry/project may be incomplete (review configurationHints) - truncated: true when the sample was capped; read counters for totals, or scope with workspace to see the rest - enabledPlugins: Auto-detected plugins per workspace - files: Unused files (sample, might be capped) - issues: Issues per type, i.e. dependencies, exports, types, etc. (sample, capped per type) - configFile: Config file status (exists:false is normal when plugins auto-configure) Options: - cwd: Working directory (defaults to the process cwd) - workspace: Scope run to array of workspaces (to drill into a package when truncated) Iterate: adjust knip.json based on hints, run again until no hints remain and false positives are minimized.
knip-docs topic
Fetch a Knip doc by topic id, or by any docs path. Consult it to resolve a finding, hint, or error instead of guessing. Available topics (use these IDs): - getting-started: New to Knip? Start here for installation and first run - first-cleanup: Guided first pass: read the report top-down and fix one unused file, export, and dependency - how-knip-works: The mental model: entry files, the module graph, reachability, and why findings cascade. Read to reason about any result - configuration: Understand configuration basics, defaults, and file locations - configuration-hints: Decode the configurationHints from knip-run: each hint type and how to resolve it - configuring-project-files: READ FIRST for unused files or false positives. Covers entry/project patterns - handling-issues: How to resolve each issue type: files, dependencies, exports, types, duplicates - known-issues: Errors or unexpected behavior? Check workarounds for common problems - issue-types: Decode knip-run output: every issue type, what it means and its key (files, dependencies, exports, …) - monorepos-and-workspaces: Multi-package repo? Configure workspaces and cross-references here - production-mode: Exclude tests, stories, devDependencies with --production and --strict flags - rules-and-filters: Focus or mute issue types with --include/--exclude and rules - compilers: Using .vue, .svelte, .astro, .mdx files? Configure compilers to parse them - auto-fix: Clean up with --fix: what it removes, related flags, and post-fix steps - jsdoc-tsdoc-tags: Keep an export but exclude it from the report with @public/@internal and custom tags - configuration-reference: Complete reference of all config options: entry, project, ignore, plugins, etc. - cli: All CLI flags, shortcuts, exit codes and environment variables - plugins-explanation: Config files showing as unused? Understand plugin config vs entry files - entry-files: Understand how Knip discovers entry files and default patterns per plugin - plugin-list: Check if a plugin exists for your tool (Jest, Vitest, ESLint, etc.) Full descriptions are registered as MCP resources; any page is also reachable by path (e.g. "guides/troubleshooting"). Append #section to get only that section (e.g. "handling-issues#unused-dependencies"). Use this instead of fetching from https://knip.dev.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | ISC |
|---|---|
| Needs | node ^20.19.0 || >=22.12.0 |
| Source | github.com/webpro-nl/knip |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-+cDC16Ri77gIbUOkxoHWa1GB+Dw66qRzUBKUqhQeJmGrJG8oM3mFXDjr8GPkgk4kZETTITMubXvb4FboszbEdw== |
Proven calls
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40knip/mcp)
New version out? Ask for a fresh report.