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.

Canon Runtime

As of 2026-07-17, the canonical local MCP runtime is:

uv run main_pipe.py

• main_pipe.py = stdio MCP bridge over Windows Named Pipe \\.\pipe\revit-mcp

• main.py = legacy HTTP fallback bridge to pyRevit Routes on :48884

Use main.py only when pipe diagnostics or compatibility require it.

Related MCP server: Revit MCP Server

How It Works

AI Client ──stdio/SSE/HTTP──> MCP Server (Python/FastMCP) ──Named Pipe/HTTP──> pyRevit Runtime ──> 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

Step 1: Clone and install

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

Step 2: Install the pyRevit extension

The revit_mcp/ folder and startup.py need to run inside Revit via pyRevit.

Option A — Install from pyRevit (recommended):

1. In Revit, go to pyRevit tab > Extensions

2. Find "MCP Server for Revit Python" > Install

3. Wait for pyRevit to reload

Option B — Manual install:

1. Copy the entire repo folder to %APPDATA%\pyRevit\Extensions\

2. Rename the folder to mcp-server-for-revit-python.extension

3. In Revit, go to pyRevit tab > Settings > Custom Extensions

4. Add the path to the .extension folder

5. Reload pyRevit (or restart Revit)

Step 3: Activate pyRevit Routes

1. In Revit, go to pyRevit tab > Settings

2. Navigate to Routes > activate Routes Server

3. pyRevit will start listening on http://localhost:48884/

Step 4: Verify connection

Open a browser and go to:

http://localhost:48884/revit_mcp/status/

You should see:

{
  "status": "active",
  "health": "healthy",
  "revit_available": true,
  "document_title": "your_project_name",
  "api_name": "revit_mcp"
}

Step 5: Start the MCP server

uv run main_pipe.py

That's it. Your AI client can now connect.

Legacy fallback

uv run main.py

Use only if the pipe path is unavailable and HTTP :48884 is intentionally being used as fallback.

Connecting Your AI Client

Claude Desktop / Claude Code

Add to your MCP config:

{
  "mcpServers": {
    "revit": {
      "command": "uv",
      "args": ["run", "main_pipe.py"],
      "cwd": "/path/to/revit-mcp-server"
    }
  }
}

Cursor / Windsurf / Other MCP Clients

Use HTTP transport:

uv run main_pipe.py --streamable-http

Then configure your client to connect to http://localhost:8000/mcp.

Transport Modes

Testing with MCP Inspector

mcp dev main_pipe.py

Then open http://127.0.0.1:6274 in your browser.

Supported Tools (48)

Create (15)

Query (12)

Modify (8)

Analyze (5)

Document (3)

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 LLM.txt for full context that helps AI assistants understand the codebase.

Development Workflow: Editing & Reloading Routes

The MCP server has two layers:

• FastMCP (tools/, main_pipe.py) — runs in your AI client process. Changes apply on next client restart.

• pyRevit Routes (revit_mcp/, startup.py) — runs inside Revit via pyRevit. Changes require a sync + reload.

Typical Edit → Test Cycle

1. Edit code in repo (e.g., revit_mcp/view_management.py or tools/view_management_tools.py)

2. Sync to pyRevit (Windows PowerShell):

   D:\GitHub\revit-mcp-server\sync_to_pyrevit.ps1

   → Copies revit_mcp/ and tools/ to your active pyRevit extension folder.

3. Reload pyRevit (via MCP tool execute_revit_code):

   from pyrevit.loader import sessionmgr
   sessionmgr.reload_pyrevit()

   → Takes ~90s. May return "Error: " vacío — that's normal (reloads kill active requests).

4. Verify your changes:

   • Endpoint routes (POST /refresh_view/, etc.): test immediately post-reload via curl or Invoke-RestMethod

   • MCP tools (new refresh_view(), etc.): visible in next MCP client session (stdio restarts after Revit reload)

Example: Adding refresh_view (2026-07-03)

1. Added refresh_view_handler route to revit_mcp/view_management.py
2. Added refresh_view tool to tools/view_management_tools.py
3. Ran sync_to_pyrevit.ps1 → copied both files to %APPDATA%\pyRevit\Extensions\
4. Called reload_pyrevit() via execute_revit_code
5. POST http://localhost:48884/revit_mcp/refresh_view/ → {"status":"refreshed",...}
6. Next MCP session → tool refresh_view() available in Claude/Cursor/etc.

Contributing

Contributions are welcome! Feel free to submit pull requests or open issues.

Author

Talal Ahmed

License

MIT