Skip to main content
Glama

🔴

WARNING

Deprecation notice, this repo is being archived in favour of the mono repo approch for the mcphttps://github.com/mcp-servers-for-revit/mcp-servers-for-revit Simpler CI, less confusion for noobs, npm package and simpler install



revit-mcp

English | 简体中文

Description

revit-mcp allows you to interact with Revit using the MCP protocol through MCP-supported clients (such as Claude, Cline, etc.).

This project is the server side (providing Tools to AI), and you need to use revit-mcp-plugin (driving Revit) in conjunction.

Join Discord | QQ Group

Related MCP server: RevitMCPBridge2026

Features

  • Allow AI to get data from the Revit project

  • Allow AI to drive Revit to create, modify, and delete elements

  • Send AI-generated code to Revit to execute (may not be successful, successful rate is higher in some simple scenarios with clear requirements)

Requirements

  • nodejs 18+

Complete installation environment still needs to consider the needs of revit-mcp-plugin, please refer to revit-mcp-plugin

Installation

1. Build local MCP service

Install dependencies

npm install

Build

npm run build

2. Client configuration

Claude client

Claude client -> Settings > Developer > Edit Config > claude_desktop_config.json

{
    "mcpServers": {
        "revit-mcp": {
            "command": "node",
            "args": ["<path to the built file>\\build\\index.js"]
        }
    }
}

Restart the Claude client. When you see the hammer icon, it means the connection to the MCP service is normal.

claude

Framework

flowchart LR
	ClaudeDesktop --> revit-mcp --> SocketService--commandName-->CommandSet--command-->CommandExecute
	CommandManager --> CommandSet
	CommandExecute --executeResult--> SocketService
	CommandProject1 --> CommandManager
	CommandProject2 --> CommandManager
	CommandProject... --> CommandManager
	subgraph ide1 [MCPClient]
	ClaudeDesktop
	end
	subgraph ide2 [MCPServer]
	revit-mcp
	end
	subgraph ide3 [Revit]
			subgraph ide3.1 [revit-mcp-plugin]
				SocketService
				CommandSet
				CommandManager
				CommandExecute
			end
	end

Supported Tools

Name

Description

get_current_view_info

Get current active view info

get_current_view_elements

Get elements from the current active view

get_available_family_types

Get available family types in current project

get_selected_elements

Get currently selected elements

get_material_quantities

Calculate material quantities and takeoffs

ai_element_filter

Intelligent element querying tool for AI assistants

analyze_model_statistics

Analyze model complexity with element counts

create_point_based_element

Create point-based elements (door, window, furniture)

create_line_based_element

Create line-based elements (wall, beam, pipe)

create_surface_based_element

Create surface-based elements (floor, ceiling, roof)

create_grid

Create a grid system with smart spacing generation

create_level

Create levels at specified elevations

create_room

Create and place rooms at specified locations

create_structural_framing_system

Create a structural beam framing system

delete_element

Delete elements by ID

operate_element

Operate on elements (select, setColor, hide, etc.)

color_elements

Color elements based on a parameter value

tag_all_walls

Tag all walls in the current view

tag_all_rooms

Tag all rooms in the current view

export_room_data

Export all room data from the project

store_project_data

Store project metadata in local database

store_room_data

Store room metadata in local database

query_stored_data

Query stored project and room data

send_code_to_revit

Send C# code to Revit to execute

say_hello

Display a greeting dialog in Revit (connection test)

Available Tools

13 tools
ai_element_filterA

An intelligent Revit element querying tool designed specifically for AI assistants to retrieve detailed element information from Revit projects. This tool allows the AI to request elements matching specific criteria (such as category, type, visibility, or spatial location) and then perform further analysis on the returned data to answer complex user queries about Revit model elements. Example: When a user asks 'Find all walls taller than 5m in the project', the AI would: 1) Call this tool with parameters: {"filterCategory": "OST_Walls", "includeInstances": true}, 2) Receive detailed information about all wall instances in the project, 3) Process the returned data to filter walls with height > 5000mm, 4) Present the filtered results to the user with relevant details.

Inputs: data (required).

color_elementsA

