Revit MCP server

Enables AI interaction with Autodesk Revit models for design assistance, analysis, and BIM workflow integration through a WebSocket connection.
Back to servers
Provider
PiggyYan
Release date
Apr 07, 2025
Language
TypeScript
Stats
5 stars

This MCP server enables seamless communication between Claude AI and Autodesk Revit, providing a bridge that allows direct interaction with Revit models through WebSocket connections. It implements the Model Context Protocol to facilitate real-time access to Revit model information, element querying, and view management.

Installation and Setup

Prerequisites

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

Installing the Server

Install all required dependencies:

npm install

Build the server:

npm run build

For development with automatic rebuilding:

npm run watch

Configuration Options

The server can be configured using environment variables:

REVIT_HOST=127.0.0.1    # Revit plugin WebSocket host
REVIT_PORT=8080         # Revit plugin WebSocket port

Integrating with Claude Desktop

To integrate the MCP server with Claude Desktop, you need to add the server configuration to Claude Desktop settings:

Windows Configuration

Add the following to the Claude Desktop configuration file located at:

%APPDATA%/Claude/claude_desktop_config.json

Use this configuration format:

{
  "mcpServers": {
    "revit-mcp-server": {
      "command": "D:/path/to/revit-mcp-server/build/index.js"
    }
  }
}

Using the MCP Server

The server provides several key functionalities:

Model Information Access

  • Access basic model metadata (name, path, version)
  • Retrieve element counts and last modification date
  • Get real-time model state synchronization

Element Management

  • Query elements with flexible filtering options
  • Access element properties and geometry information
  • Perform batch operations on multiple elements

View and Level Control

  • List all available views in the model
  • Access level information for the project
  • Navigate through the model hierarchy

Debugging

For troubleshooting and debugging the MCP communication:

  1. Use the built-in MCP Inspector:

    npm run inspector
    
  2. Monitor WebSocket communication with the Revit plugin

  3. Check server logs for connection and operation status

Error Handling Features

The server implements robust error handling mechanisms:

  • Automatic fallback to mock data when Revit connection fails
  • Detailed error logging for troubleshooting
  • Graceful connection recovery after interruptions

How to add this MCP server to Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "cursor-rules-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "cursor-rules-mcp"
            ]
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.

Want to 10x your AI skills?

Get a free account and learn to code + market your apps using AI (with or without vibes!).

Nah, maybe later