Luw MCP Server
OfficialRelated Servers
Alternatives to Luw MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI image processing tools such as vectorization, background removal, upscaling, and logo generation from any MCP-compatible client like Claude Code or Cursor.14 npmMIT
- AlicenseBqualityCmaintenanceIntegration that connects Sketchup to Claude AI through the Model Context Protocol, allowing Claude to directly interact with and control Sketchup for prompt-assisted 3D modeling, scene creation, and manipulation.1026MIT
- AlicenseAqualityCmaintenanceEnables AI photo generation, editing, and video creation from MCP-compatible clients like Claude Desktop, Cursor, and Windsurf.813 npmMIT
- AlicenseNot gradedqualityCmaintenanceConverts spoken descriptions into standards-compliant floor plans and furnished 3D models, enabling real-time collaborative editing through a live browser editor with Claude AI.8 npmApache 2.0

arcframe-mcpofficial
AlicenseNot gradedqualityDmaintenanceGenerate videos, images, audio, and 3D models from any MCP-compatible AI agent — Claude, Cursor, ChatGPT, and more.MIT- AlicenseNot gradedqualityDmaintenanceConnects Claude AI to AutoCAD for architectural design, enabling natural language to execute 684 commands. Automates drawing creation and editing through the Model Context Protocol.23 npm8MIT
TDQS
Scored across 21 tools
Most tools target distinct models/operations and the descriptions carefully draw boundaries (e.g. luw_edit_image vs luw_magic_wand, magic_wand for masked areas). However there is real overlap among luw_sketch_to_render, luw_render and luw_generate_image, and luw_run_model is a generic catch-all that overlaps every dedicated tool.
All tools share a uniform luw_ prefix, and generate_* tools follow a clear pattern. There are minor deviations (magic_wand, background, segment are noun/verb fragments rather than verb_noun, and interior_design/exterior_design use noun_design), but the set remains readable and predictable.
21 tools is on the heavy side for this surface, and several tools (luw_image_tools with 4 sub-actions, luw_personas with 11 actions, luw_projects with 12 actions) multiplex many operations each. The breadth of distinct AI models justifies much of it, but consolidation (e.g. merging sketch/render, or splitting bundled multi-action tools) would improve scoping.
Coverage is broad: generation, editing, segmentation, upscaling, 3D, video, personas, projects, result retrieval, option lookup and raw API access. Minor gaps exist (no history/listing of past generations, no credit/billing status, no deletion of individual generations), but core workflows have no dead ends.