tm_render_image — Twinmotion MCP MCP Tool
tm_render_image
(tm render image) is one of 5 tools on the
Twinmotion MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call tm_render_image from your client
- Claude Code Twinmotion MCP tm_render_image run in your project directory
- Claude Desktop Twinmotion MCP tm_render_image ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Twinmotion MCP tm_render_image ~/.cursor/mcp.json
- VS Code Twinmotion MCP tm_render_image .vscode/mcp.json
- Zed Twinmotion MCP tm_render_image ~/.config/zed/settings.json
- Windsurf Twinmotion MCP tm_render_image ~/.codeium/windsurf/mcp_config.json
- Cline Twinmotion MCP tm_render_image ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Twinmotion MCP tm_render_image ~/.gemini/settings.json
- Grok Twinmotion MCP tm_render_image .mcp.json (in your project root)
- ChatGPT Twinmotion MCP tm_render_image Settings → Connectors → Advanced → Developer mode
- Claude.ai Twinmotion MCP tm_render_image Settings → Connectors → Add custom connector
- LangChain Twinmotion MCP tm_render_image pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http twinmotion-mcp https://twinmotion-mcp.itmartin24.workers.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.