개요

Revit API의 absurd 표면 영역 때문에, AI 종종 Hallucinates 클래스, 방법, 속성, 또는 전체 네임스페이스. 또한, 유용한, API의 unofficial 또는 uncommon 용도는 AI가 없는 틈새입니다 의 지식. 이 MCP 서버는 Revit API에 LLMs 액세스를 제공합니다. 문서 및 기타 관련 내용 (see) Rvt Docs Tbc Embedder). 이름 * 후드, 그것은 rvtdocs.com과 revitapidocs.com 모두 사용, 활성화 하는 경우, 건축 Coder 블로그.

MCP 클라이언트에게 Revit API docs가 뭔가와 그것에 대해 말한 것 자체에서 API docs를 탐구하는 도구의 조합을 사용합니다.

특징

• 검색 Revit API: 클래스, 방법 및 속성 검색 (또는 API Revit API 문서의 엔터티).
• 액세스 문서: API entity의 docs 페이지의 내용을 검색 url 또는 entities 이름을 통해.
• 검색/액세스 TBC 블로그: 벡터 공간에 대한 검색 수행 건축 Coder 블로그 embeddings.

특징 (예정)

-Code Examples: Revit API 사용 예제를 가져와 이용안내 이름 * RevitSdkSamples.com에 관하여 또는 어쩌면

Revit API MCP Server

Overview

Because of the absurd surface area of the Revit API, AI often hallucinates classes, methods, properties, or even entire namespaces. Furthermore, useful, but unofficial or uncommon uses of the API are so niche that AI’s have no knowledge of it. To curb this, this MCP server provides LLMs access to Revit API documentation and other related content (see Rvt_Docs_Tbc_Embedder). Under the hood, it uses both rvtdocs.com and revitapidocs.com, and if enabled, the Building Coder Blog.

Simply ask your MCP client what the Revit API docs say about something and it will use a combination of tools to explore the API docs on its own.

Features

• Search Revit API: Search for classes, methods, and properties (or any API entity) in the Revit API documentation.
• Access Documentation: Retrieve the content of an API entity’s docs page either via the url or the entities name.
• Search/Access TBC Blog: Perform semantic search over a vector space of The Building Coder blog embeddings.

Features (Planned)

• Code Examples: Get code examples for Revit API usage and make them accessible. See RevitSdkSamples. Or maybe even entire repos, like those from ricuan-io, Nice3point, chuongmep, kilkellym, and of course jeremytammik.
• More Resources: Add other content to the vector store. Candidates include tbc-related pdfs, random blog posts, and Autodesk University resources.
• Caching (Unlikely): Cache responses to reduce traffic to the api doc sites.

Tools

This repository provides four MCP tools for working with Revit API documentation:

• search-docs - Search Revit API documentation to find entities matching your query. Returns entity names, descriptions, namespaces, types, and URL slugs for further exploration (but not the documentation itself).

• retrieve-doc - Retrieve a single Revit API documentation page using its URL slug. Use this after getting a URL slug from a search operation.

• retrieve-docs - Get full documentation content for multiple Revit API entities based on a search query. Useful when you need complete documentation content, not just search results.

• search-library - Search a comprehensive library of Revit API learning resources including blog posts, code examples, PDFs, and practical guides. Powered by OpenAI’s vector store for semantic search.

Setup

Download the executable for your OS from Releases. Or you can clone and build from source using deno task compile. Add this executable somewhere in your file system that makes sense. Good practice for Windows is /bin/, but it can be anywhere.

Run path\to\executable -h in your terminal to see the help menu. FYI: This executable is useless to run in the terminal besides for the help menu and for