Revit建筑模型管理与自动化MCP服务

Revit MCP Server

MCP server for Autodesk Revit 2024/2025/2026/2027 via pyRevit — 48 tools for building design, editing, analysis, clash detection, MEP, interop, documentation, and model persistence.

Works with any MCP client: Claude Desktop, Claude Code, Cursor, Windsurf, Copilot, or any other MCP-compatible application.

How It Works

AI Client ──stdio/SSE/HTTP──> MCP Server (Python/FastMCP) ──HTTP :48884──> pyRevit Routes ──> Revit API

The MCP server runs on your machine and communicates with Revit through pyRevit's Routes API. Any MCP-compatible AI client can connect to it.

Prerequisites

Install pyRevit (if not already installed)

pyRevit is a free add-in that lets scripts run inside Revit. This MCP server needs it to communicate with Revit.

1. Go to https://github.com/pyrevitlabs/pyRevit/releases
2. Download the latest .exe installer (e.g. pyRevit_CLI_x.x.x.x_admin_signed.exe)
3. Run the installer — accept all defaults, click Next through each screen
4. Open (or restart) Revit — you should see a pyRevit tab in the ribbon at the top
5. In the pyRevit tab, click Settings (gear icon)
6. In the Settings window, go to the Routes section on the left
7. Check the box to Enable Routes Server
8. Click Save Settings and let pyRevit reload

To verify: open a browser and go to http://localhost:48884/ — you should see a response (not a "connection refused" error).

Quick Start

1. Get the code

git clone https://github.com/Demolinator/revit-mcp-server.git
cd revit-mcp-server
uv sync

2. Load the extension into pyRevit

startup.py and revit_mcp/ run inside Revit, so pyRevit has to load this folder as an extension.

Don't install "MCP Server for Revit Python" from the pyRevit Extensions manager. That entry installs the original upstream project, which lacks most of the 48 routes this server calls.

1. Pick a folder for your pyRevit extensions, e.g. C:\pyRevitExtensions.
2. Link this repo into it under a name ending in .extension (a junction keeps it updated whenever you git pull):
   复制

   New-Item -ItemType Junction -Path C:\pyRevitExtensions\revit-mcp.extension -Target C:\path\to\revit-mcp-server
   

   (Copying the folder there with that name works too; you'll just need to copy it again after updates.)
3. In Revit: pyRevit tab → Settings → Custom Extension Directories → add C:\pyRevitExtensions.
4. In the same Settings window, under Routes, turn on Routes Server (port 48884).
5. Save Settings and Reload.

3. Check Revit is answering

With a project open, browse to http://localhost:48884/revit_mcp/status/. A working setup answers with "status": "active" and your project's title. A 404 means the extension isn't loaded; "can't reach this page" means Routes is off or Revit is closed.

4. Connect your AI client

Most desktop clients start the server themselves over stdio. Add this to the client's MCP configuration (for Claude Desktop: claude_desktop_config.json):

{
  "mcpServers": {
    "revit": {
      "command": "uv",
      "args": ["run", "--directory", "C:\path\to\revit-mcp-server", "main.py"]
    }
  }
}

For Claude Code: claude mcp add revit -- uv run --directory C:\path\to\revit-mcp-server main.py

Clients that connect over HTTP instead (some Cursor/Windsurf setups, remote clients) need the server started separately:

uv run main.py --http        # then point the client at http://127.0.0.1:8000/mcp

Configuration

Set these environment variables (or the env block of your MCP client config) to change the defaults:

Keep MCP_HOST on 127.0.0.1 unless you understand the risks in SECURITY.md.

Try tools without an AI client

uv run mcp dev main.py       # opens the MCP Inspector at http://127.0.0.1:6274

Supported Tools (48)

Create (15)

Query (12)

Modify (9)

Analyze (5)

Document (2)

Interop & Persistence (4)

Advanced (1)

Architecture

Two runtimes communicate over HTTP:

Multi-Version Revit Support

This server supports Revit 2024, 2025, 2026, and 2027 through centralized helper functions that handle the ElementId API differences across versions:

• get_element_id_value() — Extracts integer IDs using .Value (2024+) with .IntegerValue fallback
• make_element_id() — Creates ElementIds using System.Int64 (2024+) with int fallback

No configuration needed — version detection is automatic via try/except at runtime.

Revit 2027 note: Revit 2027 runs on .NET 10 (vs .NET 8 in 2025/2026). This MCP server is pyRevit-based, so .NET compatibility is handled by pyRevit itself — ensure you run a pyRevit build with Revit 2027 support. None of the 48 tools use APIs removed in 2027 (AXM/FormIt import, Mechanical.Zone members, legacy rebar creation, or the dropped EnergyDataSettings properties).

Unit Handling

All tools accept millimeters (mm). The server converts to Revit's internal feet.

Creating Your Own Tools

Adding a new tool requires 2 files + 2 registration lines:

1. Route handler in revit_mcp/new_module.py (IronPython 2.7)
2. Tool definition in tools/new_tools.py (Python 3.11+)
3. Register routes in startup.py
4. Register tools in tools/__init__.py

See CONTRIBUTING.md for a complete worked example, and LLM.txt for context that helps AI assistants understand the codebase.

Contributing

Contributions are welcome — from typo fixes to new tools! Read CONTRIBUTING.md for the dev setup, the edit–reload loop, a step-by-step "add a tool" walkthrough, and coding conventions.

• Looking for a place to start? See issues labeled good first issue.
• Found a bug or have an idea? Open an issue.
• Please follow our Code of Conduct, and report security issues privately per SECURITY.md.

Author

Talal Ahmed

License

MIT