How to connect Claude to SketchUp

What does connecting Claude to SketchUp mean?

A normal Claude chat only sees what you type or paste. It can write SketchUp Ruby, but it can't open your model, run the code or look at the result. You do that part, and you paste the errors back.

Connecting means giving Claude tools it can call. The standard way is the Model Context Protocol (MCP): a small server exposes actions like "run this Ruby" or "take a screenshot", and Claude decides when to use them. Once connected, Claude can inspect the model, make a change, check it and try again without you copying anything.

There are two kinds of connection, and the difference matters:

• A cloud connection builds a model on someone else's server and hands you a file. Nothing touches your open model.
• A local connection runs inside SketchUp on your computer. Claude works on the model you have open, including models you already made.

For background on MCP itself, see SketchUp MCP servers.

Ways to connect Claude to SketchUp

Trimble's SketchUp connector for Claude

Trimble announced an official SketchUp connector for Claude in April 2026. You add it in Claude under Customize › Connectors, search for SketchUp and sign in with a Trimble ID. You describe an object, Claude builds it in a cloud SketchUp session and gives you a thumbnail and a download link to a .skp file that opens in any SketchUp version.

Its strengths: there's nothing to install, and it's made by the company that makes SketchUp. Its limits, per Trimble's own help page: version 1 only creates new files. It can't open or edit an existing .skp, and each change produces a new file version. Free SketchUp users can generate up to 30 models before a paid SketchUp subscription is needed. Good for blocking out a new object, not for working on your project file.

Claude Desktop, Code tab, with a plugin

Claude Desktop has a Code tab that can run plugins and local MCP servers on your computer (the regular Chat tab can't reach a local server). A SketchUp extension runs the server inside SketchUp, and a Claude plugin tells Claude where to find it. This is the easiest local route if you don't use a terminal. MakeIt4Me works this way (we make it; more below).

Claude Code in a terminal or editor

Claude Code is the command-line version. It comes with paid Claude plans (Pro and above) or an API account. You register a local server with one command, then talk to it in the terminal or in an editor like VS Code.

Free open-source SketchUp MCP servers

Several free projects on GitHub do the same basic job: a SketchUp extension plus a small server that lets Claude run Ruby in your model. They cost nothing and you can read every line. Setup usually means installing a Python toolchain, editing Claude's MCP config by hand and starting the server from SketchUp's Extensions menu. Check whether a project handles undo and screenshots before you rely on it. The differences are laid out on our comparison page.

How to set up a local connection, step by step

The details depend on which server you pick, but every local route follows the same outline. You need SketchUp Pro or Studio on desktop, because SketchUp Free (web) and SketchUp Go don't run extensions.

1. Install the SketchUp extension. Open Extensions › Extension Manager (on the Window menu before SketchUp 2021.1), click Install Extension and pick the .rbz file. Some servers then need a SketchUp restart or a Start Server menu item.
2. Tell Claude about the server. In Claude Desktop, open the Code tab, click Customize and add or upload the plugin you were given. In Claude Code, register the server's address, for example claude mcp add --transport http sketchup http://localhost:9876/mcp (use the port your server's instructions give).
3. Restart Claude so it loads the new tools.
4. Check the connection. With a model open, ask: "Can you see the model I have open in SketchUp?" A working setup answers with what's in your model, not a guess.

By default Claude asks before each action. That gets tiring when it builds something in twenty steps. In the Code tab you can pick a less interruptive permission mode from the mode menu under the prompt box (Cmd+Shift+M on Mac, Ctrl+Shift+M on Windows). Auto mode, where your plan and model offer it, lets Claude keep going while background checks watch for risky actions. Only do this when every change can be undone (see below).

What Claude is good and bad at in SketchUp

Claude does best on work that has a clear rule behind it, where SketchUp makes you repeat the same clicks:

• Batch edits: replace a material everywhere, rename components to a pattern, tag every object of a kind.
• Reports: counting components, listing parts, writing a cut list to a CSV.
• Blocking out simple geometry from dimensions or reference photos: a shed, a deck, a box with a lid.
• Setting up scenes with named camera views.
• Writing and testing small Ruby tools you'd otherwise never get around to.

It's weaker where the job is about taste or precision it can't measure:

• Organic or highly detailed shapes. It thinks in boxes, lines and arcs.
• Judging how something looks. Screenshots help, but it can miss a face that is slightly off.
• Long builds in one go. Errors stack up if it never stops to check.
• Rendering. It works on geometry, not photoreal images.

How to prompt Claude for SketchUp work

• Give real dimensions and units. "A 36 in wide door opening, 80 in tall, centered on the front wall" beats "add a door". SketchUp stores lengths in inches internally, so say metric out loud if you work in it.
• Say what to leave alone. "Replace Light Oak with Walnut, but not on the flooring."
• Work in small steps. Ask for the floor, look, then the walls. Each step is easier to check and undo.
• Ask it to look. "Take a screenshot from the front and check the roof lines up with the walls." A connection with a screenshot tool lets Claude catch its own mistakes.
• Point at things. Select objects in SketchUp and say "the selected group", or use names from the Outliner.
• Ask for a count first. "How many components use this material?" tells you whether it understood before it changes anything.

Undoing what Claude did

SketchUp's Ruby API lets code group its changes into one named undo step with model.start_operation("Name", true) and model.commit_operation. A well-behaved SketchUp MCP server does that for every change, so Edit › Undo (Cmd+Z on Mac, Ctrl+Z on Windows) takes back a whole request at once.

Not every server does. If yours runs code without an operation, one request can leave dozens of separate undo steps, and code that fails halfway leaves half a change behind. Two habits help either way:

• Save, or save a copy, before a big request.
• Ask Claude to wrap its changes in a single operation and to abort the operation if the code raises an error.

File saves and exports written to disk can't be undone from SketchUp.

Questions