Revit MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| color_elementsA | Color elements in the current view based on a category and parameter value. Each unique parameter value gets assigned a distinct color. |
| 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). |
| 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). |
| 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). |
| delete_elementA | Delete one or more elements from the Revit model by their element IDs. |
| 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. |
| 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. |
| get_current_view_infoA | 获取 Revit 当前活动视图的详细信息，包括视图类型、名称、比例等属性。 |
| get_selected_elementsB | Get elements currently selected in Revit. You can limit the number of returned elements. |
| operate_elementC | Operate on Revit elements by performing actions such as select, selectionBox, setColor, setTransparency, delete, hide, etc. |
| 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. |
| tag_all_wallsA | Create tags for all walls in the current active view. Tags will be placed at the middle point of each wall. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
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.
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.
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.
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.