Build123d MCP vs Manim MCP Server
A side-by-side look at the Build123d MCP and Manim MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Build123d MCP for art & culture work over a hosted endpoint; choose Manim MCP Server for art & culture as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Build123d MCP when
- You need dedicated capabilities in the Art & Culture domain.
- You prefer a remote HTTP/SSE transport.
Choose Manim MCP Server when
- You need dedicated capabilities in the Art & Culture domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
MANIM_EXECUTABLE.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Art & Culture | Art & Culture |
| Quality signal | 53/100 · Good | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | MANIM_EXECUTABLE |
| Verified owner | Community listing | Community listing |
| GitHub stars | 108 | 651 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Build123d MCP | View Manim MCP Server |
Tools & capabilities
Build123d MCP tools
No tool names declared yet. Check the project README from the listing page.
Manim MCP Server tools
No tool names declared yet. Check the project README from 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.
Build123d MCP
{
"mcpServers": {
"pzfreo-build123d-mcp": {
"url": "http://localhost:8000/mcp"
}
}
}
Manim MCP Server
{
"mcpServers": {
"abhiemj-manim-mcp-server": {
"command": "uvx",
"args": [
"manim"
],
"env": {
"MANIM_EXECUTABLE": "YOUR_MANIM_EXECUTABLE_HERE"
}
}
}
}
Frequently asked questions
Build123d MCP is categorized under Art & Culture and uses a remote HTTP/SSE transport. Manim MCP Server belongs to Art & Culture and uses a local stdio subprocess. Pick Build123d MCP for art & culture work and Manim MCP Server for art & culture.
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.
Build123d MCP has no declared pricing — check the project's own site. Manim MCP Server is listed as free. Auth: no auth required. 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 pzfreo-build123d-mcp and abhiemj-manim-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Build123d MCP has a quality signal of 53/100 (Good) with 1 views, 0 installs and 108 GitHub stars. Manim MCP Server has 41/100 (Fair) with 3 views, 0 installs and 651 GitHub stars.
