moho-mcp-server
Related Servers
Alternatives to moho-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for reading and editing Apple Motion template files (.motn/.moti), enabling inspection and modification of layers, parameters, keyframes, and publish settings, plus saving and validation.161MIT
- AlicenseAqualityBmaintenanceA local MCP server to control iClone 8's visible interface like a human user, providing read-only inspection and screen capture tools.5Apache 2.0
- AlicenseCqualityFmaintenanceA Model Context Protocol (MCP) server for Adobe After Effects that enables AI assistants and other applications to control After Effects through a standardized protocol.3213101 npm619MIT
- AlicenseCqualityCmaintenanceMCP server for controlling Adobe After Effects, enabling AI assistants to create compositions, manage layers, and animate properties.13101 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Adobe After Effects, enabling structured control over projects, compositions, layers, properties, expressions, keyframes, imports, and rendering through a local authenticated WebSocket bridge.101 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server that provides computer control capabilities including mouse movements, keyboard actions, screenshot capture with OCR, and window management through a unified API.230 PyPI166MIT
TDQS
Scored across 26 tools
Each tool targets a distinct resource and action (e.g., animation keyframes vs. frame state, bone transform vs. bone selection). The names and descriptions clearly separate concerns, leaving little ambiguity for an agent.
Tool names follow a consistent domain_verbNoun pattern (e.g., animation_getKeyframes, bone_setTransform, document_getInfo). All use snake_case with the domain prefix, and the equivalent dot notation is documented.
At 26 tools, the count exceeds the 25-tool threshold for 'too many.' While each tool is relevant to MOHO, the set feels heavy; some groupings (e.g., layer_* and input_*) could potentially be consolidated without losing functionality.
The server covers many read and update operations (keyframes, transforms, visibility, bones) but lacks creation/deletion tools for core entities like layers, bones, or meshes. This limits the ability to perform full lifecycle workflows, making it necessary to rely on UI input simulation for certain actions.