Rsdoctor
io.github.yifancongPublished by GitHub account yifancongv0.1.0Updated Oct 24, 2026
An MCP server that provides build analysis and optimization recommendations for Rspack projects.
Overview
An MCP server that analyzes Rspack builds and suggests optimizations for build performance and artifacts.
- What you can do
- Rsdoctor is a build analyzer for projects built with Rspack. It visualizes compilation behavior and time consumption, and analyzes build artifacts such as resource lists and module dependencies. It also inspects the build process for Loader, Plugin, and Resolver behavior, and applies build rules like duplicate package detection and ES version checks. Users can add custom scan rules based on the build data it collects.
- When to use it
- Use it when working on an Rspack project and you want an assistant to help identify build bottlenecks, inspect module and dependency structure, or review build-time behavior. It is aimed at development teams optimizing build performance and engineering quality.
- Requirements
- Runs locally as a stdio process started with Node.js from the npm package @rsdoctor/mcp-server. It is desktop-only and declares no authentication, environment variables, or headers. It targets Rspack projects; webpack projects are directed to Rsdoctor 1.x or migration to Rspack.
Installation
In SourceWeft
- Open Rsdoctor in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Rsdoctor
[discord channel] [npm version] [downloads] [license]
English | 简体中文
Rsdoctor is a build analysis tool for the Rspack ecosystem. It visualizes the build process and output to help developers investigate build issues and identify performance bottlenecks. It also provides build data to agents for automated diagnosis and optimization of JavaScript programs.
🔥 Features
- Agent-Driven Analysis: Provides build data to agents for automated diagnosis and optimization of JavaScript programs
- Compilation Visualization: Visualize the compilation process and timing to troubleshoot build issues and identify performance bottlenecks
- Comprehensive Analysis: Analyze build output, inspect the build process, and run diagnostic checks:
- Output Analysis: Inspect assets, output sizes, and module dependencies
- Build Process Analysis: Inspect Loader and Plugin execution and module resolution
- Diagnostic Checks: Detect duplicate packages and check ECMAScript syntax versions to identify potential build issues
📚 Getting started
To get started with Rsdoctor, see the Quick Start.
🤝 Contribution
New contributors welcome!
Please read the Contributing Guide.
🧑💻 Community
Come and chat with us on Discord! The Rstack team and users are active there, and we're always looking for contributions.
🦀 Rstack
Rsdoctor is part of Rstack, the fast, unified JavaScript toolchain for developers and agents.
🙌 Code of conduct
This repo has adopted the ByteDance Open Source Code of Conduct. Please check Code of Conduct for more details.
🙏 Credits
Some of the implementation of Rsdoctor refers to the excellent projects in the community, and we would like to thank them:
- bundle-stats is an excellent tool for analyzing build artifacts, and Rsdoctor is inspired by it in terms of build analysis.
- webpack-bundle-analyzer is a classic tool for analyzing Webpack, and Rsdoctor is inspired by it in terms of build artifact analysis. Rsdoctor also uses its classic treemap visualization.
- Statoscope is an excellent tool for analyzing build artifacts, and Rsdoctor is inspired by it in terms of build analysis.
- Webpack Team and Community have created an excellent bundling tool and a rich ecosystem.
- vite-plugin-inspect has inspired Rsdoctor's exploration of build process analysis.
This Rsdoctor website is powered by Netlify.
📖 License
Rsdoctor is licensed under the MIT License.
Source: README.md at commit 039497c
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts