
Claude Code is a coding agent, so on paper it has no business touching a floor plan or a mood board. In practice, 2026 has been the year that changed, because MCP servers let you bolt real design tools onto the agent. Connect the right ones and Claude Code can render a photorealistic version of your actual room, model a building in Blender, drive a parametric Grasshopper definition, or hand you a floor plan with material specs, all from the same chat window you already keep open.
This is a working list, not a hype reel. I run MeltFlex, so I will be upfront about where our own MCP fits and where it does not, and I will tell you plainly which of these are genuinely useful today and which are still rough. There are exactly seven worth knowing for architects and interior designers, and most studios will want two or three of them, not all seven.

An MCP server is the bridge. It lets Claude Code call a tool like MeltFlex and get a real room render back, without leaving the chat.
The short version
Here is the whole list in one table, sorted roughly from interiors to heavy architecture. Use it to find your two or three, then read the honest take on each below.
| MCP server | Best for | Output | Free? |
|---|---|---|---|
| MeltFlex | Interior designers, stagers, homeowners | Photoreal redesign of your real room, shoppable furniture | Credits, free to try |
| Architecture MCP | Early concepts and specs | 3D concepts, floor plans, material and cost sheets | Free tier, then paid |
| Blender MCP | 3D modeling and rendering | Live edits to a Blender scene | Free, open source |
| Grasshopper MCP | Parametric design | Generated and edited GH definitions | Free, community |
| Rhino MCP | Architects modeling in Rhino | Geometry and analysis in Rhino | Free, community |
| Interior Design 3D | 3D room planning | Room layouts, materials, lighting, tours | Unclear, npm package |
| Figma MCP | Decks and design systems | Component extraction, design handoff | Free with Figma |
I will declare the bias and then make the case anyway. MeltFlex MCP exists because every other AI design tool quietly throws away the one thing that matters most: your actual space. You send Claude Code a photo of your living room, describe the look you want, and it returns a photorealistic redesign of that exact room, with the same windows, ceiling height and proportions, restyled. It does not invent a generic room that happens to look nice. It restyles yours.
The second half of the moat is the furniture. Pass a reference image of a sofa you are considering, or a piece you already own, and the redesign builds around it, so the result is a plan you can act on rather than a pretty picture you can never source. That is the same engine behind shoppable results in the MeltFlex app, now available as two tools in chat: generate_interior to restyle a room, and check_credits to see your balance. It runs on your own credits, ten per render, and a failed generation is refunded automatically.

