메뉴
Retrieve and analyze Revit API documentation through the local Revit API Docs MCP server. Use when answering questions about Autodesk Revit API classes, methods, properties, version differences, obsolete or changed APIs, migration between Revit 2020-2027, or when writing/reviewing Revit API code that needs authoritative docs.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Create and run CAD/BIM API tests using pytest via RevitDevTool Named Pipe bridge. Use when writing new pytest test files for Revit/AutoCAD/Civil3D API, adding test fixtures for host documents/elements, running tests against a live host instance, setting up conftest.py with PEP 723 dependencies, or asking "how do I test Revit API with pytest". Covers test structure, fixtures, lazy imports, transactions, auto-rollback, dependency injection, and CLI options.
Build and test Revit add-ins with correct configurations for Revit 2022-2027 (NET 4.8, NET 8.0, NET 10.0). Use when building, compiling, testing, packaging Revit projects, or when the user mentions Revit versions, build configurations, testing across multiple Revit versions, or the ModularPipelines build system.
Write pyRevit IronPython tools for Revit with correct project structure, coding conventions, and WPF/MVVM patterns. Use when creating or editing pyRevit pushbutton scripts, shared libs, bundle.yaml, XAML views, or ViewModels.
| name | revit-api-docs |
| description | Retrieve and analyze Revit API documentation through the local Revit API Docs MCP server. Use when answering questions about Autodesk Revit API classes, methods, properties, version differences, obsolete or changed APIs, migration between Revit 2020-2027, or when writing/reviewing Revit API code that needs authoritative docs. |
Use the revit-api-docs MCP server before answering version-sensitive Revit API questions or writing code that depends on Revit API behavior.
The MCP server is remote-first. It does not require a local SQL server, local docs checkout, or manual sync. It creates a private SQLite cache file automatically and uses it only to reduce repeated network and token cost.
2026 unless the project configuration or user request names another version.revit_docs_search(query, version, kind?, namespace?, limit?).revit_docs_get(symbol_or_href, version, sections, max_chars).api_card first to understand purpose, use cases, lifecycle, constraints, and key related APIs.members and related from revit_docs_get to navigate API tables; never manually scrape docs HTML in the agent.revit_docs_compare(from_version, to_version, symbol_or_href).revit_docs_compare(from_version, to_version) without symbol_or_href.search before get; do not fetch pages speculatively.limit <= 8 for search unless the user needs exhaustive discovery.syntax, parameters, remarks, exceptions, examples, or see_also.api_card for the first answer pass; fetch member detail pages only when syntax or edge behavior is needed.members before fetching member detail pages. This is the low-token path for "related API" questions.revit_docs_compare without symbol_or_href.Use this command when configuring a local MCP client from the repo root:
uvx --from .agents/mcp/revit-api-docs revit-api-docs-mcp
Required setup: install uv/uvx, then add the command server to the MCP client.
Optional setup:
REVIT_API_DOCS_CACHE only if the default cache location is not acceptable.REVIT_API_DOCS_SOURCE only when the user explicitly provides a static mirror of the website.Normal use should not set REVIT_API_DOCS_SOURCE; the server should use remote docs plus its auto-created SQLite cache.