Ghibli Video MCP Server
Related Servers
Alternatives to Ghibli Video MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA TypeScript-based MCP server that implements virtual try-on capabilities using the HeyBeauty API, allowing users to visualize how clothes would look on them through Claude.22 npm19MIT
- AlicenseAqualityDmaintenanceA TypeScript server that integrates Google's Gemini Pro model with Claude Desktop through the Model Context Protocol, allowing Claude users to access Gemini's text generation capabilities.765 npm12MIT
- AlicenseBqualityDmaintenanceA TypeScript-based middleware that translates Claude AI's decisions into OBS WebSocket commands, enabling solo creators to automate streaming production without manual technical management.232MIT
- FlicenseNot gradedqualityDmaintenanceA TypeScript-based Model Context Protocol server that enables Claude Desktop to fetch real-time weather data via external weather APIs. It provides a simple integration for users to query current weather information through natural language interactions.7 npm-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for converting documents between formats such as HTML, PDF, Markdown, and DOCX, built with TypeScript and designed for Claude Desktop.8 npmMIT
- FlicenseAqualityCmaintenanceA local MCP server for Claude Desktop that integrates Agnes Image 2.1 Flash and Agnes Video V2.0, enabling natural language generation of images and videos with automatic local saving.3-
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: get_points retrieves points, get_task_result fetches task results, and image_to_video handles video conversion. An agent can easily differentiate them based on their specific functions.
The tools follow a consistent verb_noun pattern (get_points, get_task_result, image_to_video), with minor deviations in verb usage (get vs. image_to). The naming is readable and mostly predictable, though not perfectly uniform.
With only 3 tools, the set feels thin for a video server's apparent scope, lacking operations like video management, task creation, or point usage. This minimal count may limit agent workflows and indicate incomplete coverage.
There are significant gaps in the tool surface for a video server domain: no tools for creating tasks, managing videos, or using points, and core operations like video playback or editing are missing. This will likely cause agent failures in handling typical video-related workflows.