# revit [Health: Active]

**Category:** 📐 Architecture & Design  
**Repository:** https://github.com/ScanBIM-Labs/revit-mcp  
**GitHub Stars:** 0  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/revit

## Description
Revit model query + APS Design Automation runner.

## Tools
Capabilities this server exposes over MCP:

- **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: Do not call if you already have a translated URN (use the existing model_id instead), if the file is not a Revit source file, or if the URL requires authentication the worker cannot satisfy.
APS scopes: data:read data:write data:create bucket:read bucket:create viewables:read (OSS bucket create + object PUT + Model Derivative job).
Rate limits: APS default ~50 req/min per app per endpoint; Model Derivative translation jobs ~60 req/min; OSS uploads size-limited per file to 100MB for direct upload, larger via resumable.
Errors: 401 APS token expired — refresh credentials and retry. 403 scope insufficient — request data:write + bucket:create. 404 bucket/object not found — confirm bucket was created. 409 bucket exists — safe to ignore, reuse it. 429 rate limited — back off with exponential delay. 5xx APS upstream — retry with jitter up to 3x, then surface.
Side effects: Creates a new transient OSS bucket named scanbim-revit-<timestamp>, uploads the object, and starts a Model Derivative translation job. NOT idempotent — each call creates a fresh bucket and new URN.
- **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 must be success), and do not use for free-text searches across the whole model — filter by category here or use revit_run_schedule for tabular views.
APS scopes: data:read viewables:read (Model Derivative metadata + properties).
Rate limits: APS default ~50 req/min per app per endpoint; Model Derivative translation jobs ~60 req/min; OSS uploads size-limited per file to 100MB for direct upload, larger via resumable.
Errors: 401 APS token expired — refresh. 403 scope insufficient — add viewables:read. 404 URN not found — confirm model_id and that translation has run. 429 rate limited — back off. 5xx APS upstream — retry with jitter.
Side effects: Read-only. Idempotent.
- **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 when you just need the elements themselves (use revit_get_elements), or to modify values — this is read-only.
APS scopes: data:read viewables:read (Model Derivative metadata + properties).
Rate limits: APS default ~50 req/min per app per endpoint; Model Derivative translation jobs ~60 req/min; OSS uploads size-limited per file to 100MB for direct upload, larger via resumable.
Errors: 401 APS token expired — refresh. 403 scope insufficient — add viewables:read. 404 URN not found — verify model_id. 429 rate limited — back off. 5xx APS upstream — retry with jitter.
Side effects: Read-only. Idempotent.
- **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 metadata (use revit_get_elements) or parameter schema (use revit_get_parameters).
APS scopes: data:read viewables:read (Model Derivative metadata + properties).
Rate limits: APS default ~50 req/min per app per endpoint; Model Derivative translation jobs ~60 req/min; OSS uploads size-limited per file to 100MB for direct upload, larger via resumable.
Errors: 401 APS token expired — refresh. 403 scope insufficient — add viewables:read. 404 URN not found — check model_id. 429 rate limited — back off. 5xx APS upstream — retry with jitter.
Side effects: Read-only. Idempotent.
- **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: Do not use as a substitute for Navisworks Manage for contractual clash reports — this is a first-pass coordination sniff test, not a certified Clash Detective run.
APS scopes: data:read viewables:read (Model Derivative metadata + properties).
Rate limits: APS default ~50 req/min per app per endpoint; Model Derivative translation jobs ~60 req/min; OSS uploads size-limited per file to 100MB for direct upload, larger via resumable.
Errors: 401 APS token expired — refresh. 403 scope insufficient — add viewables:read. 404 URN not found — verify model_id. 429 rate limited — back off. 5xx APS upstream — retry with jitter.
Side effects: Read-only against APS. May read from D1 vdc_rules table if present. Idempotent.
- **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 happens automatically in revit_upload), and do not call repeatedly while a prior IFC job is still inprogress — poll the manifest instead.
APS scopes: data:read data:write viewables:read (Model Derivative job + manifest).
Rate limits: APS default ~50 req/min per app per endpoint; Model Derivative translation jobs ~60 req/min; OSS uploads size-limited per file to 100MB for direct upload, larger via resumable.
Errors: 401 APS token expired — refresh. 403 scope insufficient — add data:write. 404 URN not found — confirm model_id was translated. 409 not applicable. 429 rate limited — back off. 5xx APS upstream — retry with jitter up to 3x.
Side effects: Creates a Model Derivative job and, on completion, a new IFC derivative inside the model's manifest. Safe to re-run (APS deduplicates) but each call with x-ads-force may retranslate.
- **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 3D views (use revit_get_views) — this returns only 2D sheet entries.
APS scopes: data:read viewables:read (Model Derivative metadata + object tree).
Rate limits: APS default ~50 req/min per app per endpoint; Model Derivative translation jobs ~60 req/min; OSS uploads size-limited per file to 100MB for direct upload, larger via resumable.
Errors: 401 APS token expired — refresh. 403 scope insufficient — add viewables:read. 404 URN not found — check model_id. 429 rate limited — back off. 5xx APS upstream — retry with jitter.
Side effects: Read-only. Idempotent.
- **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 you only want drawing sheets (use revit_get_sheets) or element data inside a view (use revit_get_elements / revit_run_schedule).
APS scopes: data:read viewables:read (Model Derivative metadata + object tree).
Rate limits: APS default ~50 req/min per app per endpoint; Model Derivative translation jobs ~60 req/min; OSS uploads size-limited per file to 100MB for direct upload, larger via resumable.
Errors: 401 APS token expired — refresh. 403 scope insufficient — add viewables:read. 404 URN not found — check model_id. 429 rate limited — back off. 5xx APS upstream — retry with jitter.
Side effects: Read-only. Idempotent.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "revit": {
    "url": "https://revit-mcp.itmartin24.workers.dev/mcp"
  }
}
```

## Documentation

## What the revit MCP server does

The revit MCP server provides MCP access to Revit model data and selected model-processing workflows through Autodesk Platform Services. It is designed for agents that need to inspect uploaded models, retrieve structured information, and request common AEC data operations without manually navigating Revit.

The service covers model upload and translation, category-based element queries, parameter retrieval, schedule extraction, clash detection using VDC rules, IFC export, and inventory queries for sheets and views. It does not describe desktop application control or editing individual Revit objects directly.

## How it works

The revit MCP server is exposed as a remote MCP endpoint. The README’s quick-start configuration uses:

```json
{
  "mcpServers": {
    "revit": {
      "url": "https://revit-mcp.itmartin24.workers.dev/mcp"
    }
  }
}
```

Cloudflare Workers provide the runtime. APS OAuth2 with the client-credentials flow handles Autodesk service authentication. Cloudflare D1 records usage, while Cloudflare KV caches tokens.

The repository also documents a unified MCP endpoint at `https://mcp.scanbimlabs.io/unified/mcp` for direct JSON-RPC requests. That example calls a `list_models` tool, which is separate from the eight Revit tools listed for this service.

