
学习如何构建你的REVIT管理程序
概览
Revit MCP 允许 AI 客户端通过模型上下文协议(MCP)调用 Autodesk Revit 工具。MCP 服务器将工具调用转发给本地的 Revit 插件,插件执行相应的 Revit API 工作流程。 - 演示视频:Revit MCP - AI驱动BIM工作流程演示 - 知识网站:https://shuotao.github.io/REVIT_MCP_study/ - 默认WebSocket端口:8964 用通俗易懂的语言与Revit交流。让你的AI客户端“给此视图的每一面墙体尺寸”或“检查幕墙立面”,Revit会通过建筑规范、工程量计量、合规检查来完成。 使用Revit并希望获得AI辅助、基于标准的工作流程的BIM工程师和架构师。你需要在Windows上使用Revit(2022–2026),并且能够熟练安装插件。 1. 构建并部署C#插件——参见手动设置。这部分是实际与Revit通信的部分。2. 无需克隆——它直接从npm运行:3. 完整配置:AI客户端配置。
概述(AI 翻译)
英文 |繁體中文
Revit MCP 允许 AI 客户端通过模型上下文协议(MCP)调用 Autodesk Revit 工具。MCP 服务器将工具调用转发给本地的 Revit 插件,插件执行相应的 Revit API 工作流程。
- 演示视频:Revit MCP - AI驱动BIM工作流程演示
- 知识网站:
- 默认WebSocket端口:
8964
这是什么?
用通俗易懂的语言与Revit对话。要求你的AI客户端*“为此视图中的每面墙体尺寸”或“检查幕墙立面”*,Revit会通过222个MCP工具和90个专业BIM SOPs(建筑规范、工程量计量、合规检查)来完成。
适合谁: 使用 Revit 并希望获得 AI 辅助、基于标准的工作流程的 BIM 工程师和架构师。你需要 Windows 版 Revit(2022–2026 版),并且安装插件时会感到熟悉。
快速入门(3步)
-
安装Revit插件。 构建并部署C#插件——参见手动设置。这部分是实际与Revit通信的部分。
-
将你的AI客户端指向MCP服务器。 无需克隆——它直接从npm运行:
-
**打开Revit,在功能区启用MCP服务,然后开始询问。
本页由 AI 翻译,技术细节请以原文为准。
README
以下为原文 README 节选,完整内容请查看原文。
Revit MCP - AI-Powered Revit Control
English | 繁體中文
Revit MCP lets AI clients call Autodesk Revit tools through the Model Context Protocol (MCP). The MCP server forwards tool calls to a local Revit add-in, and the add-in executes the corresponding Revit API workflow.
- Demo video: Revit MCP - AI-Powered BIM Workflow Demonstration
- Knowledge site:
- Default WebSocket port:
8964
What is this?
Talk to Revit in plain language. Ask your AI client to “dimension every wall on this view” or “check the curtain-wall elevations”, and Revit does it — through 239 MCP tools backed by 90 professional BIM SOPs (building code, quantity take-off, compliance checks).
Who it’s for: BIM engineers and architects who use Revit and want AI-assisted, standards-based workflows. You’ll need Revit (2022–2026) on Windows and to be comfortable installing an add-in.
Quickstart (3 steps)
- Install the Revit add-in. Build and deploy the C# add-in — see Manual Setup. This is the half that actually talks to Revit.
- Point your AI client at the MCP server. No cloning needed — it runs straight from npm:
{ "mcpServers": { "revit-mcp": { "command": "npx", "args": ["-y", "@shuotao/revit-mcp-server"] } } } - Open Revit, enable the MCP service in the ribbon, and start asking. Full setup: AI Client Configuration.
Questions or want to show what you built? → Discussions
Current Project Counts
| Item | Count | Source |
|---|---|---|
| Runtime MCP tools | 239 | registerRevitTools() in MCP-Server/src/tools/index.ts |
| Domain SOP files | 94 | domain/*.md except README.md, plus domain/references/*.md |
| Claude skills | 61 | .claude/skills/*/SKILL.md |
When these numbers change, update CLAUDE.md, README.zh-TW.md, this file, docs/DOCUMENT_AUDIENCE_INVENTORY.md, and run:
.\scripts\verify-qaqc.ps1 -SkipBuild -SkipDeploy
New: Interactive Clash Viewer (MCP Apps)
detect_clashes can now render an interactive clash-review UI inline in the conversation, via the MCP Apps extension (io.modelcontextprotocol/ui). This requires an MCP host that supports the extension. It is purely additive:
- Interactive rendering only happens in GUI hosts that support MCP Apps (Claude Desktop, the claude.ai web app, VS Code GitHub Copilot). A terminal CLI like Claude Code can’t render the panel and always shows the text result — this is expected, not a fault.
- Hosts without MCP Apps support keep getting
detect_clashes’s normal text result — nothing changes for them.
安装
npx -y @shuotao/revit-mcp-server配置
{ "mcpServers": { "revit-mcp": { "command": "npx", "args": ["-y", "@shuotao/revit-mcp-server"] } } }