Manual registration, if you ever need it

\n\nUse the **exact path the installer printed**. It is already expanded for your\nmachine, which matters: `%LOCALAPPDATA%` is expanded by `cmd.exe` and **not** by\nPowerShell, so a config written with the variable silently points nowhere.\n\n```powershell\n# after closing Claude Code — user scope makes it available across projects\nclaude mcp add --scope user horizun-revit -- \"C:\\Users\\\\AppData\\Local\\Programs\\Horizun\\MCP\\server\\horizun-mcp.exe\"\n\n# after closing Codex\ncodex mcp add horizun-revit -- \"C:\\Users\\\\AppData\\Local\\Programs\\Horizun\\MCP\\server\\horizun-mcp.exe\"\n```\n\n```toml\n# Codex timeouts — %USERPROFILE%\\.codex\\config.toml\n[mcp_servers.horizun-revit]\ncommand = 'C:\\Users\\\\AppData\\Local\\Programs\\Horizun\\MCP\\server\\horizun-mcp.exe'\nargs = []\nstartup_timeout_sec = 120\ntool_timeout_sec = 600\n```\n\n```json\n// Cursor, Cline, Windsurf and other MCP clients\n{\n \"mcpServers\": {\n \"horizun-revit\": {\n \"command\": \"C:\\\\Users\\\\\\\\AppData\\\\Local\\\\Programs\\\\Horizun\\\\MCP\\\\server\\\\horizun-mcp.exe\"\n }\n }\n}\n```\n\n**Claude Desktop does not need Claude Code.** Prepare its real `.mcpb` Desktop\nExtension and inspect every supported client from one screen:\n\n```powershell\npwsh -File scripts/install-claude-desktop-extension.ps1 # a real .mcpb Desktop Extension\npwsh -File scripts/diagnose-integrations.ps1 # Codex, Claude Code, Claude Desktop and ChatGPT Work\n```\n\n**ChatGPT Work does not need Codex or Claude Code.** It reaches the same installed\nserver through OpenAI's Secure MCP Tunnel. Run\n`scripts/chatgpt-tunnel.ps1 -Status` or use **Configurar ChatGPT Work** in the\nStart menu. This was verified in the desktop Work interface with a free account\non 2026-09-04; account and workspace controls can vary.\n\nTOML literal strings (single quotes) take Windows paths as they are; JSON needs\nevery backslash doubled. **Raise your client's tool timeout** if it has one: a\nmodel scan or a batch open holds Revit's UI thread for minutes, and a 60-second\ndefault gives up on work that is still running — the bridge then looks broken\nwhile it is merely busy.\n\n

