All servers / Developer / Rsdoctor MCP server
Rsdoctor MCP server
@rsdoctor/mcp-server 是一个 MCP Server,旨在帮助用户更便捷地使用 Rsdoctor 的构建数据。它可以与 Rsdoctor 的本地构建分析数据配合使用,通过问答的形式,帮助你快速获取构建分析结果。
Tested by ConnectATDScore 70 out of 100. Tested 2026-11-18 on package version 0.1.5. Package: @rsdoctor/mcp-server · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 6 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 14 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (1.0 seconds including download)
- Tools offered: 15
- Last published: 2026-08-07
- Weekly downloads (npm): 4,374
- License: MIT · Direct dependencies: 0
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.
get_chunksno parametersget all chunks
get_chunk_by_id0 of 1 parameter describedget chunk by id
get_module_by_id0 of 1 parameter describedget module detail by id (Rspack or Webpack module id): - id: the id of the module (corresponds to Rspack or Webpack's internal module id) - issuerPath: the referrer chain (array of module ids, from entry to this module) - dependencies: direct dependencies (array of module ids this module imports/requires) - allDependencies: all transitive dependencies (if user asks for detail) - chunks: array of chunk ids this module belongs to - imported: array of module ids that import this module - isEntry: whether this module is an entry point - size: { sourceSize, transformedSize, parsedSize } - layer, modules, rootModule, webpackId: advanced info - bailoutReason: if present, the reason why this module is not tree-shaken or optimized away (e.g. "side effects", "dynamic import", "unknown exports", etc.) - Please use Rspack or Webpack's terminology for all fields. - If user asks for "why not tree-shaken", always return bailoutReason and explain in plain language. - If user asks for "who imported this module", return issuerPath as a dependency chain. - If user asks for "all dependencies", return allDependencies.
get_module_by_path0 of 1 parameter describedget module detail by module name or path (absolute or relative, as in Rspack or Webpack stats) - If multiple modules match, return all matched module paths and stop, let user select. - Otherwise, return the same fields as getModuleById. - Always include bailoutReason if present. - If user asks for "why is this module in the bundle", show the full issuerPath chain. - If user asks for "why not tree-shaken", show bailoutReason and explain.
get_module_issuer_path0 of 1 parameter describedget module issuer path (who imported this module, recursively) - Return as a dependency chain (array of module ids from entry to this module) - If possible, render as a tree or graph for clarity. - For each module in the chain, show its path and (if present) bailoutReason.
get_package_infono parametersget package info
get_package_dependencyno parametersget package dependency
get_rule_infono parametersget rules info, the rules info is a Record<{id: number, name: string, description: string, severity: string, category: string, module: string, path: string, line: number, column: number, message: string, fix: string}>, where: - id: an incremental sequence mark - name: the name of the rule - description: the description of the rule - severity: the severity of the rule - category: the category of the rule - E1001 Duplicate Packages: #### Description there is a same name package which bundled more than one version in your application. it is not good to the bundle size of your application. #### General Solution add an entry in `resolve.alias` which will configure Webpack to route any package references to a single specified path. For example, if `lodash` is duplicated in your bundle, the following configuration would render all Lodash imports to always refer to the `lodash` instance found at `./node_modules/lodash`: ```js { alias: { lodash: path.resolve(__dirname, 'node_modules/lodash') } } ``` , - E1002 Cross Chunks Packages: #### Description There is a package with the same version that is duplicated across different chunks in your application. This redundancy increases the overall bundle size, which is not optimal for performance. #### General Solution To address this issue, you can use Rspack's **SplitChunksPlugin** to extract common dependencies into a separate chunk. This ensures that the same package is not duplicated across multiple chunks, thereby reducing the bundle size. For example, if **lodash** is being duplicated across different chunks, you can configure the **optimization.splitChunks** option in your Webpack configuration to extract **lodash** into a separate chunk: ``` module.exports = { optimization: { splitChunks: { cacheGroups: { commons: { test: /[\/]node_modules[\/]lodash[\/]/, name: 'lodash', chunks: 'all', }, }, }, }, }; ``` This configuration will automatically split out common dependencies (including those from `node_modules`) into separate chunks, ensuring that no package is duplicated across different chunks. - E1004 ECMA Version Check: #### Description This rule is used to detect incompatible advanced syntax. When scanning the rule, the configuration of browserslist is prioritized.
get_similar_packagesno parametersget similar packages. Similar packages are categorized as follows, with each line representing a category of similar packages. The presence of packages below does not necessarily mean there are similar packages - replacement should only be considered when packages from the same category exist: 1. cannot exist simultaneously: lodash、lodash-es、string_decode:Consider migrating to lodash-es for better Tree Shaking support. /n 2. cannot exist simultaneously: dayjs, moment, date-fns, js-joda. Consider using dayjs to replace moment for smaller bundle size. /n 3. cannot exist simultaneously: antd, material-ui, semantic-ui-react, material-ui, arco-design /n 4. cannot exist simultaneously: axios, node-fetch 5. cannot exist simultaneously: redux, mobx, Zustand, Recoil, Jotai 6. cannot exist simultaneously: chalk, colors, picocolors, kleur 7. cannot exist simultaneously: fs-extra, graceful-fs It's fine to have any of the above packages in your project, but packages from the same category (i.e. same line) should not coexist. If there are no similar packages, just return that there are no similar packages, without listing which packages exist. Please provide a simple response without listing all packages.
get_packages_by_package_name0 of 1 parameter describedget similar packages. Similar packages are categorized as follows, with each line representing a category of similar packages. The presence of packages below does not necessarily mean there are similar packages - replacement should only be considered when packages from the same category exist: 1. cannot exist simultaneously: lodash、lodash-es、string_decode:Consider migrating to lodash-es for better Tree Shaking support. /n 2. cannot exist simultaneously: dayjs, moment, date-fns, js-joda. Consider using dayjs to replace moment for smaller bundle size. /n 3. cannot exist simultaneously: antd, material-ui, semantic-ui-react, material-ui, arco-design /n 4. cannot exist simultaneously: axios, node-fetch 5. cannot exist simultaneously: redux, mobx, Zustand, Recoil, Jotai 6. cannot exist simultaneously: chalk, colors, picocolors, kleur 7. cannot exist simultaneously: fs-extra, graceful-fs It's fine to have any of the above packages in your project, but packages from the same category (i.e. same line) should not coexist. If there are no similar packages, just return that there are no similar packages, without listing which packages exist. Please provide a simple response without listing all packages.
get_duplicate_packagesno parametersNo description
get_bundle_optimizeno parametersgetBundleOptimize calls multiple functions to provide conclusions to users: - getRuleInfo for duplicate packages - GetSimilarPackages to check if there are similar packages that need optimization - getMediaAssetPrompt to check if media assets need optimization - GetAllChunks to check if there are oversized resources and provide splitChunk suggestions
get_loader_time_all_filesno parametersGet compilation time spent by each loader on individual files
get_loader_timesno parametersGet compiled directories loader times
get_portno parametersGet the port of the MCP server
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.