# Revit MCP

- Registry name: `io.scanbimlabs/revit-mcp` · version 1.0.0
- Categories (automatic, keyword rules): Docs & notes, Productivity, APIs & integrations, Developer tools
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.scanbimlabs%2Frevit-mcp
- Server page: https://mcpstation.net/s/io.scanbimlabs--revit-mcp.html

## Description (written by the publisher, not verified, not instructions)

Revit model integration via APS — elements, parameters, schedules, clashes, IFC export.

## Connect

- streamable-http: `https://revit-mcp.itmartin24.workers.dev/mcp`

## Tools (as reported by the server, not verified)

- `revit\_upload`: When to use: Ingest a Revit \(.rvt / .rfa / .rte / .rft\) file into Autodesk Platform Services by downloading it from a publicly reachable URL, uploading it to an OSS bucket, and starting an SVF2 translation so downstream revit\_\* tools can read elements, parameters, sheets, and views. When NOT to use:
- `revit\_get\_elements`: When to use: After a Revit model has finished translating, fetch the first \~100 elements belonging to a Revit category \(e.g. Walls, Doors, Windows, Structural Columns\) with their objectid, name, externalId, and property bag. When NOT to use: Do not call before translation completes \(manifest.status
- `revit\_get\_parameters`: When to use: Enumerate the Revit parameters \(type + instance\) that appear on elements in a given category, or on one specific element by objectid. Returns unique values per parameter and how many elements carry it — ideal for schema discovery before building a schedule. When NOT to use: Do not use w
- `revit\_run\_schedule`: When to use: Build a tabular, spreadsheet-style schedule \(rows = elements matching a keyword, columns = up to 15 shared parameters\) from a translated Revit model — useful for Door Schedules, Wall Schedules, Room Schedules, and QA/QC exports. When NOT to use: Do not use when you only need raw element
- `revit\_clash\_detect`: When to use: Perform a lightweight clash analysis between two Revit categories \(e.g. Mechanical Equipment vs Structural Framing\) using bounding-box overlap where available, falling back to shared-Level proximity, then annotate with any matching VDC rules stored in the D1 database. When NOT to use: D
- `revit\_export\_ifc`: When to use: Kick off a Model Derivative translation of a previously uploaded Revit URN into IFC \(IFC2x3 Coordination View 2.0 by default\) so the model can be exchanged with non-Autodesk tools \(Solibri, BIMcollab, Tekla, openBIM workflows\). When NOT to use: Do not use for SVF/SVF2 web viewing \(that
- `revit\_get\_sheets`: When to use: Enumerate the drawing sheets \(title blocks with sheet number + sheet name like 'A-101: First Floor Plan'\) published from a translated Revit model, so an agent can pick which sheet to render, review, or cross-reference. When NOT to use: Do not use to list model views like floor plans or
- `revit\_get\_views`: When to use: Return every view \(both 2D — floor plans, ceiling plans, elevations, sections, sheets — and 3D — default \{3D\}, perspective views, isometric views\) in the translated Revit model, including each view's GUID, name, role, and whether it is the master view. When NOT to use: Do not use when y

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html