revit_mcp

The Revit MCP Server acts as a bridge between Claude AI and Autodesk Revit, enabling real-time interaction with Revit models over a WebSocket connection. It implements the Model Context Protocol (MCP) to expose model information, element data, and view/level control to Claude, while handling errors gracefully by falling back to mock data when the Revit connection is unavailable. Once running, you can connect Claude to the server to query model metadata, retrieve element properties and geometry, filter elements, and navigate views and levels within a Revit model.

To use the server, start it with the configured Node command and ensure the Revit WebSocket plugin is accessible at the configured host and port. The server exposes capabilities such as model information (name, path, version, modification date), element counts, element querying with filters, and view/level management. If the connection to Revit cannot be established, the server will transparently switch to mock data to keep workflows moving. Configure the Revit connection settings via environment variables (REVIT_HOST and REVIT_PORT) or adjust the server startup script as needed. The integration with Claude Desktop can then be configured by pointing Claude to the server under an mcpServers entry, enabling Claude to issue MCP queries and receive structured responses about the Revit model in real time.

Prerequisites:

• Node.js v14 or higher
• npm
• Autodesk Revit (2023 or later)
• Revit WebSocket Plugin (companion plugin)

Step-by-step installation:

1. Install dependencies

npm install

2. Build the server

npm run build

3. (Optional for development) Enable auto-rebuild during development

npm run watch

4. Configure environment variables (example)

export REVIT_HOST=127.0.0.1
export REVIT_PORT=8080

5. Run the server (as defined in mcp_config, via Node with the built index)

node build/index.js

6. Verify the MCP endpoint is reachable and the WebSocket connection to the Revit plugin can be established.

If you are integrating with Claude Desktop, ensure Claude is configured to point to the server entry in your Claude config file (e.g., claude_desktop_config.json) under the mcpServers section.

Tips and tips:

• Ensure REVIT_HOST and REVIT_PORT correctly point to the Revit WebSocket plugin. The server will attempt to connect and fall back to mock data if the connection fails.
• Check logs for connection status, especially during startup and when Revit becomes available/unavailable.
• If you modify environment variables, restart the server to apply changes.
• The server exposes a WebSocket API for real-time model data; use the MCP Inspector (npm run inspector) for debugging MCP traffic.
• When deploying, consider mounting configuration via environment variables or a config file to simplify re-deploys and environment consistency.