## Setup and configuration

Connect an MCP client to the documented Revit URL, then provide a ScanBIM user key when authentication is required. The key can be sent in either of two ways:

- `x-scanbim-api-key: <your_user_key>`
- `Authorization: Bearer sk_scanbim_<your_user_key>`

Use only one format. The first form sends the user key verbatim. The second sends the complete value, including the `sk_scanbim_` prefix. User keys are obtained from the ScanBIM billing settings page. The README’s shell example stores the first form in the `SCANBIM_USER_KEY` environment variable.

## Tools and capabilities

The available tools are:

- `revit_upload` uploads a Revit file to APS and starts translation.
- `revit_get_elements` retrieves elements by category.
- `revit_get_parameters` returns parameters for an element.
- `revit_run_schedule` extracts schedule data.
- `revit_clash_detect` runs clash detection with VDC rules.
- `revit_export_ifc` exports a model as IFC.
- `revit_get_sheets` lists model sheets.
- `revit_get_views` lists model views.

Together, these operations support model inspection, schedule-oriented extraction, coordination checks, and interchange through IFC.

## Limitations and notes

Authentication is enforced by the service. A missing or malformed header returns HTTP 401 with a JSON-RPC error code of `-32001`. Successful calls return HTTP 200 and debit credits. If the account lacks credits, the service returns HTTP 402 and includes checkout URLs for five credit packs plus a billing-page top-up URL.

Switching between the two authentication formats can create a separate free-plan account for the alternate key, so clients should keep one header format consistently.

_Full upstream README: https://allmcps.com/mcp/revit/readme_