Autodesk Revit向けのモデルコンテキストプロトコル(MCP)のpyRevit志向実装

ローカルペアリングとAutodesk Marketplaceでの出版物

このプロジェクトはAutodesk Marketplaceの審査準備中です。まだ認証は取得していません。 審査候補者はPython実行を含む20のツールすべてを保持します。参照 出版要件と未完成の門檻、 プライバシー情報とセキュリティの境界線。

pyRevit拡張機能をインストールした後、RevitでMCP > Bridge > Connectを選択してください 同意し、Windowsユーザーのために暗号化されたペアリング秘密を作成すること。選択 **切断すると取り消します。モデルやPython実行を変更するリクエストは表示されます ペイロードはRevitでレビューしてから進むことができます。ペアリングもローカル化を可能にします Revitの発見と起動。ペアリングは同じRevitインスタンス間で共有されます Windowsユーザー;接続前に正しいルートポートを選択してください。

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.