RevitDocs.Mcp
A Revit API documentation retrieval server based on the MCP protocol that communicates with local AI clients via STDIO. It provides versioned, read-only documentation and code search tools to mitigate API hallucination when AI generates Revit code.
Timeline (last 90 days)
RevitDocs.Mcp is a server based on the MCP protocol, developed by the team of the Vietnamese YouTube channel Kỹ Sư Giấy (Paper Engineer), used to retrieve Revit API documentation before AI writes Revit code in order to avoid API hallucination.
RevitDocs.Mcp communicates with local AI clients via STDIO, runs outside Revit, is completely decoupled from the Revit process, and does not require any AI vendor's API key.
RevitDocs.Mcp provides four read-only tools: Revit Docs search (search API documentation by version), Revit Docs read (read the content of a documentation page), Revit Codes search (search sample code in reviewed sources), and Revit Docs sources (list available documentation sources and their status).
The Revit Docs search tool makes version an explicit required parameter, forcing the AI to declare the target Revit version to avoid cross-version confusion.
RevitDocs.Mcp has not yet released an official version, so users must build it from source, and the project is based on .NET 10.
The RevitDocs.Mcp project produced 27 commits within 30 days, indicating a fairly active development pace.
Encoding domain constraints into tool design (such as making version an explicit parameter) is an effective way to constrain AI behavior through interface signatures, which is more reliable than repeatedly admonishing in prompts, and is worth other CAD/BIM-related MCP servers learning from.
The above information comes from a video introduction from the single source Kỹ Sư Giấy, and independent verification and third-party reviews of this project in the developer community have not yet appeared.
All Facts (8)
RevitDocs.Mcp is a server based on the MCP protocol, developed by the team of the Vietnamese YouTube channel Kỹ Sư Giấy (Paper Engineer), used to retrieve Revit API documentation before AI writes Revit code in order to avoid API hallucination.
50%UnverifiedRevitDocs.Mcp communicates with local AI clients via STDIO, runs outside Revit, is completely decoupled from the Revit process, and does not require any AI vendor's API key.
50%UnverifiedRevitDocs.Mcp provides four read-only tools: Revit Docs search (search API documentation by version), Revit Docs read (read the content of a documentation page), Revit Codes search (search sample code in reviewed sources), and Revit Docs sources (list available documentation sources and their status).
50%UnverifiedThe Revit Docs search tool makes version an explicit required parameter, forcing the AI to declare the target Revit version to avoid cross-version confusion.
50%UnverifiedRevitDocs.Mcp has not yet released an official version, so users must build it from source, and the project is based on .NET 10.
50%UnverifiedThe RevitDocs.Mcp project produced 27 commits within 30 days, indicating a fairly active development pace.
50%UnverifiedEncoding domain constraints into tool design (such as making version an explicit parameter) is an effective way to constrain AI behavior through interface signatures, which is more reliable than repeatedly admonishing in prompts, and is worth other CAD/BIM-related MCP servers learning from.
50%UnverifiedThe above information comes from a video introduction from the single source Kỹ Sư Giấy, and independent verification and third-party reviews of this project in the developer community have not yet appeared.
50%