@knip/mcp 0.0.14 → 0.0.16

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@knip/mcp",
-  "version": "0.0.14",
+  "version": "0.0.16",
   "description": "Knip MCP Server",
   "type": "module",
   "bin": {
@@ -28,7 +28,7 @@
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.25.1",
     "zod": "^4.1.11",
-    "knip": "^5.80.0"
+    "knip": "^5.81.0"
   },
   "engines": {
     "node": ">=18.18.0"

package/src/docs/docs/blog/for-editors-and-agents.md

@@ -30,8 +30,11 @@ with [3 key features][5]:
 2. **Imports Tree View** for direct links to implementations
 3. **Exports Tree View** for direct links to import & usage locations
 
-Find [Knip on the VS Code Marketplace][6] and find [Knip in the Open VSX
-Registry][7].
+The extension has a [built-in MCP Server][6] with a command and resources to
+configure Knip for you, _completely automated_.
+
+Find [Knip on the VS Code Marketplace][7] and find [Knip in the Open VSX
+Registry][8].
 
 ## MCP Server
 
@@ -40,7 +43,7 @@ coding agent to "configure knip" and it will RTFM so you don't have to. Using a
 newer model like Opus 4.5 or GPT 5.2 results in an optimized `knip.json` file
 and an uncluttered codebase.
 
-The [MCP Server is available][8] separately and built into the VS Code
+The [MCP Server is available][9] separately and built into the VS Code
 Extension.
 
 ## Language Server
@@ -52,25 +55,25 @@ information. Queries like "where is an export imported" or "is this import part
 of a circular dependency" are just scratching the surface here.
 
 Extensions for other IDEs can be built on top. See
-[language-server/README.md][9]
+[language-server/README.md][10]
 
 ## Screenshots
 
 - [Lint Findings][4]
 - [Imports & Exports][5]
-- [Contention][10]
-  - [Circular Dependencies][11]
-  - [Conflicts][12]
-  - [Branching][13]
-- [VS Code Extension Settings][14]
+- [Contention][11]
+  - [Circular Dependencies][12]
+  - [Conflicts][13]
+  - [Branching][14]
+- [VS Code Extension Settings][15]
 
 ### Lint Findings
 
-![Lint Findings][15]
+![Lint Findings][16]
 
 ### Imports & Exports
 
-![hover][16]
+![hover][17]
 
 ### Contention
 
@@ -82,7 +85,7 @@ branched/diamond-shaped import chains.
 
 If an import is part of a circular dependency, Knip will display:
 
-![Circular Dependencies][17]
+![Circular Dependencies][18]
 
 #### Conflicts
 
@@ -90,7 +93,7 @@ TypeScript shows direct conflicts when importing or re-exporting the same named
 export from different files. Except when the problem is more subtle and the
 chain spans more than one file. Knip warns:
 
-![Conflicts][18]
+![Conflicts][19]
 
 #### Branching
 
@@ -98,30 +101,31 @@ Branched or diamond-shaped imports chains indicate unnecessary re-exports and
 complexity. They help to untangle large codebases and shrink or get rid of
 barrel files. Knip warns:
 
-![Branching][19]
+![Branching][20]
 
 ### VS Code Extension Settings
 
-![VS Code Extension Settings][20]
+![VS Code Extension Settings][21]
 
 [1]: https://github.com/webpro-nl/knip/network/dependents
 [2]: https://www.npmjs.com/package/knip
 [3]: #editor-extension
 [4]: #lint-findings
 [5]: #imports--exports
-[6]: https://marketplace.visualstudio.com/items?itemName=webpro.vscode-knip
-[7]: https://open-vsx.org/extension/webpro/vscode-knip
-[8]: https://www.npmjs.com/package/@knip/mcp
-[9]:
+[6]: #mcp-server
+[7]: https://marketplace.visualstudio.com/items?itemName=webpro.vscode-knip
+[8]: https://open-vsx.org/extension/webpro/vscode-knip
+[9]: https://www.npmjs.com/package/@knip/mcp
+[10]:
   https://github.com/webpro-nl/knip/blob/main/packages/language-server/README.md
-[10]: #contention
-[11]: #circular-dependencies
-[12]: #conflicts
-[13]: #branching
-[14]: #vs-code-extension-settings
-[15]: /screenshots/editors-and-agents/diagnostics.webp
-[16]: /screenshots/editors-and-agents/imports-exports.webp
-[17]: /screenshots/editors-and-agents/circular-dependency.webp
-[18]: /screenshots/editors-and-agents/conflict.webp
-[19]: /screenshots/editors-and-agents/branch.webp
-[20]: /screenshots/editors-and-agents/vscode-extension-settings.webp
+[11]: #contention
+[12]: #circular-dependencies
+[13]: #conflicts
+[14]: #branching
+[15]: #vs-code-extension-settings
+[16]: /screenshots/editors-and-agents/diagnostics.webp
+[17]: /screenshots/editors-and-agents/imports-exports.webp
+[18]: /screenshots/editors-and-agents/circular-dependency.webp
+[19]: /screenshots/editors-and-agents/conflict.webp
+[20]: /screenshots/editors-and-agents/branch.webp
+[21]: /screenshots/editors-and-agents/vscode-extension-settings.webp

package/src/docs/docs/features/monorepos-and-workspaces.md

@@ -100,16 +100,31 @@ The following options are available inside workspace configurations:
 Use `--debug` for verbose output and see the workspaces Knip includes, their
 configurations, enabled plugins, glob options and resolved files.
 
-## Lint a single workspace
+## Filter workspaces
 
-Use the `--workspace` (or `-W`) argument to focus on a single workspace (and let
-Knip run faster). Example:
+Use the `--workspace` (or `-W`) argument to select one or more workspaces:
 
 ```sh
 knip --workspace packages/my-lib
 ```
 
-This will include the target workspace, but also ancestor and dependent
+The filter supports multiple formats:
+
+```sh
+knip --workspace @myorg/my-lib     # Package name
+knip --workspace '@myorg/*'        # Package name glob
+knip --workspace packages/my-lib   # Directory path
+knip --workspace './apps/*'        # Directory glob
+```
+
+Combine selectors to include or exclude workspaces:
+
+```sh
+knip --workspace @myorg/* --workspace '!@myorg/legacy'
+knip --workspace './apps/*' --workspace '@shared/utils'
+```
+
+This will include the target workspace(s), but also ancestor and dependent
 workspaces. For two reasons:
 
 - Ancestor workspaces may list dependencies in `package.json` the linted

package/src/docs/docs/guides/configuring-project-files.md

@@ -200,6 +200,6 @@ automatically added as well.
 
 [1]: ../typescript/unused-exports.md
 [2]: ../explanations/entry-files.md
-[3]: ../reference/configuration#ignoreexportsusedinfile
+[3]: ../reference/configuration.md#ignoreexportsusedinfile
 [4]: ../features/production-mode.md
 [5]: ../explanations/plugins.md#entry-files

package/src/docs/docs/guides/handling-issues.mdx

@@ -294,7 +294,7 @@ Some packages have the same name as a Node.js builtin (for instance `buffer` or
 **Solution**: if Knip reports such a dependency as unused, add it to
 [ignoreDependencies][22].
 
-#### Conditional or dynamic dependencies
+### Conditional or dynamic dependencies
 
 Dependencies added conditionally in configuration files may not be detected by
 Knip. This happens because Knip loads and executes config files, and conditional
@@ -586,7 +586,7 @@ To exclude false positives from the report, there are a few options:
 - [Ignore exports used in file][47] for exports used internally.
 - Individual exports can be [tagged using JSDoc syntax][48].
 - Have the export in an entry file:
-  
+
   - Add the file to the `entry` file patterns array in the configuration.
   - Move the export(s) to an entry file.
   - Add the file to the `exports` field of `package.json`

package/src/docs/docs/guides/troubleshooting.md

@@ -90,7 +90,7 @@ a regex that works too:
 
 <img src="/screenshots/trace-dependency.png" alt="trace dependency" class="mw500" />
 
-Use [--workspace \[dir\]][8] to filter accordingly.
+Use [--workspace \[filter\]][8] to filter accordingly.
 
 #### Legend
 
@@ -121,10 +121,10 @@ to [open an issue on GitHub][14].
 [2]: #exceptions-thrown-by-knip
 [3]: #debug
 [4]: #trace
-[5]: ../guides/handling-issues.md
+[5]: ../guides/handling-issues.mdx
 [6]: ./issue-reproduction.md
 [7]: ../reference/known-issues.md
-[8]: ../reference/cli.md#--workspace-dir
+[8]: ../reference/cli.md#--workspace-filter
 [9]: ../explanations/entry-files.md
 [10]: ../explanations/plugins.md
 [11]: ../features/production-mode.md

package/src/docs/docs/overview/features.md

@@ -36,7 +36,7 @@ Also see [related tooling][2].
 | [Strict mode][23]            | Use `--strict` to isolate workspaces and consider only `dependencies` |
 | [Trace][24]                  | Trace exports to find where they are used                             |
 | [Watch mode][25]             | Use `--watch` for live updates of unused files and exports            |
-| [Workspace][26]              | Use `--workspace` to lint a single workspace in a monorepo            |
+| [Workspace][26]              | Use `--workspace` to filter workspaces in a monorepo                  |
 
 [1]: ../reference/issue-types.md
 [2]: ../reference/related-tooling.md
@@ -44,7 +44,7 @@ Also see [related tooling][2].
 [4]: ../reference/cli.md#--cache
 [5]: ../guides/working-with-commonjs.md
 [6]: ../features/compilers.md
-[7]: ../guides/troubleshooting.md#issues-reported-by-knip
+[7]: ../guides/troubleshooting.md#debug
 [8]: ../features/rules-and-filters.md#filters
 [9]: ../features/auto-fix.mdx#format
 [10]: ../reference/jsdoc-tsdoc-tags.md
@@ -63,4 +63,4 @@ Also see [related tooling][2].
 [23]: ../features/production-mode.md#strict-mode
 [24]: ../guides/troubleshooting.md#trace
 [25]: ../reference/cli.md#--watch
-[26]: ../features/monorepos-and-workspaces#lint-a-single-workspace
+[26]: ../features/monorepos-and-workspaces.md#lint-a-single-workspace

package/src/docs/docs/overview/getting-started.mdx

@@ -77,7 +77,17 @@ If the output makes sense to you, feel free to go to the next page:
 
 ## Too Much?
 
-In large or complex codebases the output might be overwhelming. Start by
+In large or complex codebases the output might be overwhelming.
+
+:::tip[NEW]
+
+Use the new [Knip Editor Extension][3] and let your coding agent configure Knip
+for you. The built-in MCP Server will intelligently craft a custom `knip.json`
+based on the documentation and configuration hints.
+
+:::
+
+Start by
 limiting the number of shown issues per type:
 
 <Tabs syncKey="pm">
@@ -108,12 +118,12 @@ limiting the number of shown issues per type:
 
 The output is easier to digest and may include some configuration hints to get
 an idea of what's left to configure. Many unused files? Go to [configuration][2]
-and follow up with [troubleshooting][3] if needed.
+and follow up with [troubleshooting][4] if needed.
 
 :::tip
 
 Do not use the `ignore` option just to get rid of unwanted output. Read
-[Configuring Project Files][4] to get the most out of Knip.
+[Configuring Project Files][5] to get the most out of Knip.
 
 :::
 
@@ -191,5 +201,6 @@ already.
 
 [1]: /playground
 [2]: ./configuration.md
-[3]: ../guides/troubleshooting.md
-[4]: ../guides/configuring-project-files.md
+[3]: ../blog/for-editors-and-agents.md
+[4]: ../guides/troubleshooting.md
+[5]: ../guides/configuring-project-files.md