mcp-gif
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gif_infoA | Get metadata of a GIF file: dimensions, frame count, delays, loop count, and average FPS |
| gif_frameA | Extract a single frame from a GIF as a PNG image |
| gif_frames_listA | List all frames of a GIF with their index, delay (ms), and FPS |
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
gif_info and gif_frames_list both provide delay and FPS information, which could cause confusion, though gif_info is summary metadata while gif_frames_list is per-frame. gif_frame is clearly distinct.
All tools use a consistent gif_ prefix and snake_case, but the second part mixes singular/plural nouns (frame vs frames_list) and uses no explicit verbs, which is a minor deviation from standard verb_noun patterns.
Three tools is a compact set for a focused GIF inspection/extraction server; it's not overly thin and each tool serves a clear purpose, though less comprehensive than larger utilities.
The server covers the core workflow of inspecting a GIF (metadata, frame listing, frame extraction), but lacks batch or creation/editing tools, which are minor gaps for a GIF utility.