A single generate_interior call from Claude Code: your real room, restyled, with furniture you can actually buy.
Honest take: use it when the job is “show me my space, redesigned, with real pieces”. It is deliberately narrow, so it is not a 3D modeler and not a CAD tool. For interior designers, stagers and homeowners it is the fastest path from a room photo to a believable, buyable redesign without leaving Claude Code.
Architecture MCP (the sceneview-tools server) is the broadest single tool here. It exposes eight tools that walk from a rough idea to something a contractor can read: generate_3d_concept for massing and materials, create_floor_plan with SVG layouts and basic compliance checks, interior_design for mood boards and furniture layouts with dimensions, plus material_palette, lighting_analysis with lux calculations, and cost_estimate. The paid tiers add render walkthrough specs and a full technical export covering electrical, plumbing, HVAC and accessibility.
Honest take: this is a strong early-stage and documentation tool, and the lighting and cost outputs are genuinely useful for scoping. The catch is that its visuals are concept-grade SVG and spec sheets, not photoreal renders, so pair it with a renderer for client-facing images. It is free for about ten designs a month, then 49 dollars a month for Pro and 149 for Studio. For a solo architect doing feasibility and specs, the free tier alone earns its place in the config.
Blender MCP, by Siddharth Ahuja, is the open-source server that turned “control Blender by talking to it” from a demo into something people actually use. It pairs a Blender add-on with a Python MCP server, so Claude Code can manipulate objects, control materials, inspect the scene and even run scripts, and it hooks into asset libraries like Poly Haven and Hyper3D so you can pull in textures and models by name.
Honest take: powerful, free, and the right answer if you already know Blender and want to skip memorizing the Python API. If you do not know Blender, set expectations low, because it will do impressive things and then fail in ways that need a real 3D artist to unstick. For architects building quick massing studies or designers prototyping a scene, it is the best free 3D option on this list. It needs Blender 3.6 or newer.
McNeel has not shipped an official server yet, so this is community territory, and it is surprisingly healthy. Several Grasshopper MCP projects (alfredatnycu, veoery and others) bridge Claude to a parametric definition through a small TCP or socket server running inside Grasshopper, often paired with a knowledge base of components so the agent can reason about which nodes to wire together. The companion Rhino servers let the agent read a .3dm file, model geometry and run analysis.
Honest take: the standout value is that Grasshopper MCP helps the AI reason about logic and systems, not just static shapes, which is exactly what parametric work is about. That makes it genuinely useful for architects doing computational design, facade systems or generative studies. Because it is community-built, expect setup friction and rough edges, and read the repo before you trust it on a live project. Niche, but for the right architect it is the most interesting entry here.
The interior-design-3d-mcp npm package advertises seven tools for 3D interior visualization: a room planner, AR furniture placement, a material switcher, lighting design and virtual room tours built on SceneView. On paper that is a tidy feature set that sits between flat redesign and full 3D modeling, and it works with Claude, Cursor and VS Code.
Honest take: I am including it because the capability list is right for interior designers, but the public documentation is thin and the pricing is unclear, so go in with low expectations and test it on a throwaway project first. If it matures, it fills a real gap between MeltFlex-style redesign and Blender-style modeling. Right now it is a watch-this-space pick rather than a daily driver.
Not every design job is a render. Figma MCP is the official, vendor-maintained server, and it lets Claude Code read design files, extract components and tighten the design-to-handoff loop. For an architecture or interior studio, that means client decks, brand and presentation assets, spec boards and a consistent design system, all driven from the agent.
Honest take: do not expect it to render a room, because that is not its job. Expect it to take the unglamorous but constant work of presentations, proposals and design systems off your plate. Being vendor-maintained, it is also one of the lowest-risk servers to install. If your studio lives in Figma for client-facing material, this belongs in your config next to whichever renderer you choose.
The pattern is the same for all of them. In Claude Code you run one command, then restart the session:
claude mcp add <name> -- <command that starts the server>For MeltFlex that is a single line, then a one-time sign-in with your own key so renders bill to your account:
claude mcp add meltflex -- npx -y meltflex-mcp
npx -y meltflex-mcp auth mf_sk_xxxxxxxxxxxxYou generate your key in account settings (it looks like mf_sk_…), and the same config shape works in Cursor, Claude Desktop and Windsurf through their mcp.json. Once a server shows as connected, its tools appear to the agent and you just ask in plain language. The full MeltFlex setup page has copy-paste config for every client.

The same server connects to any MCP client. Claude Code is a single command, the rest take a small JSON block.
Two things are worth saying out loud, because the “AI does everything” framing sets you up to be disappointed. First, none of these servers replace design judgment. They shorten the loop between an idea and seeing it, which is where rooms and buildings actually get better, but the taste is still yours. Second, this whole category is early. The interior and architecture corner of MCP is thin compared to the coding tools, which is exactly why it is worth getting in now, but it also means rough edges, changing pricing and the occasional server that overpromises.
The practical setup for most studios is two or three servers, not seven: a renderer that keeps your real space, one modeling or parametric tool that matches how you work, and Figma for the deliverables. Start there, add more only when a real job demands it.
Add MeltFlex to Claude Code
Can Claude Code do interior design?
Not by itself. It is a coding agent that can plan and describe, but it cannot render your room or model geometry until you connect an MCP server. MeltFlex MCP gives it photoreal room redesign, Blender MCP gives it 3D modeling, Grasshopper MCP gives it parametric design.
Which MCP server keeps my real room?
MeltFlex MCP. You send a photo and it restyles that exact space, keeping the windows and proportions, and you can anchor it to real furniture through reference images. Most other servers model from scratch or generate a new room.
Are these free?
Blender, Grasshopper and Rhino servers are free and open source, Figma MCP is free with a Figma account, Architecture MCP has a free tier then paid plans, and MeltFlex runs on your own per-render credits with failures refunded.
How many should I install?
Usually two or three: a renderer, one modeling or parametric tool, and Figma for deliverables. Adding all seven just clutters the agent.