GIF Creator MCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@GIF Creator MCPconvert my video.mp4 to a GIF with 15 fps and 480px width"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
GIF Creator MCP
An MCP (Model Context Protocol) server that converts video files to GIF animations.
Features
Convert any video file to GIF format
Customize output settings (FPS, dimensions, duration)
Extract specific portions of videos
High-quality GIF generation with optimized palette
Related MCP server: FFmpeg MCP
Installation
npm install
npm run buildUsage
Right now, Claude Desktop does not support video input. I'd recommend using a different client like Goose and adding it as an extension.
In Goose, you can use the Gif Creator tool by going to Advanced Settings > Extension > + Add Custom Extension > and in the command pasting:
node /path/to/gif-creator-mcp/dist/index.jsI'd also increase the time out to 1000.
For other MCP clients, you can use the following command to start the server:
{
"mcpServers": {
"gif-creator": {
"command": "node",
"args": ["/path/to/gif-creator-mcp/dist/index.js"]
}
}
}Tools
convert_video_to_gif
Converts a video file to a GIF file, saving it in the same directory as the source video.
Parameters:
video_path(required): Path to the video file to convertfps(optional): Frames per second for the GIF (1-30, default: 10)width(optional): Width of the output GIF (maintains aspect ratio if height not specified)height(optional): Height of the output GIF (maintains aspect ratio if width not specified)start_time(optional): Start time in seconds (default: 0)duration(optional): Duration in seconds (default: entire video)
Examples
Basic conversion
{
"video_path": "/path/to/video.mp4"
}Custom settings
{
"video_path": "/path/to/video.mp4",
"fps": 15,
"width": 480,
"start_time": 5,
"duration": 10
}Extract a specific portion
{
"video_path": "/path/to/long-video.mov",
"start_time": 30,
"duration": 5,
"fps": 20
}Requirements
Node.js
FFmpeg (automatically installed via @ffmpeg-installer/ffmpeg)
Notes
The output GIF is saved in the same directory as the input video
The filename is the same as the video file but with a .gif extension
Large videos may take some time to process
The tool uses optimized palette generation for better quality GIFs
License
MIT
Available Tools
1 toolconvert_video_to_gifC
Convert a video file to a GIF file in the same directory
| Name | Required | Description | Default |
|---|---|---|---|
| video_path | Yes | Path to the video file to convert | |
| fps | No | Frames per second for the GIF (default: 10) | |
| width | No | Width of the output GIF (maintains aspect ratio if height not specified) | |
| height | No | Height of the output GIF (maintains aspect ratio if width not specified) | |
| start_time | No | Start time in seconds (default: 0) | |
| duration | No | Duration in seconds (default: entire video) |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the output location but doesn't cover critical behaviors like whether the tool overwrites existing files, handles errors, requires specific permissions, or has performance constraints. For a file conversion tool with zero annotation coverage, this leaves significant gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, clear sentence that efficiently conveys the core functionality without unnecessary details. It's front-loaded with the main action and location, making it easy to understand at a glance.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of a video-to-GIF conversion tool with no annotations and no output schema, the description is incomplete. It lacks information about output format, error handling, file size considerations, and behavioral traits, which are essential for proper tool invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description doesn't add any parameter-specific information beyond what's already in the schema, which has 100% coverage. It mentions the output directory but doesn't explain parameter interactions or defaults. With high schema coverage, the baseline is 3, as the description doesn't compensate but also doesn't detract.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: converting a video file to a GIF file. It specifies the verb 'convert' and the resources involved (video to GIF), and mentions the output location ('in the same directory'). However, it doesn't differentiate from siblings since none exist, so it can't achieve a perfect score of 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, limitations, or scenarios where other tools might be more appropriate. With no sibling tools, this isn't a major issue, but it still lacks explicit usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- First observed
convert_video_to_gif
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as converting video to GIF, leaving no room for confusion or misselection.
A single tool inherently has perfect naming consistency since there are no other tools to compare against. The tool name 'convert_video_to_gif' follows a clear verb_noun pattern, but consistency cannot be assessed across multiple tools.
A single tool for a GIF creator server feels thin and incomplete for the domain. While the tool performs a core function, typical GIF creation workflows might include additional operations like resizing, cropping, adjusting speed, or creating GIFs from images, suggesting the scope is underdeveloped.
The tool set is severely incomplete for a GIF creator domain. It only covers video-to-GIF conversion, missing essential operations such as creating GIFs from image sequences, editing existing GIFs (e.g., trimming, optimizing), or managing output settings (e.g., frame rate, quality). This will likely cause agent failures when broader tasks are required.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Turn words, images, and audio into an animated video with MP4 export.
Convert files between 400+ image, video, audio, document, ebook, archive and font formats.
Run FFmpeg and FFprobe in the cloud: convert, compress, trim and analyze video and audio.
- RendobarOAuthcom.rendobar
Transform video, audio and images, and generate media from prompts. FFmpeg, captions, models.
Related MCP Servers
- -licenseAqualityNot gradedmaintenanceEnables extracting screenshots from video files at specific timestamps or intervals. Supports multiple video formats and output customization including resolution, quality, and format options.4111-
- AlicenseAqualityCmaintenanceEnables video and audio processing through FFmpeg, supporting format conversion, compression, trimming, audio extraction, frame extraction, video merging, and subtitle burning through natural language commands.826MIT
- AlicenseAqualityDmaintenanceProvides video manipulation via ffmpeg (frame extraction, format conversion, trimming, audio adjustments, filters, and subtitle handling) without requiring an external API key.20MIT
- AlicenseNot gradedqualityCmaintenanceTurn words, images, and audio into an animated video with MP4 export.MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ananddtyagi/gif-creator-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server