WebP Conversion MCP Server
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 Conversion MCP Serverconvert this image to webp format"
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 Conversion MCP Server
This project is a Model Context Protocol (MCP) server that converts image files to WebP format.
Features
Convert PNG, JPG, and JPEG files to WebP
Support for single image or batch image conversion
Option to configure quality and lossless compression
Option to keep original files
Provides a detailed report of the conversion result
Installation & Execution
npx -y @xoy8n/webp-converter@latestCursor mcp.json Configuration
{
"mcpServers": {
"webp-converter": {
"command": "npx",
"args": ["-y", "@xoy8n/webp-converter@latest"]
}
}
}Related MCP server: WebP Batch Converter
MCP Tool List
1. convert_to_webp
Converts a single image file to WebP format.
Parameters:
image_path: Path to the image file to convertbase_path: Base directory pathquality: WebP quality setting (default: 95)lossless: Whether to use lossless compression (default: false)keep_original: Whether to retain the original file (default: false)
Returns:
Conversion success status
Input/output file paths
File size before/after conversion
Applied quality and compression settings
2. batch_convert_to_webp
Converts multiple image files to WebP format in one go.
Parameters:
image_paths: Array of paths to image files to convertbase_path: Base directory path (optional)quality: WebP quality setting (default: 95)lossless: Whether to use lossless compression (default: false)keep_original: Whether to retain the original files (default: false)
Returns:
Array of conversion results for each image file
How to Use
Select the image files you want to convert.
Run the
convert_to_webporbatch_convert_to_webpcommand via the MCP tools.Check the conversion results.
License
MIT
Available Tools
2 toolsbatch_convert_to_webpD
| Name | Required | Description | Default |
|---|---|---|---|
| quality | No | ||
| lossless | No | ||
| base_path | No | ||
| image_paths | Yes | ||
| keep_original | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
convert_to_webpD
| Name | Required | Description | Default |
|---|---|---|---|
| quality | No | ||
| lossless | No | ||
| base_path | Yes | ||
| image_path | Yes | ||
| keep_original | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
v1.0.16- First observed
batch_convert_to_webp - First observed
convert_to_webp
TDQS
Scored across 2 tools
Despite lacking descriptions, the names clearly distinguish between single and batch conversion, reducing ambiguity for an agent.
Both tools follow a consistent verb_noun pattern with snake_case ('convert_to_webp', 'batch_convert_to_webp').
With only two tools, the server feels thin for a conversion domain, but it covers the essential single and batch operations.
Basic conversion functionality is present, but missing tools for settings, status, or output management, making it minimally complete.
Maintenance
Related MCP Connectors
Convert images to PNG, JPEG, WebP, or AVIF through one public remote MCP tool.
Convert files between formats without quality loss. Speed up your workflow with fast, reliable con…
Resize, convert, compress, crop, thumbnail and watermark images from your AI chat.
Image toolkit: resize, compress, crop, watermark, convert, rotate, EXIF read/strip.
Related MCP Servers
- AlicenseCqualityDmaintenanceImage Tools MCP is a Model Context Protocol (MCP) service that retrieves image dimensions and compresses images from URLs and local files using the TinyPNG API. It supports converting images to formats like webp, jpeg/jpg, and png, providing detailed information on width, height, type, and compressi29 npm10MIT
- AlicenseAqualityDmaintenanceAn MCP server that enables batch conversion of images to WebP format with configurable options like quality settings, lossless mode, and multi-threading support.16MIT
- AlicenseAqualityDmaintenanceEnables conversion between multiple image formats including JPG, PNG, WebP, GIF, BMP, TIFF, SVG, ICO, and AVIF with quality control and batch processing capabilities.498 npm2MIT
- AlicenseNot gradedqualityDmaintenanceEnables batch image compression and resizing using the TinyPNG API. Supports PNG, JPEG, WebP, and AVIF formats with detailed compression reports and multiple resize modes.7 npm2ISC