MPFB MCP
OfficialRelated Servers
Alternatives to MPFB MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible clients to control Blender for modeling, materials, animation, physics, rendering, scene inspection, documentation search, and asset/generation service integration. It exposes a stdio endpoint with many Blender operations for creating and editing 3D content.AGPL 3.0
- AlicenseCqualityBmaintenanceEnables secure, local automation of Blender through typed MCP tools for scene, modeling, material, animation, rendering, and file workflows via an authenticated loopback bridge.173MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP hosts and coding agents to model, inspect, measure, and deliver real Blender scenes through 15 tools and 217 catalog operations, returning actual rendered images after key edits. Works against a live Blender GUI via addon or a persistent headless worker, producing editable .blend files, GLB exports, previews, and acceptance records.1BSD 3-Clause
- AlicenseAqualityCmaintenanceEnables connecting Blender 3D to AI assistants via MCP, allowing prompt-driven 3D modeling, scene editing, and real-time manipulation. Supports object/material control, scene inspection, viewport screenshots, and integrations with Poly Haven, Sketchfab, and AI model generators.22MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI-assisted 3D modeling workflows by connecting Blender with LLMs and CSM.ai, allowing text-based editing, asset retrieval from CSM.ai sessions, and humanoid animation using Mixamo files.132MIT
- AlicenseNot gradedqualityDmaintenanceExposes 50+ Blender tools (object manipulation, materials, animation, etc.) via MCP for AI-driven 3D workflows and automation.1MIT
TDQS
Scored across 34 tools
The set is exceptionally well-differentiated: read/write pairs are clearly split (get_face_units vs get_expression, set_targets vs symmetrize_targets), and the two-step rigging and material tools have explicit boundaries. The summary tool overlaps other readers but is explicitly positioned as a convenience first-call, so ambiguity is low.
All tools use the mpfb_ prefix and a snake_case verb_noun pattern (add_asset, get_object_info, set_skin), with only natural domain wording differences such as human/character. Naming is predictable and consistent throughout.
At 34 tools this is heavy for an MCP surface, exceeding the typical well-scoped range; many list/get/set pairs and niche diagnostics could be consolidated. The broad MakeHuman domain justifies some breadth, but context cost is high.
Core character lifecycle is covered: create/from preset, rig/add rigify, dress/undress assets, shape targets, face units/expressions, skins/materials, save/load presets, refit, and status/docs/list support. Missing a direct character/rig deletion or swap tool and some pose/ink-layer/makeup application paths, but those are minor workarounds.