# Revit MCP (remote · revit-mcp.itmartin24.workers.dev)

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

- Trust score: 68/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `revit-mcp.itmartin24.workers.dev`: 68/100 (this document), [markdown](https://verifymcp.io/servers/io-scanbimlabs-revit-mcp/revit-mcp.md), [page](https://verifymcp.io/servers/io-scanbimlabs-revit-mcp/revit-mcp)

## Channel facts

- Endpoint: `https://revit-mcp.itmartin24.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2629 tokens (~328/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http io-scanbimlabs-revit-mcp https://revit-mcp.itmartin24.workers.dev/mcp
```

### Codex

```toml
[mcp_servers.io-scanbimlabs-revit-mcp]
url = "https://revit-mcp.itmartin24.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-scanbimlabs-revit-mcp": {
      "type": "remote",
      "url": "https://revit-mcp.itmartin24.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-scanbimlabs-revit-mcp --url https://revit-mcp.itmartin24.workers.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-scanbimlabs-revit-mcp:
    url: "https://revit-mcp.itmartin24.workers.dev/mcp"
```

### Other

```json
{
  "mcpServers": {
    "io-scanbimlabs-revit-mcp": {
      "type": "http",
      "url": "https://revit-mcp.itmartin24.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 67, +4)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 63, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 61)

First indexed and scored.

## MCP tools (8)

### `revit_upload` (~450 tokens)

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.

Input parameters:

- `file_name` (string, required): Original file name including the Revit extension (.rvt, .rfa, .rte, .rft). Used as the OSS object key; non-alphanumeric characters are sanitized to underscores.
- `file_url` (string, required): Public HTTPS URL the worker can fetch the Revit file from. Must return 200 with the raw .rvt bytes (no auth gate, no HTML redirect). Max 100MB for direct upload.
- `project_name` (string): Optional human-readable project label echoed back in the response for bookkeeping. No effect on APS processing.

### `revit_get_elements` (~328 tokens)

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.

Input parameters:

- `category` (string, required): Revit category name to filter on (case-insensitive substring match). Use canonical Revit category names like Walls, Doors, Windows, Structural Columns, Ducts, Pipes, Mechanical Equipment.
- `model_id` (string, required): Base64url-encoded URN of the translated Revit model (returned from revit_upload as model_id/urn). Always begins with 'dXJu' (base64 of 'urn:').

### `revit_get_parameters` (~315 tokens)

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.

Input parameters:

- `category` (string, required): Revit category to filter on (case-insensitive substring match). Ignored when element_id is supplied.
- `element_id` (string): Optional APS Model Derivative objectid of a single element to inspect. When provided, overrides category filtering and returns parameters only for that element.
- `model_id` (string, required): Base64url-encoded URN of the translated Revit model (returned from revit_upload). Always begins with 'dXJu'.

### `revit_run_schedule` (~290 tokens)

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.

Input parameters:

- `model_id` (string, required): Base64url-encoded URN of the translated Revit model. Always begins with 'dXJu'.
- `schedule_name` (string, required): Category name or keyword used to select rows (case-insensitive substring match on Category/name). Common examples: Walls, Doors, Windows, Rooms, Furniture, Mechanical Equipment.

### `revit_clash_detect` (~343 tokens)

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.

Input parameters:

- `category_a` (string, required): First Revit category for the pairwise clash check (case-insensitive substring match). Typical MEP/structural examples: Mechanical Equipment, Ducts, Pipes, Cable Trays.
- `category_b` (string, required): Second Revit category to compare against category_a. Often a structural/architectural discipline when category_a is MEP.
- `model_id` (string, required): Base64url-encoded URN of the translated Revit model. Always begins with 'dXJu'.

### `revit_export_ifc` (~370 tokens)

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.

Input parameters:

- `include_properties` (boolean): Whether to include Revit property sets in the IFC output. true -> IFC2x3 Coordination View 2.0 (with psets); false -> minimal IFC2x3 geometry.
- `model_id` (string, required): Base64url-encoded URN of the translated Revit model to export to IFC. Always begins with 'dXJu'.

### `revit_get_sheets` (~258 tokens)

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.

Input parameters:

- `model_id` (string, required): Base64url-encoded URN of the translated Revit model whose sheets you want to list. Always begins with 'dXJu'.

### `revit_get_views` (~275 tokens)

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.

Input parameters:

- `model_id` (string, required): Base64url-encoded URN of the translated Revit model whose views you want to list. Always begins with 'dXJu'.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-scanbimlabs-revit-mcp/revit-mcp#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 68
- 2026-08-01: 67
- 2026-07-31: 67
- 2026-07-30: 63
- 2026-07-29: 63
- 2026-07-28: 62
- 2026-07-27: 62
- 2026-07-26: 61

## Links

- Remote endpoint: https://revit-mcp.itmartin24.workers.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-scanbimlabs-revit-mcp/revit-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-scanbimlabs-revit-mcp/revit-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/io-scanbimlabs-revit-mcp/revit-mcp