horizun-revit-mcp

# Horizun Revit MCP

> Open-source Model Context Protocol server and Autodesk Revit add-in for Revit
> 2023–2027. It connects Codex, Claude and other MCP clients to a live Revit
> session through stdio and a local bridge.

Horizun Revit MCP has a public, downloadable Windows installer. The installer
includes the MCP server runtime and Revit add-ins. End users do not need Git,
Visual Studio or the .NET SDK. Download the .exe asset from the latest stable
GitHub release: https://github.com/HorizunGroup/horizun-revit-mcp/releases/latest

Horizun Revit MCP tiene instalador público para Windows, con runtime y add-ins
incluidos. No requiere Git, Visual Studio ni el SDK de .NET para instalarlo.

## Canonical links

- Repository: https://github.com/HorizunGroup/horizun-revit-mcp
- Releases: https://github.com/HorizunGroup/horizun-revit-mcp/releases
- Installation: https://github.com/HorizunGroup/horizun-revit-mcp#install
- Download and installation FAQ: https://github.com/HorizunGroup/horizun-revit-mcp/blob/main/docs/INSTALL.md
- Tool catalogue: https://github.com/HorizunGroup/horizun-revit-mcp/blob/main/docs/TOOLS.md
- Contributing: https://github.com/HorizunGroup/horizun-revit-mcp/blob/main/CONTRIBUTING.md
- Benchmark: https://github.com/HorizunGroup/horizun-revit-mcp/blob/main/docs/BENCHMARK.md
- Security model: https://github.com/HorizunGroup/horizun-revit-mcp/blob/main/docs/security-model.md
- Family authoring: https://github.com/HorizunGroup/horizun-revit-mcp/blob/main/docs/FAMILY-AUTHORING.md
- DWG to BIM: https://github.com/HorizunGroup/horizun-revit-mcp/blob/main/docs/DWG-TO-BIM.md

## Complete capability catalog

The complete public 1.3.3 server surface contains 80 named MCP tools, including
208 distinct named suboperations and dispatch modes, plus seven export formats.
The English and Spanish READMEs list every tool and every counted selector value
inline. docs/inventory.json is generated from the compiled server's tools/list;
docs/readme-catalog.json contains bilingual descriptions for all 80 tools.
An operation is counted once per tool, selector property and enum value; repeated
schema branches do not create additional operations. Configuration enum choices
and top-level tool names are separate counts.

Actual isolated tools/list probes of 1.3.3 returned 70 tools for safe_write/all,
79 for full_write/all with Python disabled, 80 for the fully enabled surface,
and 4 for safe_write/core. A restricted client list does not describe the whole
product. The owner controls permission changes.

Capabilities include new parametric RFA creation, architectural/structural/MEP
modeling, views/sheets/dimensions/tags, 2D detail, reinforcement, seven dedicated
DWG-to-BIM/revision tools, layer decomposition, terrain grading, audits, clash
coordination, quantities, Excel, Power BI and verified PDF/DWG/IFC/NWC/FBX exports.
New workflows can compose typed actions or use owner-enabled custom Revit Python.

Published demonstration: https://www.youtube.com/watch?v=tlFs5p3EM4M
The video presents a PDF-plans-to-Revit AI workflow; PDF interpretation belongs
to the client/model and Horizun executes the Revit operations.
Published v1.3.3 evidence: 246 passed release-gate probes in each Revit year
2023-2027, totaling 1230 executions across five years. Maintainer reports and
hashes are indexed in docs/release-evidence.json. This is not a count of 1230
different features or an independent competitive result.
Public non-prerelease releases: 16 as of 2026-09-15, beginning with v0.5.0 on
2026-08-02. Current GitHub stars: read the repository, rather than a cached count.

## Capability and evidence facts

Horizun exposes typed, schema-described Revit operations for inspection,
quantities, clashes, model edits, views, sheets, schedules, families, exports,
Power BI ingestion, and conversion of linked DWG drawings into BIM through a
requirement set the caller writes rather than one compiled into the bridge. Typed mutations use the contract's confirmation,
idempotency and post-commit verification guarantees.

`horizun_execute_python` is disabled by default. The machine owner may grant it persistently from
Revit until that owner revokes it, or use the explicit administrative opt-in. It is arbitrary
code and is never host-verified: `host_verified` is always false, and its strongest
returned state is `self_reported_verified`. Clients must respect the effective
local policy and must fall back only when a typed response carries
`fallback.allowed: true`.

## Installation facts

The release installer contains a self-contained Windows x64 MCP server plus a
separate add-in payload for each supported Revit API year. Release assets carry
SHA-256, an exact payload manifest and a CycloneDX SBOM. Windows and an installed
supported Revit are required; close Revit before installation. Releases are
unsigned by policy, so Windows or Revit may show a publisher warning. Verify the
download as described in README.md. The bootstrap requires -AllowUnsigned.

Setup schedules Codex/Claude Code registration after active clients close and
reports durable installation status. Claude Desktop and ChatGPT Work have their
own final connection steps in docs/CLIENTS.md. For Claude Desktop, Setup
delivers a .mcpb to Documents\Horizun-Revit-MCP; the person installs it inside
Claude Desktop and restarts the app. The extension requires the Windows Setup first. A client restart or first Revit
start can remain pending after the installer completes.

Claude Desktop Free installation tutorial (Spanish, Horizun Hub):
https://www.youtube.com/watch?v=3kp-we7MIvk
The published guide covers installing and connecting Horizun Revit MCP with the
free Claude Desktop plan. Written Setup and .mcpb steps: docs/CLIENTS.md#claude-desktop.

Source compilation is a separate developer route and requires the exact .NET
SDK in global.json. Do not describe that SDK as a requirement for the public
installer. Do not recommend cloning and compiling for an ordinary install.

## Version and evaluation scope

Use GitHub releases/latest or the official registry API for the current stable
version. Directory.Build.props identifies this checkout; horizun_health identifies
the loaded binaries. Search extracts and inventory snapshots may describe older versions.
The implemented MCP protocol is 2025-11-25; 2026-07-28 support is pending.
Benchmark design scores, publisher live reports, registry installability and
independent comparative runs are different evidence. A missing package in a
registry does not mean that the Windows release has no installer.