Autodesk Revit MCP Server

io.github.Sam-AECPublished by GitHub account Sam-AECv0.1.1Updated Nov 3, 2026

MCP server connecting AI assistants to Autodesk Revit through a local bridge.

The publisher's own server: Autodesk Product Help MCP

VerifiedSTDIODesktop onlyDeveloper ToolsMedia & Design

Overview

AI-generated overview

Connects AI assistants to Autodesk Revit through a local bridge so they can review BIM model quality and fix Revit parameters.

What you can do
  • Inspect BIM models read-only to review model quality
  • Propose and apply Revit parameter fixes through an approved plan
  • Inspect IFC models, with Rhino, Grasshopper and Speckle providers included
  • Run in mock mode with canned responses for development without Revit
When to use it
Useful for AEC and BIM teams on Windows who want an assistant to audit Revit model quality and make controlled parameter corrections, or to explore the toolset in mock mode before connecting a live Revit session.
Requirements
Runs locally over stdio as a Python 3.11+ package or an MCPB bundle using the uv runtime. Live Revit automation needs Windows, Revit 2024–2027 and the native Revit add-in. MCP_REVIT_WORKSPACE_DIR and MCP_REVIT_ALLOWED_DIRECTORIES are required; MCP_REVIT_MODE selects bridge or mock, and MCP_REVIT_BRIDGE_URL is needed in bridge mode.
Before you install
Model changes are gated behind an approved plan by default, but approving a plan lets the assistant modify Revit parameters, so review plans before approving. The server can access files in the directories listed in MCP_REVIT_ALLOWED_DIRECTORIES, so keep that list narrow. An audit log path can be set via MCP_REVIT_AUDIT_LOG.

Installation

In SourceWeft

  1. Open Autodesk Revit MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

AEC Model Bridge

Python MCP server for reviewing BIM model quality and fixing Revit parameters with Claude, Codex and other MCP clients. Read-only tools inspect the model; model changes require an approved plan by default.

Get started | Example workflows | Tool reference

Live Revit automation requires Windows, Revit 2024–2027 and the native Revit add-in. The server also includes IFC inspection, Rhino and Grasshopper, and Speckle providers. Navisworks integration is in progress. See the installation guide.

Run the server

Requires Python 3.11 or newer. To explore the tools in mock mode from a repository checkout:

powershell
python -m pip install -e packages/mcp-server-revit$env:MCP_REVIT_MODE = "mock"$env:MCP_REVIT_WORKSPACE_DIR = (Get-Location).Path$env:MCP_REVIT_ALLOWED_DIRECTORIES = $env:MCP_REVIT_WORKSPACE_DIRpython -m revit_mcp_server.mcp_server

MCP clients start the server over stdio. The console command is aec-model-bridge; revit-mcp-server remains available as a compatibility alias. For development without Revit, set MCP_REVIT_MODE=mock to return canned responses. The release .mcpb bundle uses the MCPB uv runtime and prompts for a permitted workspace directory.

Configuration

Environment variablePurpose
MCP_REVIT_MODEbridge for a live application or mock for development
MCP_REVIT_WORKSPACE_DIRWorkspace root for server file operations
MCP_REVIT_ALLOWED_DIRECTORIESSemicolon-separated permitted directories
MCP_REVIT_HOST_VERSIONOptional Revit year selector, such as 2026
MCP_REVIT_BRIDGE_URLOptional explicit bridge endpoint
MCP_REVIT_AUDIT_LOGAudit log location
MCP_REVIT_LOG_LEVELLogging verbosity

See the configuration reference and release notes.

License

GPL-3.0-or-later with the Revit Linking Exception, or a commercial license.

Maintained by A. Sam Mohammad.

Source: packages/mcp-server-revit/README.md at commit 7fd43b3

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Autodesk integrations