Color elements in the current view based on a category and parameter value. Each unique parameter value gets assigned a distinct color.

Inputs: categoryName (required), parameterName (required), useGradient, customColors.

create_line_based_elementA

Create one or more line-based elements in Revit such as walls, beams, or pipes. Supports batch creation with detailed parameters including family type ID, start and end points, thickness, height, and level information. All units are in millimeters (mm).

Inputs: data (required).

create_point_based_elementA

Create one or more point-based elements in Revit such as doors, windows, or furniture. Supports batch creation with detailed parameters including family type ID, position, dimensions, and level information. All units are in millimeters (mm).

Inputs: data (required).

create_surface_based_elementA

Create one or more surface-based elements in Revit such as floors, ceilings, or roofs. Supports batch creation with detailed parameters including family type ID, boundary lines, thickness, and level information. All units are in millimeters (mm).

Inputs: data (required).

delete_elementA

Delete one or more elements from the Revit model by their element IDs.

Inputs: elementIds (required).

get_available_family_typesA

Get available family types in the current Revit project. You can filter by category and family name, and limit the number of returned types.

Inputs: categoryList, familyNameFilter, limit.

get_current_view_elementsA

Get elements from the current active view in Revit. You can filter by model categories (like Walls, Floors) or annotation categories (like Dimensions, Text). Use includeHidden to show/hide invisible elements and limit to control the number of returned elements.

Inputs: modelCategoryList, annotationCategoryList, includeHidden, limit.

get_current_view_infoA

获取 Revit 当前活动视图的详细信息,包括视图类型、名称、比例等属性。

Inputs: no named parameters.

get_selected_elementsB

Get elements currently selected in Revit. You can limit the number of returned elements.

Inputs: limit.

operate_elementC

Operate on Revit elements by performing actions such as select, selectionBox, setColor, setTransparency, delete, hide, etc.

Inputs: data (required).

send_code_to_revitB

Send C# code to Revit for execution. The code will be inserted into a template with access to the Revit Document and parameters. Your code should be written to work within the Execute method of the template.

Inputs: code (required), parameters.

tag_all_wallsA

Create tags for all walls in the current active view. Tags will be placed at the middle point of each wall.

Inputs: useLeader, tagTypeId.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools have distinct purposes, such as ai_element_filter for querying, create_*_element for element creation by type, and delete_element for removal. However, there is some overlap between ai_element_filter, get_current_view_elements, and get_selected_elements, as all retrieve elements but with different scopes (filtered vs. view vs. selected), which could cause confusion if not carefully described. The descriptions help clarify, but the boundaries are not entirely clear-cut.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern for most tools, such as create_line_based_element, delete_element, and get_available_family_types. However, there are minor deviations: ai_element_filter uses a less standard prefix, operate_element is vague compared to others, and tag_all_walls is more specific in naming. Overall, the conventions are readable and mostly uniform, with only slight inconsistencies.

    Tool Count5/5

    With 13 tools, the count is well-scoped for a Revit MCP server covering element creation, querying, deletion, and operations. Each tool appears to serve a distinct function in the BIM workflow, such as creating different element types, filtering, and executing code, making the set comprehensive without being overwhelming. This aligns with typical domain-specific servers that require moderate tool counts for effective coverage.

    Completeness4/5

    The tool set provides strong coverage for core Revit operations, including creation (point, line, surface-based), deletion, querying (filtering, view info, selection), and specialized actions like tagging and coding. Minor gaps exist, such as lack of update or modify tools for existing elements beyond basic operations in operate_element, and no explicit tools for managing views or parameters beyond current view info. However, agents can likely work around these with the available tools, ensuring most workflows are supported.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Autodesk Revit (BIM) with 705+ API endpoints. Enables AI agents to create walls, place doors/windows, generate sheets, manage views, and produce construction documents via the Model Context Protocol. Uses named pipes for zero-crash Revit integration.
      22
      MIT
    • A
      license
      A
      quality
      F
      maintenance
      Enables AI to interact with Revit via MCP, allowing data retrieval and element creation, modification, and deletion.
      13
      59 npm
      MIT