webperfect
📷✨ WebPerfect: An intelligent MCP server with a fully automated batch pipeline for web-ready images. Features include noise reduction, auto levels/curves, JPEG artifact removal, 4K resizing, smart sharpening with shadow/highlight enhancement, and advanced WebP conversion. Optimized compression delivers smaller files without sacrificing quality.
claude mcp add --transport stdio punkpeye-webperfect-mcp-server node /path/to/webperfect-mcp-server/build/index.js
How to use
WebPerfect is an MCP server designed to optimize and enhance images for the web using AI-driven processing and advanced image manipulation. It offers a dedicated process_images tool that applies noise reduction, auto levels/curves, texture enhancement, and web-optimized WebP conversion, enabling batch processing of directories and automated workflows. You can access global statistics and presets to tailor the output quality and file size. To use it, add the webperfect server to your MCP configuration (for example in Claude or your MCP runner) and invoke process_images with an inputDir and outputDir. You can also query the server's resources, such as stats/summary, to monitor performance and results. The server is built on Node.js and depends on Sharp for image processing.
Typical workflow: configure the server in your MCP environment, run process_images on a folder of input images, and retrieve the optimized outputs in the designated output folder. You can customize outputs by applying available presets (e.g., web_standard, web_high_quality, thumbnail) to control maxWidth, format, quality, and the set of enhancements applied to each image.
How to install
Prerequisites:
- Node.js >= 16
- npm (Node Package Manager)
- Git
Installation steps:
- Clone the repository:
git clone https://github.com/splendasucks/webperfect-mcp-server.git
cd webperfect-mcp-server
- Install dependencies:
npm install
- Build the server:
npm run build
- Run the server (example):
npm run start
- Optionally configure your MCP tool (e.g., Claude) to point at the built server entry (build/index.js) via the appropriate command and arguments, as shown in the integration example.
Additional notes
Tips and considerations:
- Ensure Node.js version is compatible (>= 16) and that Sharp dependencies are properly installed on your system.
- If you deploy in a container or serverless environment, remember to expose the path to the built entry (index.js) and set any required environment variables in your MCP configuration.
- The provided presets under config/optimization-presets offer quick-start options for common use cases (web_standard, web_high_quality, thumbnail). You can customize these presets or extend them as needed.
- When processing large directories, consider using batch processing and monitoring stats/summary to gauge performance and storage savings.
- If you encounter memory or performance issues, verify that the input images are supported formats and that the system has adequate RAM for large 4K processing tasks.
