render_interior — RoomLab.app MCP Tool
render_interior
(render interior) is one of 19 tools on the
RoomLab.app
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call render_interior from your client
- Claude Code RoomLab.app render_interior run in your project directory
- Claude Desktop RoomLab.app render_interior ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor RoomLab.app render_interior ~/.cursor/mcp.json
- VS Code RoomLab.app render_interior .vscode/mcp.json
- Zed RoomLab.app render_interior ~/.config/zed/settings.json
- Windsurf RoomLab.app render_interior ~/.codeium/windsurf/mcp_config.json
- Cline RoomLab.app render_interior ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI RoomLab.app render_interior ~/.gemini/settings.json
- Grok RoomLab.app render_interior .mcp.json (in your project root)
- ChatGPT RoomLab.app render_interior Settings → Connectors → Advanced → Developer mode
- Claude.ai RoomLab.app render_interior Settings → Connectors → Add custom connector
- LangChain RoomLab.app render_interior pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http roomlab https://mcp.roomlab.app/mcpOther tools on this server
- virtual_stage_room
- change_room_style
- declutter_room
- empty_room
- replace_furniture
- replace_material
- render_exterior
- custom_prompt
- set_sky_blue
- fill_and_clean_pool
- clean_garden
- make_grass_greener
- visualize_wall_colors
- create_video_walkthrough
- create_video_transition
- create_house_tour
- upscale_room_image
- get_generation
This list was read from the server itself, by connecting to it and calling tools/list on 6 November 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.