MCP Image Resolver
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PEXELS_API_KEY | No | Your Pexels API key | |
| UNSPLASH_ACCESS_KEY | No | Your Unsplash access key |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_imagesB | Search for royalty-free images from Pexels and Unsplash. Supports limit, page, and orientation filters. |
| extract_image_queryA | Transform free-form text (e.g. UI copy, context) into an optimized image search query using noun extraction. |
| get_best_imageC | Return a single best image for a query. |
| search_images_batchA | Run multiple image searches in parallel. Returns results keyed by query. |
| resolve_image_attributionA | Generate provider-compliant attribution text for an image (e.g. Photo by X on Pexels). |
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 5 tools
search_images, get_best_image, and search_images_batch all perform image searches with slight variations, which could confuse an agent trying to pick the right one. The descriptions help clarify the differences, but the overlapping purposes create some ambiguity.
Tool names generally follow a verb_noun pattern (search_images, get_best_image, resolve_image_attribution), with minor inconsistencies like search_images_batch placing the modifier at the end. Overall, the naming is readable and predictable.
With 5 tools, the server is well-scoped for its purpose: image search and attribution. Each tool has a clear role, and the count is neither too sparse nor overwhelming.
The tool surface covers a typical workflow: optimizing a query, searching for images, picking the best one, and generating attribution. Obvious gaps are minor, such as lack of a direct image-by-URL retrieval tool, but the core functionality is solid.