Do the work for clients
Blender Tailscale MCP hub
One VM. One Blender. You still own the token.
shared by @satishgoda ↗
How it's set up
Grok Bot as hub between a VM and Blender over Tailscale; MCP add-on served the port and minted the token instead of Blender Lab MCP, they posted. We have the tweet. We did not sit the hub. No dollar. No public install.
- 01Use a VM and a Blender you already run. Tailscale you already trust.
- 02Let Grok Bot sit as the hub as they named. MCP add-on serves the port.
- 03The add-on minted the token instead of Blender Lab MCP, they said. You still own that token.
- 04You still check the scene. The bot does not ship the file on day one.
- 05Write a fee from money you took. Do not invent a dollar.
Prompt
We cannot write an honest starter prompt from what was published. Use the steps above.
How the money works
A hub that drives Blender can later bill a client. They posted no dollar. First proof is one Blender job a human still checked — not a token copied from the tweet.
What to try first
This week: a Blender you own, a Tailscale you trust, and one scene you still check.
Watch out
- Tokens: a live Blender hub can burn the week. Cap the run.
- Time: one checked scene beats a Tailscale hub you cannot show.
- Claim: Grok Bot as hub between a VM and Blender over Tailscale, with an MCP add-on serving the port and minting the token instead of Blender Lab MCP, is what they posted. Not a hub we sat. Not a public install.