A Revit add-in and TypeScript MCP server bridge model operations over a local connection. For Cursor, 1 route is explicitly documented by the integration maintainer.
A Revit add-in and TypeScript MCP server bridge model operations over a local connection.
Platforms: Windows
MCP transport compatibility is inferred; this agent is not explicitly documented for this connection.
Windows, a supported Revit 2020–2026 installation, Node.js 18+ and the companion C# add-in.
Requires a matching Revit add-in build. Revit model and transaction constraints still apply.
A Revit add-in and MCP server for working with an open building model.
Platforms: Windows
MCP support suggests compatibility; this client is not documented by the maintainer.
Windows, Revit 2025, 2026 or 2027 and Node.js 18 or newer.
The bridge connects to a Revit session on the same Windows computer.
A Revit add-in and MCP bridge for model queries and undoable edits.
Platforms: Windows
The integration documentation explicitly names this client.
Windows, Revit 2025, 2026 or 2027, Node.js 18 or newer and the Revit add-in.
The add-in operates inside Revit and executes edits as named transactions.
| Integration | Cursor compatibility | Requirements |
|---|---|---|
| MCP servers for Revit | MCP compatibility (inferred) Setup guide | Windows, a supported Revit 2020–2026 installation, Node.js 18+ and the companion C# add-in. |
| Revit MCP · rui-branco | MCP compatibility (inferred) | Windows, Revit 2025, 2026 or 2027 and Node.js 18 or newer. |
| Revit MCP · KenLP | Documented setup Setup guide | Windows, Revit 2025, 2026 or 2027, Node.js 18 or newer and the Revit add-in. |
The sources establish the capabilities listed above, not complete application coverage. Check each bridge’s limitations and your application version before starting.
Choose a route that explicitly documents Cursor and matches your environment. Start with the maintainer’s setup guide and a disposable project copy. Shared MCP support alone is listed as an inference.
All Autodesk Revit integrations