- Home
- MCP servers
- WebP Batch
WebP Batch
- typescript
5
GitHub Stars
typescript
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"mhe8mah-webp-batch-mcp": {
"command": "node",
"args": [
"/path/to/webp-batch-mcp/dist/server.js"
]
}
}
}You can batch-convert images to WebP format using an MCP server that exposes a single tool called convert_to_webp. This server runs locally or via a container, processes images efficiently, and integrates with MCP-aware development environments to streamline your image optimization workflow.
How to use
Start the MCP client and point it to the webp_batch MCP server to convert images to WebP. You can adjust quality, enable lossless mode for PNGs, preserve metadata, and choose how output is organized (alongside originals, overwritten, or all WebP files placed in a separate folder). The server is designed for cross-platform use and can utilize multiple CPU cores for faster batch processing.
How to install
Prerequisites: you need Node.js and npm installed on your machine.
# Global installation
npm install -g webp-batch-mcp
# Local development
git clone https://github.com/mhe8mah/webp-batch-mcp.git
cd webp-batch-mcp
npm install
npm run build
# Docker (optional)
docker build -t webp-batch .
docker run -v /path/to/images:/data webp-batch
Additional configuration and usage notes
If you are adding this MCP server to Cursor or another MCP client, you will run the server locally and register it as an MCP stdio server. The example below shows how to reference the local server that executes the built server script.
{
"mcpServers": {
"webp-batch": {
"command": "node",
"args": ["/path/to/webp-batch-mcp/dist/server.js"]
}
}
}
Tool and behavior details
The MCP server exposes a single tool named convert_to_webp. You can configure the following parameters when calling the tool: source directory, quality (0-100), lossless mode, overwrite, number of threads, metadata preservation, and an optional flat output directory. The server uses a primary engine to perform conversions and falls back to a pure-JavaScript engine if needed. Default behavior is to place WebP files alongside the originals, with optional overwrite or flat output modes.
Available tools
convert_to_webp
Converts input images to WebP format using a primary engine (cwebp) with optional lossless mode and metadata preservation.