WebP Batch Converter
Provides containerized deployment of the WebP batch conversion service, allowing users to run the converter in an isolated environment with volume mounting for image processing.
Integrates with Jest for testing the WebP conversion functionality, ensuring reliability of the batch processing capabilities.
Leverages Node.js runtime for the conversion service, providing the foundation for the WebP batch processing engine and MCP server implementation.
Uses Sharp as a fallback image processing engine when Google's cwebp tool is unavailable, providing pure JavaScript implementation for cross-platform WebP conversion without external dependencies.
Built with TypeScript for type safety, enabling more reliable development and maintenance of the WebP conversion codebase.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@WebP Batch Converter convert all images in the photos folder to WebP with 90% quality"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
WebP Batch Converter
A Model Context Protocol (MCP) server for batch converting images to WebP format with cross-platform support. Works seamlessly with MCP-aware IDEs like Cursor.
🌟 Features
🖼️ Batch conversion of PNG, JPG, and JPEG files to WebP
🌍 Cross-platform support (macOS, Linux, Windows)
⚡ Multi-threaded processing for fast conversions
🎛️ Flexible options including quality control, lossless mode, and metadata preservation
📊 Detailed reporting with file sizes and savings statistics
🔧 Dual engine support - prefers Google's cwebp, falls back to Sharp
🎯 MCP integration for use in AI-powered development environments
Related MCP server: @image-converter/mcp
📦 Installation
Global Installation
npm install -g webp-batch-mcpLocal Development
git clone https://github.com/mhe8mah/webp-batch-mcp.git
cd webp-batch-mcp
npm install
npm run buildDocker
docker build -t webp-batch .
docker run -v /path/to/images:/data webp-batch🚀 Usage
Command Line Interface
node dist/cli.js [options]Options
--src <dir>- Source directory to scan (default: current directory)--quality <0-100>- WebP quality setting (default: 75)--lossless- Use lossless encoding (recommended for PNG)--overwrite- Replace original files with WebP versions--threads <n>- Number of concurrent conversions (default: CPU count)--preserve-meta- Preserve EXIF and ICC metadata--flat <dir>- Output all WebP files to specified directory
Examples
# Convert all images in current directory
node dist/cli.js
# High quality conversion of specific directory
node dist/cli.js --src ./photos --quality 95 --preserve-meta
# Lossless conversion with overwrite
node dist/cli.js --src ./images --lossless --overwrite
# Batch process to output directory
node dist/cli.js --src ./input --flat ./output --threads 8MCP Server
The MCP server exposes a single tool: convert_to_webp
Tool Parameters
{
"src": "string", // Source directory (default: ".")
"quality": "number", // Quality 0-100 (default: 75)
"lossless": "boolean", // Lossless mode (default: false)
"overwrite": "boolean", // Replace originals (default: false)
"threads": "number", // Concurrent threads (default: CPU count)
"preserveMeta": "boolean", // Keep metadata (default: false)
"flat": "string" // Output directory (optional)
}⚙️ How to Add This Server in Cursor
Clone and build the project:
git clone https://github.com/mhe8mah/webp-batch-mcp.git
cd webp-batch-mcp
npm install
npm run buildOpen Cursor Settings
Navigate to Features → MCP
Add a new server configuration:
{
"mcpServers": {
"webp-batch": {
"command": "node",
"args": ["/path/to/webp-batch-mcp/dist/server.js"]
}
}
}Restart Cursor
The
convert_to_webptool will be available in your AI conversations
🔧 Technical Details
Conversion Strategy
Primary Engine: Google's
cwebptool (included in libwebp-tools)Fastest performance
Best compression
Full feature support
Fallback Engine: Sharp (Node.js)
Pure JavaScript implementation
No external dependencies
Cross-platform compatibility
Output Behavior
Default: Creates
.webpfiles alongside originalsOverwrite mode: Replaces originals with WebP versions
Flat mode: Outputs all WebP files to specified directory
Metadata preservation: Maintains EXIF and ICC profiles when requested
Performance
Utilizes all CPU cores by default
Processes images concurrently using p-limit
Provides real-time progress feedback
Reports detailed conversion statistics
🛠️ Development
Building
npm run buildTesting
npm testDevelopment Mode
npm run dev📊 Test Results
Verified with real web images:
JPEG (35KB → 17KB): 51% space savings
PNG (7.9KB → 2.8KB): 65% space savings
Overall: 53% average compression
📋 Dependencies
Runtime
@modelcontextprotocol/sdk- MCP server frameworksharp- Image processing fallbackchalk- Colorized terminal outputcommander- CLI argument parsingglob- File pattern matchingp-limit- Concurrency control
Development
typescript- Type safetytsup- Fast TypeScript bundlerjest- Testing framework
📄 License
MIT License - see LICENSE file for details.
🤝 Contributing
Fork the repository
Create a feature branch
Add tests for new functionality
Ensure all tests pass
Submit a pull request
🆘 Support
For issues and feature requests, please use the GitHub issue tracker.
Available Tools
1 toolconvert_to_webpA
Batch convert images (PNG, JPG, JPEG) to WebP format with customizable options. Recursively scans directories and provides detailed conversion reports.
Inputs: src, quality, lossless, overwrite, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as batch converting images to WebP format, making it impossible for an agent to misselect among multiple options.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'convert_to_webp' follows a clear verb_noun pattern, and with no other tools to compare, there are no inconsistencies or deviations in naming conventions.
A single tool is generally too few for a server's purpose, as it limits functionality and can feel thin. For a batch conversion tool, additional operations like listing files, checking formats, or managing settings might be expected to provide a more complete surface, making the count borderline inadequate.
The tool covers the core conversion functionality well, but there are notable gaps in the surface. For a batch conversion domain, missing operations might include checking image formats, listing files before conversion, or providing status updates, which could lead to agent workarounds or inefficiencies in handling the workflow.
Maintenance
Related MCP Connectors
MCP server for Qwen Image 3 AI image generation
Convert images to PNG, JPEG, WebP, or AVIF through one public remote MCP tool.
MCP server for Wan AI video generation
MCP server for Google Veo AI video generation
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA lightweight MCP server for image processing and cloud uploads that automates resizing, converting, optimizing, and uploading images to services like AWS S3, Cloudflare R2, and Google Cloud Storage.14 npm18MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for converting images to AVIF and WebP formats using ImageMagick, with batch conversion and quality control.37 npm1MIT
- AlicenseAqualityCmaintenanceAn MCP server that converts raster images (PNG, JPG, WEBP) to scalable SVG vector graphics.145 PyPI11Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server for converting images to WebP and AVIF formats with batch processing and parallel execution.MIT