video2gif
# MCP 合集
一个 MCP 服务集合，每个 MCP 各自独立，放在自己的子目录里，互不干扰。新增 MCP 时在下方登记一行即可。
> 新增 / 修改 MCP 前，请先读 **[AGENTS.md](AGENTS.md)**（AI 维护规范总入口），详细规范拆分在 [aiDoc/](aiDoc/) 目录。
## 目录结构
```
MCP/
├── video2gif/ # 视频链接 → GIF 动图
└── ... # 更多 MCP（待补充）
```
## MCP 列表
| MCP | 说明 | 入口 / 文档 |
|-----|------|-------------|
| **video2gif** | 把视频链接转成 GIF 动图（含 SSRF 防护），供魔搭 / 钉钉 DEAP / Claude Code 等 MCP 客户端调用 | [video2gif/README.md](video2gif/README.md) |
## 使用
进入对应子目录后按其 README 安装 / 运行即可。以 video2gif 为例：
```bash
cd video2gif
uvx --from . video2gif-mcp
# 或 pip install . && video2gif-mcp
```
TDQS
Scored across 1 tool
With only one tool in the server, there is no possibility of confusing it with other operations. The tool's purpose is singular and clearly described.
The single tool name 'video_to_gif' clearly conveys its function and uses a simple, readable convention. Since there is only one tool, naming consistency is trivially maintained.
A single tool is on the low end of the typical range. For a narrowly scoped service like video-to-gif conversion, one tool may be acceptable, but it feels minimal compared to servers that include multiple related utilities.
The tool covers the core video-to-gif conversion workflow with options for size, fps, width, time range, and loop. Minor gaps exist, such as no support for checking video metadata or asynchronous processing, but it fulfills the server's stated purpose.