MCP for IIIF Images
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 |
|---|---|
| fetch_iiif_manifestC | Fetch and validate a IIIF manifest from a URL |
| fetch_iiif_imageA | Retrieve a IIIF image from a base URI, fetching info.json and returning the image data scaled to roughly 1M pixels total area. |
| fetch_iiif_image_regionA | Retrieve a specific region of a IIIF image using percentage coordinates, with the region scaled to roughly 1M pixels total area. Use this to fetch regions of interest at higher detail for more accurate image description and analysis. |
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
The tools are mostly distinct: fetch_iiif_image retrieves full images, fetch_iiif_image_region handles specific regions, and fetch_iiif_manifest deals with manifests. However, the first two tools could be confused as both fetch images, though the region variant is clearly specialized for partial extraction.
All tool names follow a consistent verb_noun pattern with 'fetch_iiif_' prefix, using snake_case uniformly. This predictability makes it easy for agents to understand and select the right tool.
With only 3 tools, the set feels thin for a full IIIF image server, lacking operations like listing resources, updating metadata, or handling annotations. While it covers basic fetching, the scope is limited and may require workarounds for common workflows.
The tool surface is severely incomplete for IIIF image handling. It only supports fetching images, regions, and manifests, missing essential CRUD operations such as creating, updating, or deleting resources, and lacks tools for searching or managing collections, which are core to the IIIF domain.