Claude for architects: Revit schedules, scripts and MCP

Pick the access route that matches the job

For an architect or BIM coordinator, a useful Claude task might be identifying rooms missing an approved finish code, comparing door information or drafting an element-reporting routine. Start with the decision the result must support. A finish-code audit needs parameter values and a reliable room key; it does not necessarily need the entire model.

A normal chat can analyze supplied exports. A generated script can operate inside a supported Revit environment after review. A configured model connection can expose live operations. Keep these routes explicit so a successful table comparison is not mistaken for a model-wide check.

Route one: review an exported schedule

Export a dedicated review schedule with individual instances visible. Record the model revision, Revit release, phase, design option, levels and treatment of linked models. Autodesk’s export procedure produces delimited schedule data. Inspect the headers, delimiter and resulting row count before uploading it.

For a room finish audit, include building, level, phase, room number, name and finish-code fields. Supply element identifiers through an appropriate export if available; otherwise explain how the reviewer will locate each result. A room number is not automatically a unique key across the project.

Give Claude the approved finish-code table and its revision. Keep the check literal first: missing values, duplicate keys and codes outside the supplied list. A suggested similar spelling belongs in a separate proposal column. It should not silently replace the original value.

Audit rooms_revE.csv against finish_codes_04.csv. Scope: Building B, Levels 01–03, proposed phase, primary option, host model only. Return missing codes, unknown codes and duplicate room keys. Include the original row number, room key, element identifier when supplied, existing value and failed rule. Do not infer finishes from room names. Preserve blanks and report ambiguous keys. No model changes are authorized.

Verify at least one passing room and several reported exceptions in Revit. Compare totals with the original schedule. If a grouped export combined instances, correct the export rather than treating the group row as a room.

For a companion PDF, Anthropic documents visual PDF analysis under supported conditions. Check that the chosen view is readable; a plan cannot reveal parameters omitted from the export.

Route two: develop a small Revit routine

If the same audit will recur, ask Claude to draft a read-only script for your approved Revit automation environment. Supply exact API and runtime versions, parameter identifiers and expected output columns. Parameter display names may be ambiguous; distinguish shared-parameter GUIDs and instance/type ownership where applicable.

The first deliverable should list selected elements and reasons for exclusions. Test reviewed code on a disposable model copy. Confirm the selected population before adding writes. A script that finds the wrong rooms efficiently is still wrong.

For a later finish-code update, use an approved mapping with an unambiguous composite key. Require a dry-run table of old and proposed values, reject duplicate keys and record read-only parameters or unavailable elements. Review the transaction behavior and save the result separately. Reopen the file and read the changed values back; also inspect a few elements outside the selection to ensure they remained unchanged.

Route three: configure the documented Revit MCP connection

There is a real vendor-documented route for Claude Desktop. Autodesk’s Revit Public MCP setup currently specifies Revit 2027.2, a separate Technical Preview add-on and manual client configuration. Its setup distinguishes read, write and experimental configurations. This is not the same as uploading an RVT file to a web chat.

Follow the vendor’s current setup instructions for your release, then test the connection on a model copy. Start with a read-only request: identify the model and list a few known elements. Confirm available tools before requesting an action; the existence of an MCP connection does not imply every Revit command is supported.

Use the connected Revit tools only to read. Identify the current model, then list rooms on Level 02 in the proposed phase, including identifiers and finish-code values. State how linked models and design options were handled. Report unavailable fields. Do not modify parameters, create views or save the model.

Compare the returned identifiers and values with a Revit schedule. Then decide whether this connection improves your actual task. Anthropic’s connector documentation explains the wider integration mechanism; the installed Revit server defines the model-specific operations and permissions.

Keep geometry, rules and sources separate

A parameter audit checks supplied data against a supplied rule. It does not by itself verify fire strategy, accessibility or structural design. For a requirement-based check, name the applicable document, edition, clause and project conditions. Preserve the source excerpt and identify which model properties or measurements support the comparison.

State units explicitly. A displayed schedule value may be rounded, while an API value may use a different internal unit system. Require documented conversion and an agreed tolerance before comparing them. Never resolve a mismatch by assuming the table or the model must be correct.

Check an exported Revit plan in ARAI

Export the relevant Revit plan to DWG and a matching PDF. Record the view, revision, export units and coordinate basis; open the DWG in CAD and check a known dimension. Specify the floor or layers to inspect and the input units. Ask ARAI for a read-only inventory of drawing objects, layers and external references, with object identifiers for checking in CAD.

Inspect drawing objects in ARAI. Attach your files to the draft before sending. Check the inventory against a known CAD selection. This workflow uses drawing exports; native RVT editing is not included. See the DWG preparation guide.