Claude Desktop can connect to an open Revit model via Autodesk’s Public MCP for Revit when you install Autodesk’s matching add‑on, configure Claude to launch that local STDIO server, and verify a read against the active document. Start with the Read package, set the executable and arguments exactly as Autodesk documents for your installed build, restart Claude on the same Windows machine, discover tools, then prove a simple query.
What connects Claude Desktop to a Revit model?
Claude Desktop is the MCP client. Autodesk's installed server exposes the Revit tools, and the running model supplies the data. Configuration connects those pieces; it does not turn ordinary chat into unrestricted model access.
Treat the first two milestones separately. A client that lists the server's tools has discovered their descriptions. A successful call against a known element establishes that the selected tool can reach the intended document. This distinction makes both verification and troubleshooting easier.
Check Revit version and choose Read, Write, or Experimental tools
As checked November 4, 2026, Autodesk documents its local STDIO Technical Preview for Revit 2027.2. Confirm the supported build and corresponding add-on before configuration; do not assume another version is covered. Tool packages differ:
• Read: query‑only; does not modify the model.
• Write: includes Read plus supported writes.
• Experimental: evolving, may change and vary by build.Autodesk explains these distinctions in Autodesk’s MCP Revit overview.
Team procedure recommendation: begin with Read to establish reliable discovery and verification in a non‑production context. A successful Read does not prove that Write or Experimental tools will succeed; treat each capability as a separate pilot with its own acceptance criteria.
Set up the Revit MCP server in Claude Desktop
Follow Autodesk’s setup guide for your exact build and chosen package; do not reuse a “universal” JSON from blogs or gists. The documented sequence is:
• Install the Autodesk Revit MCP server add‑on that matches your documented Revit 2027.2 build, then start Revit and open a model.
• In the same Windows environment, open Claude Desktop → Settings → Developer → Edit Config. Add an MCP server using the installed package’s STDIO executable and arguments exactly as documented.
• Ensure valid JSON and properly escaped Windows paths. Save, then fully restart Claude Desktop.
• In a new chat, discover the available tools; treat this as proof of discovery only.Reference: Official setup for the Revit MCP server.
Environment note: Autodesk support states the client and Revit must run in the same Windows environment; a macOS host attempting to reach a Windows VM (e.g., Parallels) is not supported. See Autodesk’s Parallels/VM support note.
Verify a model query before attempting Revit edits
Do not assume tool names or fields. First, inspect the tools exposed by your installed Read package and adapt the verification to what you actually have.
Worked example (hypothetical, adapt to your tools):
1) Establish a ground truth set in Revit
• In the active model, pick a small, known set of elements (for example, five door instances visible in a QA view). Record their ElementIds and one instance parameter that clearly exists on those elements (e.g., Mark if present). Avoid type-only parameters when you intend to validate instance values.
• Use the native element lookup and Properties to check the recorded set. A schedule is useful only when its available fields, itemization, and filters establish the same scope; do not assume ElementId is a standard schedule filter.
2) Run a minimal read via MCP
• Ask Claude to use an available read tool to return: the document context available through the tool, those specific ElementIds, and the chosen instance parameter values for each. State the intended test document explicitly; report unsupported fields rather than inventing them. Do not request edits.
• If your tool requires a category filter, include it; keep the scope tight to the five known elements.
3) Compare membership and parameters
• Membership: The returned ElementIds must match your five recorded Ids—no extras, no omissions.
• Parameter values: For each ElementId, compare the returned instance parameter to Revit’s Properties (or the itemized schedule). Exact match is required; a mismatch indicates tool, filter, or context issues.
4) Interpret outcomes
• Pass: IDs and values match your ground truth. You have proven live model reachability for this read pattern on this build, not for all reads.
• Fail: Investigate filters (wrong category/view context), field selection (type vs instance), or environment (no model open, wrong Windows context). Re-run with a smaller set—sometimes one element—until consistent.
local STDIO transport does not guarantee that everything you ask Claude to return stays on your device; your prompt and tool results may be processed by the client’s service. Align usage with your organization’s data policies.
If you want a primer on the protocol concepts, see our explainer in Revit Model Context Protocol. For context on Autodesk’s 2027 direction, see Revit 2027 AI Review: What’s Real, What Still Isn’t.
Troubleshoot Claude-to-Revit MCP connections
Work from the transport outward and keep evidence from each step.
1) Cannot start the server (configuration layer)
• Symptoms: No tools discovered; errors at launch; Claude can’t attach to a process.
• Checks: Validate that your Claude config is syntactically correct JSON, Windows paths are properly escaped, and the executable/arguments match the installed package and build. Confirm Claude and Revit run in the same Windows environment. Use the paths and flags documented in Official setup for the Revit MCP server.
2) Tools are visible but a live query fails (reachability layer)
• Symptoms: Claude lists tools, but read calls error or return nothing.
• Checks: Ensure a model is open in the running Revit session; the installed add-on is compatible; the client and model are in the documented local environment. Treat tool discovery as step one, not proof of document access.
3) Valid scope returned, but values look wrong (query design layer)
• Symptoms: Elements are returned, but membership or parameters don’t match expectations.
• Checks: Prove membership with a short list of ElementIds; avoid relying on total counts unless your schedule/itemization and filters are identical to the query. Confirm the parameter is an instance field if you expect per‑element variation. Re‑run on a single known element to isolate the issue, then widen scope.
When you’re ready to go beyond verification toward production use on Windows with native Revit and AutoCAD integrations, explore what’s available today in ArchiLabs Desktop.
Learn about how Model Context Protocol (MCP) is changing the way we use tools like Autodesk Revit and the future of AI agents and architecture
Honest review of Revit 2027 AI: placement, docs, generative design, clashes, Forma links—what saves time, what’s half‑baked, and gaps.