RVTDocs MCP
The RVTDocs MCP server provides deterministic, token-efficient querying of Revit API documentation for use in AI agent workflows.
rvtdocs_fetch: Primary lookup with three output modes —trust(metadata only, ~300 chars),full(includes snippet, ~2500 chars), ordiagnostics(snippet + resolver/semantic trace metadata)rvtdocs_scan: Lightweight existence check with minimal token output and no snippetrvtdocs_debug: Full diagnostic fetch with detailed routing/extraction trace metadata for troubleshootingrvtdocs_batch: Execute up to 10 concurrent lookups in a single tool call to reduce overhead when researching related APIsrvtdocs_stats: Retrieve local telemetry — tool call counts, success rates, cache hit rates, and top queries/failures over a configurable time window (default 24 hours)rvtdocs_version_info: Get supported Revit API documentation years, default year, and cache statsrvtdocs_schema: Return JSON schemas for all available tools for external validationrvtdocs_session_set/rvtdocs_session_get: Store and retrieve ephemeral key-value pairs in a session store (max 100 entries, LRU eviction) to cache resolved API info between tool calls
Provides tools for searching, scanning, diffing, and fetching Revit API documentation across multiple versions.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@RVTDocs MCP fetch documentation on setup"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
rvtdocs-mcp
Local-first MCP server for Revit API documentation. Downloads once, searches instantly.
Tools
Tool | Purpose | Latency |
| Keyword search across 28K+ API entries | ~7ms |
| Browse namespace or class members | ~1ms |
| Compare APIs between Revit versions | ~1ms |
| Fetch full page documentation | 50-500ms |
Related MCP server: Context7 Private Docs MCP
How it works
On first query per year, downloads the API tree index from rvtdocs.com (~7MB)
Caches permanently in
%APPDATA%/rvtdocs-mcp/(Windows) or~/.cache/rvtdocs-mcp/(Unix)Builds in-memory searchable index (28K entries, ~350ms load)
All search/scan/diff are local with <10ms latency
Workflow
# 1. Explore with vague query (zero prior knowledge needed)
rvtdocs_search(query="electrical circuit", year="2025")
-> namespaces, classes, methods ranked by relevance
# 2. Browse discovered namespace
rvtdocs_scan(target="Autodesk.Revit.DB.Electrical", types="class")
-> 78 classes in that namespace
# 3. Check version compatibility
rvtdocs_diff(from_year="2025", to_year="2027", scope="Autodesk.Revit.DB.Structure")
-> +181 added, -40 removed (classes + methods)
# 4. Fetch detail for specific API
rvtdocs_fetch(url="https://rvtdocs.com/2025/Autodesk.Revit.DB.Connector")
-> full documentation with description, methods table, remarksInstall
From git (production)
{
"mcpServers": {
"rvtdocs-mcp": {
"type": "stdio",
"command": "uvx",
"args": ["--from", "git+https://github.com/trgiangv/rvtdocs-mcp.git", "rvtdocs-mcp"]
}
}
}From local source (development)
{
"mcpServers": {
"rvtdocs-mcp": {
"type": "stdio",
"command": "uvx",
"args": ["--from", "/path/to/rvtdocs-mcp", "rvtdocs-mcp"]
}
}
}Requirements
Python >= 3.12
Dependencies:
mcp,httpx,trafilatura
Supported Revit versions
2022, 2023, 2024, 2025, 2026, 2027
Available Tools
9 toolsrvtdocs_batchB
Batch-fetch multiple RVTDocs queries in a single tool call.
Reduces tool-call overhead when looking up related APIs. Returns a list of results, one per query, plus aggregate stats.
mode:
trust (default): lean payload per query
full: include snippet per query
Inputs: queries (required), mode, year, max_chars.
rvtdocs_debugC
Run diagnostic fetch with snippet and resolver/semantic trace metadata.
Inputs: query (required), year, max_chars.
rvtdocs_fetchC
Fetch RVTDocs in single-fetch mode with trust-gate output shaping.
mode:
trust (default): lean payload, snippet removed to minimize output tokens
full: include snippet for detailed inspection
diagnostics: include snippet and return resolver/semantic trace metadata
Inputs: query (required), mode, year, max_chars.
rvtdocs_scanC
Resolve and trust-check a query with minimal output for low token cost.
Inputs: query (required), year, max_chars.
rvtdocs_schemaA
Return JSON schemas for all rvtdocs tools for external validation.
Inputs: no named parameters.
rvtdocs_session_getC
Retrieve a value from the session store.
Inputs: key (required).
rvtdocs_session_setA
Store a key-value pair in the session store.
Useful for caching resolved API info between tool calls. Data is ephemeral (lost on server restart).
Inputs: key (required), value (required).
rvtdocs_statsB
Query usage statistics for the rvtdocs MCP server.
Returns tool call counts, success rates, cache hit rates, and top queries/failures for the specified time period.
Inputs: hours.
rvtdocs_version_infoA
Returns supported Revit API documentation versions and recommendations.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Multiple tools (rvtdocs_fetch, rvtdocs_scan, rvtdocs_debug, rvtdocs_batch) serve similar fetching purposes with only subtle differences in output mode and verbosity. While descriptions clarify some distinctions, an agent may easily misselect among them.
All tools share the 'rvtdocs_' prefix, but the second part mixes verbs (fetch, scan, debug) with nouns (schema, stats, version_info) and verb_noun pairs (session_get, session_set). This inconsistency, though not chaotic, reduces predictability.
With 9 tools, the server is well-scoped. Each tool serves a distinct purpose (fetching, session management, schema, stats, version info) without bloat or triviality.
The tool surface covers core needs: fetching docs (multiple modes), session caching, schema validation, statistics, and version info. Minor gaps like a dedicated search or listing tool are absent, but the domain is narrow and the set feels functional.
Related MCP Connectors
Versioned documentation registry and semantic search for AI tools and coding assistants.
Provides access to Google's public developer documentation.
Docsy gives AI assistants current, version-specific documentation for libraries, frameworks and SDKs. Resolve library IDs and versions, then search and fetch focused official documentation with original source links using five read-only MCP tools. Hosted Streamable HTTP with OAuth 2.1 sign-in.
Search and read Apple developer documentation, HIG, and WWDC transcripts as Markdown.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceDirect access to the Revit API docs and related content.31-
- AlicenseNot gradedqualityDmaintenanceEnables querying private documentation with tools for version resolution, stale reference checking, and receipt export.MIT
- AlicenseNot gradedqualityCmaintenanceProvides MCP tools for searching and navigating a built Sphinx documentation site, exposing page contexts, headings, metadata, and navigation structure.MIT
- AlicenseBqualityBmaintenanceEnables coding agents to access extracted Source 2 documentation data and resources for writing cs_script, Hammer logic, configs, and mods with verified names.73MIT