All servers / Developer / Knip MCP server
Knip MCP server
Knip MCP Server
Tested by ConnectATDScore 94 out of 100. Tested 2026-11-18 on package version 0.0.38. Package: @knip/mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 16 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (6.4 seconds including download)
- Tools offered: 2
- Last published: 2026-11-11
- Weekly downloads (npm): 15,395
- License: ISC · Direct dependencies: 3
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
knip-run2 of 2 parameters describedRun 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-docs1 of 1 parameter describedFetch 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.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.