Autodesk Native Agent Runtime for Revit 2024

A production-grade bridge between AI agents (Antigravity, Claude, etc.) and Autodesk Revit 2024, built on the Model Context Protocol (MCP).

Architecture

Antigravity / AI Agent
    ↓ (MCP over stdio)
MCP Server (TypeScript, Node.js)
    ↓ (Named Pipe, JSON envelopes)
Revit 2024 Add-in (.NET Framework 4.8)
    ↓ (ExternalEvent)
Main-thread Dispatcher → PlanExecutor
    ↓ (TransactionGroup)
Revit API (Document, Wall, FamilyInstance, ...)
    ↓ (Verification + Assertions)
Structured Result → MCP Response

Quick Start

1. Prerequisites

• Revit 2024 installed (required for add-in build)

• .NET SDK (for building C# projects)

• Node.js 18+ (for MCP TypeScript server)

• PowerShell (for build/install scripts)

2. Set REVIT_2024_PATH

If Revit is not in the default location (C:\Program Files\Autodesk\Revit 2024), set the environment variable:

$env:REVIT_2024_PATH = "D:\REVIT\2024\Revit 2024"

3. Build

.\scripts\build-all.ps1

4. Install Add-in

.\scripts\install-revit2024.ps1

5. Open Revit 2024

Open or create a Revit project. The add-in starts the named-pipe server automatically.

6. Start MCP Server

.\scripts\start-mcp.ps1

7. Configure Antigravity

Add the MCP server to your Antigravity configuration:

{
  "mcpServers": {
    "revit": {
      "command": "node",
      "args": ["e:\\revit-A.I Native\\apps\\agent-mcp\\dist\\index.js"]
    }
  }
}

8. Get Status

Call revit_get_status from your agent. You should see:

{
  "connected": true,
  "activeDocumentTitle": "YourProject.rvt",
  "busy": false
}

9. Preview a Plan

Send a plan to revit_preview_plan:

{
  "schemaVersion": "1.0",
  "requestId": "test-001",
  "description": "Create a 5000mm wall",
  "document": { "strategy": "active_document" },
  "units": "mm",
  "coordinateSystem": "project",
  "executionMode": "preview",
  "operations": [...],
  "safety": { "requireUserConfirmation": true }
}

10. Approve & Commit

Call revit_commit_plan with the same plan. If confirmation is required, approve in Revit.

11. Inspect Audit Log

Audit logs are at %LOCALAPPDATA%\AutodeskNativeAgent\logs as JSONL files.

Supported Operations

MCP Tools

Key Design Decisions

1. No Revit API from background threads — All Revit API calls go through the ExternalEvent dispatcher

2. Atomic execution — Plans run inside a single TransactionGroup; failures roll back

3. Structured errors — Every failure carries a stable error code

4. Unit safety — All lengths carry explicit units; no hardcoded / 304.8

5. Type safety — Type/level resolution is deterministic; no random FirstElement()

6. Path security — Export/SaveAs paths are canonicalized and checked for traversal

7. Confirmation tokens — Destructive operations require human approval

Documentation

• Architecture

• Security

• Commands

• Troubleshooting

• Revit 2024 Development

• Extending to AutoCAD

• Manual Test Checklist

License

MIT