MCP Mermaid vs MCP Manimgl
A side-by-side look at the MCP Mermaid and MCP Manimgl MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Mermaid for data visualization work as a local process; choose MCP Manimgl for data visualization as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Mermaid when
- You need dedicated capabilities in the Data Visualization domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
generate_mermaid_diagram.
Choose MCP Manimgl when
- You need dedicated capabilities in the Data Visualization domain.
- You prefer a local stdio subprocess transport.
- You want tools like
create_scene, get_scene_info, clear_scene.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Visualization | Data Visualization |
| Quality signal | 65/100 · Great | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 646 | 0 |
| Directory activity | 8 views 0 installs 1 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 1 | 58 |
| Full listing | View MCP Mermaid | View MCP Manimgl |
Tools & capabilities
MCP Mermaid tools 1
generate_mermaid_diagramGenerate mermaid diagram and chart with mermaid syntax dynamically. Mermaid is a JavaScript based diagramming and charting tool that uses Markdown-inspired text definitions and a renderer to create and modify complex diagrams. The main purpose of Mermaid is to help documentation catch up with development.
MCP Manimgl tools 58
create_sceneCreate a new manimgl scene with the given configuration. IMPORTANT: Always use MCP tools for scene operations. Do NOT write or execute standalone manim scripts.get_scene_infoGet the current scene's configuration and element counts. IMPORTANT: Always use MCP tools for scene operations.clear_sceneRemove all mobjects and animations from the current scene. IMPORTANT: Always use MCP tools for scene operations.add_waitAdd a wait/pause to the scene timeline. IMPORTANT: Always use MCP tools for scene operations.save_stateSave the current scene state for later restoration. IMPORTANT: Always use MCP tools for scene operations.restore_stateRestore the scene to a previously saved state. IMPORTANT: Always use MCP tools for scene operations.set_cameraConfigure the camera position and/or orientation. IMPORTANT: Always use MCP tools for scene operations.set_configSet global rendering configuration parameters. IMPORTANT: Always use MCP tools for scene operations.add_custom_codeInject custom Python code into the scene script. The code will be inserted inside the construct() method body. Use this for advanced manim functionality not covered by other tools. IMPORTANT: Always use MCP tools for scene operations. Do NOT write or execute standalone manim scripts.verify_scene_overlapsDetect overlapping visual elements (mobjects) in the current scene. Computes axis-aligned bounding boxes for each mobject based on its stored position and dimension properties (radius, width, height, side_length, font_size). Reports any pair whose bounding boxes intersect. NOTE: Positions are only reliably updated by move_to(). After shift/scale/rotate/next_to/align_to, the stored position may be stale. Text and TeX dimensions are estimated from font_size and character count — actual rendered glyphs may differ.generate_scene_scriptGenerate the full Python script for the current scene. IMPORTANT: Always use MCP tools for scene operations. Do NOT write or execute standalone manim scripts. Use render_scene() and get_render_result() for rendering instead.add_circle- +46 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Mermaid
{
"mcpServers": {
"hustcc-mcp-mermaid": {
"command": "npx",
"args": [
"-y",
"mcp-mermaid"
]
}
}
}
MCP Manimgl
{
"mcpServers": {
"mcp-manimgl": {
"command": "uvx",
"args": [
"mcp-manimgl"
]
}
}
}
Frequently asked questions
MCP Mermaid is categorized under Data Visualization and uses a local stdio subprocess. MCP Manimgl belongs to Data Visualization and uses a local stdio subprocess. Pick MCP Mermaid for data visualization work and MCP Manimgl for data visualization.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Mermaid is listed as free. Auth: no auth required. MCP Manimgl has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add hustcc-mcp-mermaid and mcp-manimgl as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Mermaid has a quality signal of 65/100 (Great) with 8 views, 0 installs and 646 GitHub stars. MCP Manimgl has 53/100 (Good) with 1 views, 0 installs and 0 GitHub stars.