mcp-manimgl
Related Servers
Alternatives to mcp-manimgl
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that executes Manim Python scripts to generate and return rendered animations. It enables users to create mathematical and programmatic videos dynamically through natural language interfaces.3MIT
- AlicenseNot gradedqualityCmaintenanceEnables LLM agents to generate labeled contact sheets of Manim animations, scaffold storyboards from renders, and validate rendered steps against expected intents via MCP tools.MIT
- AlicenseAqualityAmaintenanceEnables AI agents to generate, execute, and compile interactive Manim slide presentations through MCP tools.82MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for creating math animations with manim, enabling AI-driven real-time interactive creation and browser preview.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables generating and editing mathematical animations via natural language, with support for multi-agent pipeline, RAG-based code generation, and parallel audio narration.MIT
- AlicenseNot gradedqualityFmaintenanceEnables creating 3Blue1Brown style math animations from text descriptions, PDFs, or images. Supports rendering educational videos for math and physics topics.19MIT
TDQS
Scored across 58 tools
Most tools have clear, specific purposes: add_* creates distinct object types, animate_* handles different animations, and set_*/get_* cover properties and queries. However, some overlap exists between generic tools like add_custom_code and animate_transform, and several add_* tools (e.g., add_vector vs add_arrow, add_function_graph vs add_parametric_curve) could confuse agents, especially with many missing descriptions.
Tool names follow a consistent verb_noun snake_case pattern: add_* for creation, animate_* for animations, set_* for properties, get_* for queries, and render_* for output. Minor exceptions like audio_duration don't break the overall predictability, and the grouping by prefix makes the set easy to navigate.
58 tools is excessive for a scene-builder server. Many similar operations are split into individual tools (18 add_* variants, 12 animate_* variants) that could be consolidated with parameters. While the domain is broad, the count makes the surface unwieldy and difficult for agents to choose from efficiently.
The set covers the full manim workflow: scene creation, object construction, transformations, animations, rendering, and audio. Gaps include no way to remove individual objects or animations (only clear_scene), and audio tracks once added cannot be removed or replaced. Overall, the core lifecycle is covered with minor dead ends.