Skip to main content
Glama
geckod22

mcp-gdx-image-webify

by geckod22
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

MCP-GDX-Image-Webify

Node.js npm TypeScript Sharp Modelcontextprotocol

Coverage

Description

MCP-GDX-Image-Webify is an MCP Server (Stdio) based on Node.js and typescript, that allows you to convert images into the WebP or AVIF formats using the sharp library. It supports multiple image formats such as JPG, JPEG, PNG, WebP, TIFF, AVIF, GIF, and SVG. The tool allows you to specify the quality of the conversion and the output directory for the converted images. On result it shows original size, new size and saving.

Related MCP server: Image Worker MCP

Installation

Prerequisites

Node.js NPM

Install

  1. Clone the repository:

git clone https://github.com/geckod22/MCP-GDX-Image-Webify.git
cd MCP-GDX-Image-Webify

  1. Install deps

npm install

  1. Build

npm run build

MCP Client configuration

Just run:

npm run installToClients

then follow the steps.

At the moment the script supports the following clients: Claude Desktop, Gemini Cli, Visual Code

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "node",
      "args": ["your_path\\MCP-GDX-Image-Webify\\build\\index.js"]
    }
  }
}

Follow the MCP install guide, and use the above general config.

Click the button to install:

Go to Cursor Settings -> MCP -> New MCP Server. Use the General config above.

Follow the MCP guide and use the standard config from above.

Your first prompt

Ex of usage. Open your project folder and run gemini cli, then Enter the following prompt to check if everything is working:

Convert the images in the current project images folder to webp with quality 80.

Testing

Run the Inspector:

npx @modelcontextprotocol/inspector node build/index.js

Contributing

Contributions are welcome! Feel free to open issues or submit pull requests to improve the project.

License

This project is licensed under the MIT License.

Credits

This project uses Sharp for high-performance image processing, licensed under the Apache License 2.0.

Available Tools

1 tool
gdx-image-webifyB

A tool to convert images to different formats using sharp. Convert from .jpg, .jpeg, .png, .webp, .tiff, .avif, .gif, .svg to webp, avif.

ParametersJSON Schema
NameRequiredDescriptionDefault
filesYesAn array of image paths. You can provide specific file paths, or use glob patterns like "C:/images/*.png" to select multiple files at once.Should be images with the following formats: .jpg, .jpeg, .png, .webp, .tiff, .avif, .gif, .svg
toPathNoDestination folder. If omitted, uses the original file directory.
qualityNoThe quality of the conversion
toFormatYesThe format to convert the images to: webp or avif
forceOverwriteNoSAFETY CHECK: Must be false by default. If a file exists, the tool will fail/skip. ONLY set to true if the user explicitly says "yes" or "overwrite" in their last message.

TDQS

B3.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must disclose behavioral traits. It merely states conversion capabilities and does not mention overwrite behavior, quality handling, error conditions, or whether original files are preserved. The safety-related forceOverwrite parameter is not referenced, leaving significant gaps for a tool that writes files.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core action. It is efficient, readable, and uses no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a conversion tool with 5 parameters including the safety-critical forceOverwrite, the description is minimal. It lacks information about behavior, limitations, return values, and usage context, making it incomplete for an agent to safely operate the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description reiterates formats that are already documented in the schema but does not add any parameter-specific semantics beyond what the schema already covers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool converts images to different formats using sharp, specifying supported input formats (.jpg, .jpeg, .png, .webp, .tiff, .avif, .gif, .svg) and output formats (webp, avif). It is specific and action-oriented, leaving no doubt about the tool's function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when image format conversion to webp/avif is needed, but it provides no explicit guidance on when to use this tool versus alternatives, prerequisites, or edge cases. With no siblings listed, a clear use-case statement is missing, though the conversion purpose is evident.

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.

  1. 1 tool updatev1.0.0
    • First observedgdx-image-webify
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusing it with others.

Naming Consistency5/5

The tool name 'gdx-image-webify' is descriptive and unambiguous; as the sole tool, naming consistency is trivially satisfied.

Tool Count3/5

With only a single tool, the server feels thin for a general-purpose image conversion utility, but it is appropriate for a focused 'webify' use case.

Completeness5/5

The tool covers all listed input formats and two output formats, fully supporting the webify purpose. There are no obvious missing operations for the stated scope.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers