MCP Image Compare Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| compare_imagesA | Compare two local image files pixel by pixel. Supports PNG and JPEG formats. Returns the number of different pixels, percentage difference, and generates a diff image showing the differences. |
| compare_image_with_urlA | Compare a local image file with a screenshot captured from a URL. Takes a screenshot of the webpage and compares it pixel by pixel with the provided image. Returns difference statistics and a diff image. |
| compare_urlsA | Compare screenshots from two different URLs. Captures screenshots of both webpages and compares them pixel by pixel. Returns difference statistics and a diff image showing the visual differences. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: two local files, local file vs URL screenshot, and two URL screenshots. No overlap.
All tools follow a consistent 'compare_' prefix with clear argument differentiation (images, image_with_url, urls).
Three tools cover the essential image comparison scenarios without unnecessary bloat.
The tool set fully covers local-local, local-URL, and URL-URL comparisons. No obvious gaps for typical use cases.