Skip to content

Revit MCP server

io.scanbimlabs/revit-mcpscanbimlabs.iostreamable-httpv1.0.0Scanned

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

8 tools: 4 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 4 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 8 findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Revit MCP server can do

The Revit MCP server is published by scanbimlabs.io, a domain the MCP Registry verified. It has 8 tools. It can create or change data (4 tools: revit_upload, revit_run_schedule, revit_clash_detect and revit_export_ifc), but cannot delete data. 4 tools only read.

1 tool brings in text other people can write (revit_get_sheets).

The fixed checks matched 8 findings (credentials-mention and base64-blob). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Changes things 4Claude Code: ask
  • revit_clash_detectWhen to use: Perform a lightweight clash analysis between two Revit categories (e.g.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Warn

      The input schema at properties.model_id.examples[0] contains a 88-character base64 string. It decodes to text: "urn:adsk.objects:os.object:scanbim-revit-1731234567/MyBuilding.rvt".

      Matched text

      inputSchema.properties.model_id.examples[0]: "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c2NhbmJpbS1yZXZpdC0xNzMxMjM0NTY3..."

      What this check looks for
    Description, as the server wrote it
    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_ifcWhen 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-Au…1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Warn

      The input schema at properties.model_id.examples[0] contains a 88-character base64 string. It decodes to text: "urn:adsk.objects:os.object:scanbim-revit-1731234567/MyBuilding.rvt".

      Matched text

      inputSchema.properties.model_id.examples[0]: "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c2NhbmJpbS1yZXZpdC0xNzMxMjM0NTY3..."

      What this check looks for
    Description, as the server wrote it
    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_run_scheduleWhen 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 …1 finding

    Why it is in this group

    • The name "revit_run_schedule" says "run": a word for a change.

    Findings

    • Warn

      The input schema at properties.model_id.examples[0] contains a 88-character base64 string. It decodes to text: "urn:adsk.objects:os.object:scanbim-revit-1731234567/MyBuilding.rvt".

      Matched text

      inputSchema.properties.model_id.examples[0]: "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c2NhbmJpbS1yZXZpdC0xNzMxMjM0NTY3..."

      What this check looks for
    Description, as the server wrote it
    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_uploadWhen 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 sta…1 finding

    Why it is in this group

    • The name "revit_upload" says "upload": a word for a change.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...Errors: 401 APS token expired — refresh credentials and retry. 403 scope insufficient — req..."

      What this check looks for
    Description, as the server wrote it
    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.
Only reads 4Show 4 read-only tools
  • revit_get_elementsWhen to use: After a Revit model has finished translating, fetch the first ~100 elements belonging to a Revit category (e.g.1 finding

    Why it is in this group

    • The name "revit_get_elements" says "get": a word for reading.

    Findings

    • Warn

      The input schema at properties.model_id.examples[0] contains a 88-character base64 string. It decodes to text: "urn:adsk.objects:os.object:scanbim-revit-1731234567/MyBuilding.rvt".

      Matched text

      inputSchema.properties.model_id.examples[0]: "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c2NhbmJpbS1yZXZpdC0xNzMxMjM0NTY3..."

      What this check looks for
    Description, as the server wrote it
    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_parametersWhen to use: Enumerate the Revit parameters (type + instance) that appear on elements in a given category, or on one specific element by objectid.1 finding

    Why it is in this group

    • The name "revit_get_parameters" says "get": a word for reading.

    Findings

    • Warn

      The input schema at properties.model_id.examples[0] contains a 88-character base64 string. It decodes to text: "urn:adsk.objects:os.object:scanbim-revit-1731234567/MyBuilding.rvt".

      Matched text

      inputSchema.properties.model_id.examples[0]: "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c2NhbmJpbS1yZXZpdC0xNzMxMjM0NTY3..."

      What this check looks for
    Description, as the server wrote it
    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_get_sheetsWhen 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…Reads text others write1 finding

    Why it is in this group

    • The name "revit_get_sheets" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.

    Findings

    • Warn

      The input schema at properties.model_id.examples[0] contains a 88-character base64 string. It decodes to text: "urn:adsk.objects:os.object:scanbim-revit-1731234567/MyBuilding.rvt".

      Matched text

      inputSchema.properties.model_id.examples[0]: "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c2NhbmJpbS1yZXZpdC0xNzMxMjM0NTY3..."

      What this check looks for
    Description, as the server wrote it
    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_viewsWhen 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 Re…1 finding

    Why it is in this group

    • The name "revit_get_views" says "get": a word for reading.

    Findings

    • Warn

      The input schema at properties.model_id.examples[0] contains a 88-character base64 string. It decodes to text: "urn:adsk.objects:os.object:scanbim-revit-1731234567/MyBuilding.rvt".

      Matched text

      inputSchema.properties.model_id.examples[0]: "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c2NhbmJpbS1yZXZpdC0xNzMxMjM0NTY3..."

      What this check looks for
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:23 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2024-11-05
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://revit-mcp.itmartin24.workers.dev/mcp: tools/list returned 8 tools to an anonymous client, including revit_upload (write), revit_run_schedule (write), revit_clash_detect (write), revit_export_ifc (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

7 warn1 info
  • The input schema at properties.model_id.examples[0] contains a 88-character base64 string. It decodes to text: "urn:adsk.objects:os.object:scanbim-revit-1731234567/MyBuilding.rvt".

    Matched text

    inputSchema.properties.model_id.examples[0]: "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c2NhbmJpbS1yZXZpdC0xNzMxMjM0NTY3..."

    What this check looks for
  • The input schema at properties.model_id.examples[0] contains a 88-character base64 string. It decodes to text: "urn:adsk.objects:os.object:scanbim-revit-1731234567/MyBuilding.rvt".

    Matched text

    inputSchema.properties.model_id.examples[0]: "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c2NhbmJpbS1yZXZpdC0xNzMxMjM0NTY3..."

    What this check looks for
  • The input schema at properties.model_id.examples[0] contains a 88-character base64 string. It decodes to text: "urn:adsk.objects:os.object:scanbim-revit-1731234567/MyBuilding.rvt".

    Matched text

    inputSchema.properties.model_id.examples[0]: "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c2NhbmJpbS1yZXZpdC0xNzMxMjM0NTY3..."

    What this check looks for
  • The input schema at properties.model_id.examples[0] contains a 88-character base64 string. It decodes to text: "urn:adsk.objects:os.object:scanbim-revit-1731234567/MyBuilding.rvt".

    Matched text

    inputSchema.properties.model_id.examples[0]: "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c2NhbmJpbS1yZXZpdC0xNzMxMjM0NTY3..."

    What this check looks for
  • The input schema at properties.model_id.examples[0] contains a 88-character base64 string. It decodes to text: "urn:adsk.objects:os.object:scanbim-revit-1731234567/MyBuilding.rvt".

    Matched text

    inputSchema.properties.model_id.examples[0]: "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c2NhbmJpbS1yZXZpdC0xNzMxMjM0NTY3..."

    What this check looks for
  • The input schema at properties.model_id.examples[0] contains a 88-character base64 string. It decodes to text: "urn:adsk.objects:os.object:scanbim-revit-1731234567/MyBuilding.rvt".

    Matched text

    inputSchema.properties.model_id.examples[0]: "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c2NhbmJpbS1yZXZpdC0xNzMxMjM0NTY3..."

    What this check looks for
Show 2 more findings
  • The input schema at properties.model_id.examples[0] contains a 88-character base64 string. It decodes to text: "urn:adsk.objects:os.object:scanbim-revit-1731234567/MyBuilding.rvt".

    Matched text

    inputSchema.properties.model_id.examples[0]: "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6c2NhbmJpbS1yZXZpdC0xNzMxMjM0NTY3..."

    What this check looks for
  • The description mentions "credentials".

    Matched text

    description: "...Errors: 401 APS token expired — refresh credentials and retry. 403 scope insufficient — req..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http revit https://revit-mcp.itmartin24.workers.dev/mcp
claude mcp add --transport http revit https://revit-mcp.itmartin24.workers.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__revit__revit_get_elements",
      "mcp__revit__revit_get_parameters",
      "mcp__revit__revit_get_sheets",
      "mcp__revit__revit_get_views"
    ],
    "ask": [
      "mcp__revit__revit_upload",
      "mcp__revit__revit_run_schedule",
      "mcp__revit__revit_clash_detect",
      "mcp__revit__revit_export_ifc"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as revit. Review it before you use it.

Capability tags behind 1 rule
  • mcp__revit__revit_get_sheets untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.scanbimlabs/revit-mcp/verify?hash=51dfbcfc587e28e4d296307aa2d3f4a817b373693ad984ca15359eda6abc4146" | jq -e '.changed == false'

Pinned hash 51dfbcfc587e, from Nov 21, 2026, 06:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.scanbimlabs/revit-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.scanbimlabs/revit-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.scanbimlabs/revit-mcp.svg)](https://radar.anlyon.com/servers/io.scanbimlabs/revit-mcp)

Source: MCP Registry. Synced Oct 21, 2026, 18:52 UTC.

Revit MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Revit MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 4 of which can change, send or delete something, and 8 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Revit MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Revit MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Revit MCP server have?

8 tools: 4 write, 4 read. revit_upload, revit_run_schedule, revit_clash_detect, revit_export_ifc, revit_get_elements, revit_get_parameters, revit_get_sheets and revit_get_views.

Does the Revit MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Revit MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Revit MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.