Add Revit MCP server to Official Integrations list

[NonicaTeam]

Add Revit MCP server to the Official Integrations list

Description

This PRO adds the Revit MCP server to the Official Integrations list in file README. Revit MCP provides access for LLM clients to interact with Revit models live with a set of 36 specialized tools.

Server Details

• Server: Revit MCP (new addition to the Official Integrations list) repo
• Changes to: README.md - added entry to Official Integrations section

Motivation and Context

Revit is one of the most popular software solutions in the building enviroment with an estimated of more than 20 million users worldwide. This MCP server allows to connect and interact with:
-Element and type properties. Helpful to find inconsistent or lacking data in the model (for instance if the material of a wall is missing the model).
-Elements locations and geometric properties. Helpful to find clashes between geometry or make accurate representations and analysis.
-Set and extract selection. Helpful to find and present results to the user.
-Project information and metadata: Access project-wide settings, units, phases, and design options. Helpful for project coordination and ensuring consistent standards across the model.
-Graphic overrides and view-specific settings: Analyze painted elements, view filters, and visual overrides per view. Helpful to understand presentation intent and maintain graphic standards.
(among others)
This server fills the gap between LLMs and Revit, integrating, automating and bringing intelligence to Revit workflows.

How Has This Been Tested?

The server has been tested extensively, including:
-Claude Desktop integration and different models (from Haiku to Opus in Claude 4)
-36 specialized tools working with different Revit models/versions and scenarios.
-Unit tests presented a 100% pass rate.
-Beta release with more than 100 users involved.

Breaking Changes

No breaking changes - this is just an addition to Official Integrations list.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Protocol Documentation
• My changes follows MCP security best practices
• I have updated the server's README accordingly
• I have tested this with an LLM client
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have documented all environment variables and configuration options

Additional context

-Repository: https://github.com/NonicaTeam/AI-Connector-for-Revit
-Platform: Windows only (Revit requirement)
-Implementation: C# using official MCP SDK

[NonicaTeam]

Any update?

[NonicaTeam]

Any issue? Could this be added in the next merge?

[olaservo]

Thanks for the submission, will include this in the next batch of updates. 👍

[olaservo]

Thanks for your contribution to the servers list. This has been merged in this combined PR: #2144

This is a new process we're trying out, so if you see any issues feel free to re-open the PR and tag me.