The scope here is deliberately narrow: text goes in, a Tripo-generated mesh appears in your scene. That makes it worth a look if you already run the Tripo Blender addon and want the request to come from an assistant instead of a panel. It also means the setup is two pieces, not one — the addon must be installed and running, and the project is upfront that this is alpha.
A bridge between an MCP client and Tripo AI, aimed at one job: turning natural language into a 3D model that lands in Blender. The project describes itself as alpha, and the path it currently supports is the Tripo Blender Addon — the addon runs the Blender-side server, and this MCP server is what the assistant talks to.
- A 3D asset generated from a natural-language description through Tripo's API and imported into the Blender scene you already have open — the README's own example is asking for a futuristic chair
- A connection that works from Claude for Desktop or Cursor, or any other MCP-enabled assistant
Python 3.10 or later, Blender, and the Tripo AI Blender Addon installed from tripo3d.ai — the addon has to be enabled and its Blender-side server started before the assistant can do anything. The package is `tripo-mcp` (0.1.2), launched with `uvx`. The project states it is in alpha and that Blender addon integration is the only supported path today.
One command — uvx tripo-mcp