Skip to main content
Glama

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: Revit MCP Server

GitHub Copilot Compatibility

This MCP server has been updated to be fully compatible with GitHub Copilot. The tool schemas now properly include the required items property for array parameters, resolving validation errors that previously occurred when using array-type parameters with GitHub Copilot's MCP client.

  • 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.

GitHub Copilot

GitHub Copilot supports MCP servers natively. Configure the server in your VS Code settings or workspace configuration:

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

Restart VS Code or reload the window to apply the configuration.

claude

Framework

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

Supported Tools

Name

Description

get_current_view_info

Get current view info

get_current_view_elements

Get current view elements

get_available_family_types

Get available family types in current project

get_selected_elements

Get selected elements

create_point_based_element

Create point based element (door, window, furniture)

create_line_based_element

Create line based element (wall, beam, pipe)

create_surface_based_element

Create surface based element (floor, ceiling)

delete_elements

Delete elements

reset_model

Reset model (delete process model when executing continuous dialog)

modify_element

Modify element's properties (instance parameters)

search_modules

Search for available modules

use_module

Use module

send_code_to_revit

Send code to Revit to execute

color_splash

Color elements based on a parameter value

tag_walls

Tag all walls in view

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, but there is some overlap between ai_element_filter, get_current_view_elements, and get_selected_elements in retrieving elements, which could cause confusion. However, their specific focuses (intelligent querying, current view, selected elements) help differentiate them. Other tools like create_line_based_element and create_surface_based_element are clearly distinct based on element type.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern (e.g., create_line_based_element, delete_element, get_available_family_types) with minor deviations. One tool, operate_element, uses a vague verb 'operate' instead of something more specific like 'modify', and send_code_to_revit is slightly less structured, but overall the pattern is clear and readable.

    Tool Count5/5

    With 13 tools, this is well-scoped for a Revit MCP server covering element creation, querying, modification, and execution. Each tool serves a specific function in the domain, such as creating different element types or retrieving element information, without being overly bloated or sparse.

    Completeness4/5

    The tool set provides good coverage for core Revit operations, including creation (point, line, surface-based), deletion, querying, and modification. Minor gaps exist, such as no explicit tool for updating element parameters beyond color or transparency, and the domain could benefit from more specialized tools for tasks like scheduling or exporting, but agents can work around these with existing tools like operate_element or send_code_to_revit.

    Related MCP Connectors

    Related MCP Servers