Autodesk Revit용 모델 컨텍스트 프로토콜(MCP)의 pyRevit 지향 구현

로컬 페어링과 Autodesk Marketplace 출판물

이 프로젝트는 Autodesk Marketplace 검토를 위해 준비 중이며; 아직 인증되지 않았습니다. 검토 후보자는 파이썬 실행을 포함한 20개 모든 도구를 유지합니다. 참조 출판 요건과 뛰어난 게이트 기록, 개인정보 보호와 보안 경계.

pyRevit 확장 프로그램을 설치한 후, Revit에서 MCP > Bridge > Connect를 선택하세요 동의하고 Windows 사용자를 위한 암호화된 페어링 비밀을 생성하는 것입니다. 선택하세요 연결을 끊으세요 취소하세요. 모델 변경 요청과 Python 실행 시 표시됩니다 진행 전에 Revit에서 검토할 페이로드를 제공합니다. 페어링은 또한 로컬 작업을 허용합니다. Revit 발견 및 실행. 동일 Revit 인스턴스 간에 페어링이 공유됩니다 Windows 사용자; 연결 전에 올바른 Routes 포트를 선택하세요.

MCP에서 Revit으로의 브리지는 루프백 호스트만 받습니다. 원격 VM/LAN HTTP 브리지는 거부됨. 선택적 HTTP MCP 전송은 쌍 베어러 헤더를 필요로 하며; stdio는 추천된 퍼블리블 전송 방식이며 클라이언트 구성에서는 토큰이 필요 없습니다. 어느 쪽도 네트워크, 터널, 인터넷에 노출하지 마세요.

MCP server for Revit - Python

A pyRevit-oriented implementation of the Model Context Protocol (MCP) for Autodesk Revit

Local pairing and Autodesk Marketplace publication

This project is being prepared for Autodesk Marketplace review; it is not yet certified. The review candidate retains all 20 tools, including Python execution. See publication requirements and outstanding gates, privacy information, and security boundaries.

After installing the pyRevit extension, choose MCP > Bridge > Connect in Revit to consent and create an encrypted pairing secret for your Windows user. Choose Disconnect to revoke it. Requests that change models and Python execution show their payload for review in Revit before proceeding. Pairing also permits local Revit discovery and launch. Pairing is shared across Revit instances for the same Windows user; select the correct Routes port before connecting.

The MCP-to-Revit bridge accepts only loopback hosts. Remote VM/LAN HTTP bridges are rejected. Optional HTTP MCP transports require a paired bearer header; stdio is the recommended publication transport and needs no token in client configuration. Do not expose either listener to a network, tunnel or the internet.

How?

• This minimal implementation leverages the Routes module inside pyRevit to create a bridge between Revit and Large Language Models (LLMs).
• It provides a straightforward template to get started quickly, letting you prototype and iterate tools to give LLMs access to your Revit models.
• These tools are designed to be expanded for your specific use cases. You’re very welcome to fork the repo and make your own contributions.
• Note: The pyRevit Routes API is currently in draft form and subject to change. This extension authenticates its own routes using Windows-user pairing. Other pyRevit routes/extensions remain outside this protection; review pyRevit server binding and the security document.

Batteries Included

This repo is aimed at:

• Beginners to the Revit API
• Python specialists who aren’t versed in C#
• Anyone wanting to prototype and iterate quickly with LLMs and Revit

It contains:

• A complete Routes implementation for pyRevit
• A minimal MCP server script to connect to any MCP-compatible client
• Several test commands to get you started right away

Key Architecture Components

The system runs as two separate servers working together in a chain:

Claude / LLM Client
       |
       |  MCP Protocol (stdio or HTTP)
       v
  main.py  (MCP Server)
       |
       |  HTTP requests (localhost:48884)
       v
  pyRevit Routes  (REST API running inside Revit)
       |
       |  Revit API calls
       v
  Revit Application

main.py is the MCP server. It speaks the MCP protocol so that Claude (or any MCP-compatible client) can call tools. When a tool is called, main.py translates it into an HTTP request and forwards it to Revit.