\n\n### 3 · Start Revit and check\n\nTwo things to expect on the first start, neither of them a fault:\n\n- Revit can show a **Security** dialog when the publisher is not already trusted\n — after verifying the build, choose **Always Load**. It can open **on a monitor\n you are not looking at**: a Revit that seems stuck on startup with the CPU idle\n is often this dialog hiding.\n- With a document open, a **Horizun Hub** tab appears in the ribbon. Its *Estado\n del puente* button answers \"is this working, and which version?\" without\n leaving Revit.\n\nFrom your MCP client, `horizun_health` answers the same with the commit\nincluded. A *contract hash mismatch* means one half is on an older build: close\nRevit and install again.\n\n### Build from source instead\n\nNothing prebuilt is downloaded or run: everything is compiled on your machine\nagainst the Revit already installed. You need the\n[.NET SDK 10.0.400](https://dotnet.microsoft.com/download), fixed by\n`global.json` so release bytes do not depend on the latest installed patch. The\nproduced add-ins still target the runtime hosted by each Revit year: .NET\nFramework 4.8 for 2023–2024, .NET 8 for 2025–2026 and .NET 10 for 2027.\n\n```powershell\ngit clone https://github.com/HorizunGroup/horizun-revit-mcp\ncd horizun-revit-mcp\npowershell -ExecutionPolicy Bypass -File .\\install.ps1\n```\n\nIt finds every Revit by its own `RevitAPI.dll`, builds the add-in for each of\nthose years and the MCP server, installs both, and reads every installed binary\nback to prove it landed — stamped commit plus SHA-256 against what was staged. A\nbuild failure changes nothing; a failure after that rolls back through its undo\nledger and tells you the exact state you are in. To update: `git pull`, close\nRevit, run it again.\n\nOr hand the whole thing to an agent — paste this into **Claude Code** or\n**Codex** in any folder:\n\n```\nClone https://github.com/HorizunGroup/horizun-revit-mcp into this folder, read its\nAGENTS.md, and follow the install procedure there. Install and verify the binaries,\nthen confirm the automatic completion status. Do not edit an active client's\nconfiguration; let the installed helper finish registration after that client exits.\n```\n\nBoth pick up [AGENTS.md](https://github.com/HorizunGroup/horizun-revit-mcp/blob/main/AGENTS.md) automatically once they are inside the\nrepository. It carries the prerequisites, the failure modes and the two\nsurprises worth knowing before the first Revit start.\n\n## Architecture\n\n![Horizun Revit MCP architecture: an MCP client speaks stdio to the Horizun server, which forwards over a token-authenticated named pipe to the Revit add-in, which dispatches onto Revit's UI thread](https://raw.githubusercontent.com/HorizunGroup/horizun-revit-mcp/main/docs/assets/architecture.svg)\n\n- **`Horizun.Revit`** — the add-in. `App` (IExternalApplication) starts a\n named-pipe server and publishes a discovery file; `Dispatcher` crosses each\n request onto Revit's UI thread via `ExternalEvent`; `Guard` and `Reconcile` are\n the \"cannot lie\" commit contract; commands live under `Commands/`.\n- **`Horizun.Server`** — the MCP server. The wire format is hand-rolled from the\n open MCP spec, with no third-party SDK: it discovers the pipe, speaks MCP over\n stdio and forwards to the plugin. Schemas and behavioural effects live in one\n shared contract, so `tools/list` answers with Revit closed without drifting\n from the add-in. It negotiates MCP through 2025-11-25; exposes standard Tools,\n Resources, Prompts, Completions, opt-in Logging and durable Tasks; and returns both\n backward-compatible text and `structuredContent`. Five tools are\n **host-resident** — they answer inside the server and never touch Revit.\n- **One command at a time.** Concurrent calls wait in a bounded 16-slot FIFO\n queue; a full queue applies explicit backpressure instead of dropping work.\n Every reply carries what Revit raised while the command ran — warnings, errors\n and modal dialogs — on success and on failure.\n\n## Capabilities\n\nGrouped by what you would actually be doing. The complete reference — every\ntool, and what each one refuses — is in **[docs/TOOLS.md](https://github.com/HorizunGroup/horizun-revit-mcp/blob/main/docs/TOOLS.md)**.\n\n| Group | What it covers |\n| --- | --- |\n| **Session** | Health and target selection across two open Revit versions, document open/save/relinquish, session inspection, view capture as an image. |\n| **Query** | Composable queries and paginated inventory across host and loaded links, model census, quantities, clash, native schedule read. |\n| **Write** | Parameter writes, keynotes, deletion with the cascade counted, transforms, atomic creation of levels, grids, walls, floors, roofs, rooms, MEP runs and structural framing. |\n| **Views & sheets** | Dependency-aware plans, sections, elevations, 3D and drafting views, templates, sheets, viewports, schedules and annotation. |\n| **2D detail** | Semantic resource discovery per view (line styles, region types with real `IsMasking`, placeable symbols — always by id, never by name), and atomic, rehearsed, totally-rolled-back drafting: lines, arcs, polylines, filled/masking regions with pure-validated loops, detail components and symbols, line-style edits. |\n| **Dimensions** | Semantic reference discovery (faces, centerlines, grids, levels, edges — with fingerprints and structured ambiguity instead of guesses), rehearsed-by-creation linear/angular/radial/diameter/arc-length/spot dimensioning with total rollback and `stale_plan` drift refusal, complete dimension reads, and verified edits. The full workflow with examples is in **[docs/DIMENSIONS.md](https://github.com/HorizunGroup/horizun-revit-mcp/blob/main/docs/DIMENSIONS.md)**. |\n| **Planimetry** | End-to-end documentation directly in Revit, without a PDF control loop: query and audit sheets/views/placements/annotations; correct cited findings; pack ordered views and schedules automatically around fixed obstacles; plan collision-aware tags and semantic dimension chains; apply them through the rehearsed annotation writer; create verified revisions, sheet assignments and clouds; then capture and visually review every real sheet through the `planimetry-review` MCP prompt. Unreadable, truncated, ambiguous or uncaptured work is unknown/refused, never clean. See **[docs/PLANIMETRY-AUDIT.md](https://github.com/HorizunGroup/horizun-revit-mcp/blob/main/docs/PLANIMETRY-AUDIT.md)** and **[docs/PLANIMETRY-PRODUCTION.md](https://github.com/HorizunGroup/horizun-revit-mcp/blob/main/docs/PLANIMETRY-PRODUCTION.md)**. |\n| **Families** | RFT → RFA compilation with parameters, formulas, types, dimensions, nested instances, solid/void forms and MEP connectors; system-type duplication with complete compound structures. |\n| **Interoperability** | PDF, DWG, configurable IFC, Navisworks NWC, multi-view FBX, images, schedules, `.xlsx` written over the OPC package, and direct Power BI push ingestion. |\n| **Quantities → budget** | A takeoff of the quantities YOU name (parameter, geometry volume/area, length, count) per element and per budget code, across loaded links with provenance, where a zero is a measurement and absent / empty / unreadable / invalid are four different answers; then a comparison against a budget baseline read from Excel - added / removed / modified / unchanged / not_comparable per code, with quantity, classification and price deltas kept apart, no unit converted and no price invented - written to Excel and Power BI with each destination reported on its own. See **[docs/QUANTITIES-AND-BUDGET.md](https://github.com/HorizunGroup/horizun-revit-mcp/blob/main/docs/QUANTITIES-AND-BUDGET.md)**. |\n| **DWG → BIM** | Convert a linked drawing into a model through a VERSIONED requirement set that is yours rather than compiled in: link and reload typed, read the geometry with an explicit coverage block naming what cannot be read, plan, rehearse, apply, and stamp every created element with the CAD entity it came from. Walls straight and curved, floors with holes, rooms placed by a point genuinely inside them, doors and windows hosted in the wall the drawing implies, columns, grids, and load-bearing walls and slabs verified by re-reading Revit's own parameter. Then AUDIT the result against the drawing, and plan a second revision against the first with what changed named from a closed vocabulary - unchanged, added, removed, moved, reshaped, retyped, relayered, resized, rehosted, manually diverged, ambiguous, conflict. Nothing is ever deleted automatically and a judgement is never taken silently. The workflow, the requirement-set schema and what a drawing cannot tell you are in **[docs/DWG-TO-BIM.md](https://github.com/HorizunGroup/horizun-revit-mcp/blob/main/docs/DWG-TO-BIM.md)**; **[docs/ADR-001-direct-dwg-reader.md](https://github.com/HorizunGroup/horizun-revit-mcp/blob/main/docs/ADR-001-direct-dwg-reader.md)** records what it deliberately does not read, and why. |\n| **Model surgery** | Layer splitting, floor-loop splitting, ungroup/regroup by parameter, slab elevation copying, toposolid embedding and grading, wall rectangularisation. |\n| **Orchestration** | Up to 100 typed writes in one ordered plan with `${key.path}` references, plus durable background jobs polled without touching Revit. |\n\n

Direct Power BI connection

\n\n`horizun_power_bi_push` uses Microsoft's push semantic-model REST endpoint; it\ndoes not automate Power BI Desktop. Credentials are configured in the\nenvironment of the MCP server, never in a tool call:\n\n```powershell\n# Option A: short-lived OAuth access token\n$env:HORIZUN_POWER_BI_ACCESS_TOKEN = ''\n\n# Option B: Entra service principal; Horizun obtains the access token\n$env:HORIZUN_POWER_BI_TENANT_ID = ''\n$env:HORIZUN_POWER_BI_CLIENT_ID = ''\n$env:HORIZUN_POWER_BI_CLIENT_SECRET = ''\n```\n\nThe destination is fixed to `api.powerbi.com`; dataset and workspace ids must be\nGUIDs; values are primitive JSON only; the union is limited to 75 columns,\nstrings to 4,000 characters and each call to 10,000 rows, following Microsoft's\n[push semantic-model limitations](https://learn.microsoft.com/power-bi/developer/embedded/push-datasets-limitations).\nRun with the default `dry_run: true`, then apply with a new `idempotency_key`. An\nidentical retry replays the stored answer; a connection loss after upload is\nreported `in_doubt` and is never sent again automatically.\n\n