rvt-mcp AGENTS.md

AGENTS.md — rvt-mcp install guide for AI agents

This file is machine-readable install instructions for AI coding agents (Claude Code, Cursor, Cline, VS Code Copilot, Gemini CLI, Antigravity, OpenCode, Codex, and any other stdio MCP client). A user pointed you here because they want rvt-mcp (a Revit MCP server) wired up without hand-editing config files themselves.

What you can do:

• Install the client setup ZIP from GitHub Releases (RvtMcp.Setup-*-win-x64.zip).
• Deploy the bundled plugin into %APPDATA%\Autodesk\Revit\Addins\<year>\ for every installed Revit year.
• Wire supported MCP hosts with the bundled self-contained server executable.
• Verify the handshake and roll back on failure.

Current status — 2026-08-28: latest published release is v0.6.1. Use /repos/bimwright/rvt-mcp/releases/latest. Do not install v0.5.0 or earlier tags.

What you cannot do:

• Install Revit, manage Revit licensing, or launch Revit for the first time. If Revit 2022–2027 is not installed, stop and tell the user.
• Install from unpublished/old tags or old RvtMcp.Setup-*.zip URLs for v0.5.0 and earlier.
• Use NuGet as the client installer. Bimwright.Rvt.Server (0.1–0.3) is obsolete. RvtMcp.Server is server-only (no Revit add-in). Only run dotnet tool install -g RvtMcp.Server if the user explicitly asked for a global .NET tool and plugins are already installed from the GitHub Release ZIP.
• Install the .NET 8 SDK, clone the repo, restore NuGet packages, or build source for a client install. If the user did not explicitly ask for a developer setup, use the GitHub Release ZIP only.

---

Rules for agents

Read these before touching anything. They exist so rvt-mcp stays predictable, auditable, and reversible.

1. Preview every change. Use -WhatIf, --dry-run, or a printed diff before any write. Tell the user the exact file path and the exact change.
2. Install from the latest GitHub Release ZIP only for a Revit client machine. Do not fall back to dotnet tool install, v0.5.0 or earlier tags, source build, or repo clone unless the user explicitly asks for developer installation. If they explicitly asked for the NuGet global tool: RvtMcp.Server 0.6.1+, never Bimwright.Rvt.Server, and they still need the ZIP for plugins.
3. Two explicit approval gates — do not collapse without the user saying so:
   • Before running install.ps1 without -WhatIf.
   • Before editing any MCP host config file outside the setup installer's own preview/apply flow.
4. Never bypass the Revit undo stack at runtime. rvt-mcp's design guarantee is that every edit is reviewable and reversible. Don't advise users to work around transaction wrapping or disable batch_execute safety.
5. On any failure, offer rollback. Config edits are auto-backed up to <file>.bimwright.bak. The full stack comes off with the bundled uninstall.ps1 -Yes.
6. Verify before claiming done. After wiring, run tools/list in the host and confirm the single rvt-mcp entry responds, then call get_current_view_info with no args.