It is an independent, experimental tool developed in-house at HENN. It is not made by Autodesk and not by Open WebUI.

Contents

Read this part first

When you connect, the chat model can …

In practice, that means:

  • Save your work before you connect. Try it on a copy of a model first, not on something you care about.
  • Only connect to an Open WebUI you trust.
  • Watch what it does.

If any of that is not acceptable for the machine you are on, stop here.

What you need before you start

  1. **Windows, and Revit .**
  2. <The Revit-side MCP server / dependency>, working in Revit.
  3. An Open WebUI you can log into, in a browser on this same computer.
  4. Open WebUI permissions to create API key and add user-specific integrations.
  5. The plugin, installed from its .yak package / installer.

Revit with the plugin loaded

Setting it up — once

You only do this once. After that, connecting is one click.

Step 1 — Open the settings

The settings window as it opens

Step 2 — Connect

The warning shown before connecting

Settings once the link is running

Step 3 — Fill in your Open WebUI details

  • Base URL —
  • User API key —

The Open WebUI box in settings, filled in

Step 4 — Tell Open WebUI about it

Step 5 — Reload your browser

The browser asking to allow access to devices on the local network

Step 6 — Try it

In the new chat, activate the tool

Turning the Revit tool on in an Open WebUI chat

and then type:

If it answers with something about your model, you’re done.

A chat describing the open Revit model

Using it day to day

  1. Open Revit.
  3. Go to Open WebUI, activate the tool, and chat.

When something goes wrong

Nothing happens when I click connect

Revit says it’s connected, but the chat can’t see any Revit tools

It worked yesterday and today it doesn’t

I need to report a problem

The monitor window, showing status and log

Things worth knowing

Words you’ll see

In the plugin What it means