xml.Revit.MCP Tools Overview
xml.Revit.MCP provides a comprehensive set of tools for integrating with Autodesk Revit through the Model Context Protocol (MCP). This library serves as a bridge between AI assistants and Revit, enabling powerful automation capabilities and programmatic interaction with building models.
Key Features
The tool library includes numerous functions for Revit automation and interaction:
Basic Operations:
- Get available commands from Revit plugin
- Execute specified commands in Revit
- Call specific Revit functions with parameters
- Retrieve view data and selected elements
Element Management:
- Find elements by category
- Get element parameters and locations
- Update element parameters
- Delete elements
- Show/highlight elements in current view
- Move elements to new positions
Creation Tools:
- Create levels/floors
- Create floor plan views
- Create grid lines
- Create walls and floors
- Create rooms and room tags
- Create doors and windows
- Create MEP elements (ducts, pipes, cable trays)
- Create family instances
- Link DWG files
- Create sheets
Installation Requirements
- xml.Revit: Version 1.3.4.3 or newer
- Python: 3.10 or newer
- UV Package Manager: Required for installation
- Revit: Compatible with versions 2019-2024 (with plugin)
Installation Process
-
First, install the UV package manager:
pip install uv
-
Install the revit-mcp package:
pip install revit-mcp
-
Test the installation:
uvx revit-mcpYou should see:
RevitMCPServer - INFO - Successfully connected to Revit on startup
Integration with AI Assistants
Claude for Desktop
Edit claude_desktop_config.json to include:
{
"mcpServers": {
"RevitMCPServer": {
"command": "uvx",
"args": [
"revit-mcp"
]
}
}
}
Cursor
Edit mcp.json to include:
{
"mcpServers": {
"RevitMCPServer": {
"command": "uvx",
"args": [
"revit-mcp"
]
}
}
}
Cline
Edit cline_mcp_setting.json to include:
{
"mcpServers": {
"RevitMCPServer": {
"command": "uvx",
"args": [
"revit-mcp"
]
}
}
}
Extending Functionality
You can create custom MCP服务功能 files to implement additional functionality by:
- Implementing the
xml.Revit.MCP.Public.IMCPMethodinterface - Following JSON-RPC 2.0 specification for communication
- Compiling to a DLL and placing it in the designated MCP folder
Plugin Configuration
When using the xml.Revit.MCPServer:
- Register the plugin with Revit
- Configure commands through: Add-in Modules → Revit MCP Plugin → Settings
- Enable the service: Add-in → Revit MCP Plugin → Revit MCP Switch
Once enabled MCP服务, AI assistants can discover and control your Revit program, executing the various commands provided by the xml.Revit.MCP tools library.
1 maintainer
Metadata
1 maintainer
Release files for revit-mcp 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| revit_mcp-1.0.1.tar.gz | 33.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| revit_mcp-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 69.6 kB
Release files / revit_mcp-1.0.1.tar.gz
| Download URL | revit_mcp-1.0.1.tar.gz |
|---|---|
| Size | 33.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a5edd628f99cc002feed110001cf032cc9eef5b0c8dcfbfa3687da2501daf083
|
|
BLAKE2b-256 checksum How to use checksums |
fadf37742e96e39693dc3c87278907e80c4fbd450c4d7448097873cbde296a52
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.0
|
Release files / revit_mcp-1.0.1-py3-none-any.whl
| Download URL | revit_mcp-1.0.1-py3-none-any.whl |
|---|---|
| Size | 36.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b20b4da2b1f5cf0e437304c4fe4289f3f6db4052f3c7d01339e4ee89b133b43f
|
|
BLAKE2b-256 checksum How to use checksums |
885bd795ce1ce4d57b6440a7a328349c5453fd8ef1024b16208bd92aa4ffdac5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.0
|
Security for revit-mcp 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
