Open-source Revit MCP server: let Claude and other AI assistants read and edit BIM models, with human approval on every change.
Compatibility
AEC Model Bridge is a standard MCP server. It speaks the Model Context Protocol over stdio, so any AI client that can start a local MCP server can use it with the Revit model you have open.
This page separates two groups. The first is what this repository documents and sets up. The second is what should work because it is standard MCP. The maintainers have not tried anything marked "not tested".
AI assistants and MCP clients
| Client | Status | How to connect |
|---|---|---|
| Claude Desktop | Documented here | Install the .mcpb bundle from the latest release, or tick the Claude Desktop option in the installer. The README shows the claude_desktop_config.json entry. |
| VS Code with GitHub Copilot (agent mode) | Documented here | Use the VS Code extension, the committed .vscode/mcp.json, or the install link in install-buttons.md. |
| Cursor | Documented here | Use the Cursor install link in the README, or add the mcpServers entry from the README. |
| Codex | Documented here | The README states Codex uses the same values as the Claude Desktop entry. The panel chat can also call the codex command-line tool. |
| Hermes Desktop | Example provided | Start from docs/examples/hermes-desktop.json. |
| Windsurf, Cline, Roo Code, Continue | Same configuration shape, not tested | marketplaces.md lists these as accepting the mcpServers entry. |
| Claude Code, Zed, Gemini CLI, Goose, LM Studio, JetBrains AI Assistant | Standard MCP clients, not tested | They can start a stdio MCP server. Use the same command, arguments and environment variables as the README entry. Check each client's own MCP documentation for where the entry goes. |
Agent frameworks
Any framework with an MCP stdio client can launch the server and call its tools. Examples are the Claude Agent SDK, the OpenAI Agents SDK, and LangChain or LangGraph through an MCP adapter. None of these has been tested with this server.
What will not work directly
A client that accepts only a remote MCP server over HTTP cannot start a local stdio server. Many browser-based chat apps work this way. A local proxy can expose a stdio server over HTTP. That opens your model to anything that can reach the proxy, so read Security first. The server is designed for a single machine, with the Revit add-in on loopback.
Live work always needs the Revit add-in. The server talks to a running copy of Revit on Windows.
Applications and formats
| Tool | Status | Notes |
|---|---|---|
| Revit 2024 to 2027 | Available | Native C# add-in. |
| IFC | Available | Reads IFC files without Revit running. |
| Rhino and Grasshopper | Available | Connects to the Rhino add-in on localhost:3004. |
| Speckle | Available | Needs a Speckle client ID in your environment. |
| Navisworks Manage | In progress | The provider and tools are registered. The add-in is not finished. |
| Power BI | In progress | The tool exists but is not registered in the hub. |
| Excel and SQLite | Available as export | The report tools write .xlsx and .db files. |
Where the server is listed
Registry files for the official MCP Registry (server.json), Smithery (smithery.yaml, mock mode) and Glama (glama.json) are in the repository root. See marketplaces.md for the current status of each listing.
Try it without Revit
Set MCP_REVIT_MODE to mock. Any client above can then browse the tools and get sample answers. Live mode does not use mock data.