Autodesk Revit MCP Server

AEC Model Bridge is the open, secure runtime that puts Revit, Rhino, Navisworks, and Power BI behind one MCP call center — so an AI agent orchestrates them directly, instead of you manually dumping data between disconnected apps. The autodesk revit mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 1 defined tool rather than through you.

What it actually does

• 100+ MCP tools for model authoring, documentation, parameters, views, sheets, exports, and QA
• Native Revit & Navisworks add-ins with no Dynamo or pyRevit dependencies
• Multi-platform synchronization: Cross-query Navisworks clash results, Revit parameters, and Rhino models dynamically
• Speckle and PowerBI automated data handoffs
• Async job orchestration and centralized PII redaction
• Reflection and in-process Python for advanced API workflows

Its toolset

Everything the assistant can do here goes through one of these:

• Requirements — You also need Windows 10 or 11, Python 3.11 or later, and a licensed Revit installation for the version you want to use

Configuration

You will need 4 environment variables: MCP_REVIT_MODE, MCP_REVIT_BRIDGE_URL, MCP_REVIT_WORKSPACE_DIR, MCP_REVIT_ALLOWED_DIRECTORIES. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

| Revit version | Add-in target | Required build tools | |---|---|---| | 2024 | .NET Framework 4.8 | .NET 8 SDK and .NET Framework 4.8 developer pack | | 2025 | .NET 8 for Windows | .NET 8 SDK | | 2026 | .NET 8 for Windows | .NET 8 SDK | | 2027 | .NET 10 for Windows | .NET 10 SDK | You also need Windows 10 or 11, Python 3.11 or later, and a licensed Revit installation for the version you want to

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Autodesk Revit's toolset — Requirements — is a fair guide to whether it matches your workflow. It is maintained by sam-aec; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the autodesk revit mcp server does with a few real requests.