Skip to main content
Glama

πŸ—οΈ Revit MCP Server

A Model Context Protocol server for Revit integration, enabling seamless communication between Claude AI and Autodesk Revit.

English | δΈ­ζ–‡

🎯 Overview

This TypeScript-based MCP server provides a bridge between Claude AI and Revit, allowing direct interaction with Revit models through a WebSocket connection. It implements the Model Context Protocol to enable:

  • ⚑ Real-time access to Revit model information

  • πŸ” Element querying and filtering

  • πŸ‘€ View and level management

  • πŸ›‘οΈ Robust error handling with fallback mock data

Related MCP server: QGISMCP

✨ Features

πŸ”Œ Revit Integration

  • πŸ“‘ WebSocket-based communication with Revit plugin

  • πŸ”„ Real-time model data access

  • πŸ” Graceful fallback to mock data when connection fails

  • βš™οΈ Configurable connection settings via environment variables

πŸš€ Core Functionalities

  • πŸ“Š Model Information

    • Access basic model metadata (name, path, version)

    • Get element counts and last modification date

    • Real-time model state synchronization

  • πŸ—οΈ Element Management

    • Query elements with flexible filtering

    • Access element properties and geometry

    • Batch element operations

  • πŸŽͺ View & Level Control

    • List all available views

    • Access level information

    • Navigate through model hierarchy

πŸ’» Development

πŸ“‹ Prerequisites

  • Node.js (v14 or higher)

  • npm

  • Autodesk Revit (2023 or later)

  • Revit WebSocket Plugin (companion plugin)

πŸ”§ Installation

Install dependencies:

npm install

Build the server:

npm run build

For development with auto-rebuild:

npm run watch

βš™οΈ Configuration

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

πŸ”— Integration with Claude Desktop

Add the server configuration to Claude Desktop:

Windows:

%APPDATA%/Claude/claude_desktop_config.json

Configuration format:

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

πŸ› Debugging

For debugging the MCP communication:

  1. Use the built-in MCP Inspector:

npm run inspector
  1. Monitor WebSocket communication with Revit plugin

  2. Check server logs for connection and operation status

⚠️ Error Handling

The server implements robust error handling:

  • Automatic fallback to mock data when Revit connection fails

  • Detailed error logging

  • Graceful connection recovery

πŸ“„ License

MIT License

🀝 Contributing

Contributions are welcome! Please feel free to submit pull requests.

πŸ“¬ Contact

If you have any questions or suggestions, feel free to reach out:

Available Tools

6 tools
get_categoriesB

θŽ·ε– Revit ζ¨‘εž‹δΈ­ηš„ζ‰€ζœ‰η±»εˆ«

Inputs: no named parameters.

get_element_infoC

θŽ·ε– Revit ε…ƒη΄ ηš„θ―¦η»†δΏ‘ζ―

Inputs: elementId (required), getItemPropertyInfo, getItemParameterInfo.

get_elementsC

θŽ·ε– Revit ζ¨‘εž‹δΈ­ηš„ε…ƒη΄ 

Inputs: categoryIds, viewIds, levelIds.

get_familiesC

θŽ·ε– Revit ζ¨‘εž‹δΈ­ηš„ζ‰€ζœ‰ζ—

Inputs: categoryId, name.

get_levelsB

θŽ·ε– Revit ζ¨‘εž‹δΈ­ηš„ζ‰€ζœ‰ζ₯Όε±‚

Inputs: no named parameters.

get_viewsB

θŽ·ε– Revit ζ¨‘εž‹δΈ­ηš„ζ‰€ζœ‰θ§†ε›Ύ

Inputs: no named parameters.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting different Revit model components: categories, element info, elements, families, levels, and views. There is no overlap in functionality, and an agent can easily distinguish between them based on the specific resource each retrieves.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with 'get_' as the prefix and a plural or singular noun describing the resource. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming style.

    Tool Count4/5

    With 6 tools, the count is reasonable for a Revit model server, covering key retrieval operations. However, it might be slightly under-scoped as it lacks tools for creating, updating, or deleting elements, which could be expected in a full Revit integration.

    Completeness2/5

    The tool set is severely incomplete for a Revit domain, as it only provides read-only retrieval operations. There are significant gaps in CRUD coverageβ€”no tools for creating, updating, or deleting elements, categories, families, etc., which will likely cause agent failures when trying to modify models.

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Connects QGIS to Claude AI through the Model Context Protocol, enabling AI-assisted project creation, layer manipulation, processing algorithm execution, and Python code running within QGIS.
      7
      -
    • A
      license
      B
      quality
      D
      maintenance
      Connects Blender to Claude AI through the Model Context Protocol, enabling AI-assisted 3D modeling, scene creation, and manipulation through natural language commands.
      17
      2
      MIT
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants like Claude to interact with Autodesk Construction Cloud Build platform for construction project management, including issues tracking, RFIs, submittals, and document management through natural language.
      -