Ai MCP Server

+50 tools to inspect, select, edit and document elements in live Revit models. Exposed over MCP by the ai mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

The AI Connector for Revit connects AI Desktop Apps (like Claude, Cursor or Copilot) with Revit. Rather than generating new Revit code, the AI uses a set of +50 predefined tools to inspect, select, edit and document elements in Revit models.

• Predefined Tools —
• Inspect and edit parameters, family sizes, sheets and views, names and more
• Get the value of a parameter
• Determine the file size of a family
• List views placed on a sheet
• Feedback-Driven Interaction —

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration

• Autodesk Revit from 2022 to 2027 - NonicaTab Revit plugin. - Claude Desktop App or Cursor for automatic setup Also compatible with Copilot in VSCode and any other MCP compatible desktop app. ---

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the ai mcp server does with a few real requests.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by NonicaTeam; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.