mcp-gifs
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CACHE_TTL_SECONDS | No | Cloudflare Workers self-host setting: result cache TTL in seconds (default 600). | 600 |
| RATE_LIMIT_GLOBAL | No | In-memory global rate limit for self-hosters on other platforms (requests per 60 s; unset or 0 disables). Off by default and not set on the public deployment. | |
| RATE_LIMIT_PER_IP | No | In-memory per-IP rate limit for self-hosters on other platforms (requests per 60 s; unset or 0 disables). Off by default and not set on the public deployment. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Find openly licensed animated GIFs by keyword. Results come from Wikimedia Commons (primary) and Openverse (fallback); they skew documentary/educational rather than meme-style. Always show the attribution line with any GIF you display.
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_gifsA | Search openly licensed animated GIFs by keywords (e.g. "cat", "rocket launch", "dancing"). Returns direct GIF URLs, preview URLs, dimensions, license and a ready-made attribution string. English keywords work best. |
| get_gifA | Fetch full details for one GIF by the id returned from search_gifs (e.g. "wikimedia:File:Foo.gif" or "openverse:"). |
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 2 tools
search_gifs and get_gif have clearly distinct purposes: one discovers GIFs by keyword, the other retrieves details for a specific GIF ID. There is no meaningful overlap that would cause misselection.
Both tools follow a consistent snake_case verb_noun pattern: search_gifs and get_gif. The singular/plural difference reflects the natural distinction between searching many GIFs and fetching one.
With only two tools, the surface feels thin even for a focused GIF server. Basic discovery is covered, but additional lightweight operations like trending or random GIF retrieval are absent.
The core workflow—search for GIFs and inspect a specific result—is fully covered. Minor gaps such as trending/popular lists or random selection can be worked around via keyword searches.