Cutom_Revit_MCP_server

This MCP server enables Claude Desktop to drive Autodesk Revit 2023 through natural language. It exposes 61 tools organized into categories such as Query Tools, Element Tools, Parameter Tools, View Tools, Sheet Tools, Selection Tools, Visibility Tools, Level/Grid Tools, MEP Tools, Annotation Tools, and Project Tools. Claude sends tool calls via the MCP protocol over HTTP to the local Revit plugin, which then executes Revit API operations and returns results. Typical workflows include listing elements (e.g., walls), creating sheets or rooms, updating parameters, or querying project information. To use it, ensure the MCP server is running (the Node server starts on port 8080) and that Claude Desktop is configured with the server’s path and environment pointing to localhost:8080. You can test individual tools by posting to the /execute endpoint with a tool name and parameters, and you can verify health with a /health check. The server translates high-level natural language intents into concrete Revit operations via the 61 registered tools, enabling tasks like counting doors by level, creating sheets with specified views, querying elements by category, and manipulating elements or views as requested by Claude.

Prerequisites:

• Autodesk Revit 2023 installed (default path C:\Program Files\Autodesk\Revit 2023)
• Node.js v18+ installed
• .NET Framework 4.8 Developer Pack installed
• Claude Desktop installed

Step-by-step:

1. Build the Revit plugin (C#):

   • Open a terminal and navigate to the RevitPlugin folder: cd RevitPlugin
   • Restore and build: dotnet restore dotnet build -c Release
   • Built artifacts will appear in RevitPlugin\bin\Release\ (RevitMcpPlugin.dll and Newtonsoft.Json.dll)

2. Deploy the Revit plugin:

   • Copy files to the Revit add-ins folder: set ADDIN_DIR=%APPDATA%\Autodesk\Revit\Addins\2023 copy RevitPlugin\RevitMcpPlugin.addin "%ADDIN_DIR%" copy RevitPlugin\bin\Release\RevitMcpPlugin.dll "%ADDIN_DIR%" copy RevitPlugin\bin\Release\Newtonsoft.Json.dll "%ADDIN_DIR%"

3. Install MCP Server dependencies (Node.js):

   • cd mcp-server
   • npm install

4. Build the MCP Server (TypeScript):

   • cd mcp-server
   • npx tsc
   • This outputs to mcp-server/dist/

5. Configure Claude Desktop to connect to the MCP server:

   • Edit Claude config at %APPDATA%\Claude\claude_desktop_config.json
   • Add a revit entry under mcpServers, for example: { "mcpServers": { "revit": { "command": "node", "args": [ "C:\FULL\PATH\TO\github_revit_MCP_server\mcp-server\dist\index.js" ], "env": { "REVIT_HOST": "localhost", "REVIT_PORT": "8080" } } } }
   • Replace C:\FULL\PATH\TO with the actual absolute path to your project folder, using double backslashes for JSON strings.

6. Launch and test:

   • Start Revit 2023 and open a project; the plugin will start the HTTP server on port 8080.
   • Restart Claude Desktop to recognize the new MCP server.
   • In Claude, start a conversation and try examples like:
     • "List all walls in the model"
     • "Get project information"
     • "Count all doors grouped by type"
     • "Create a new sheet A-501 called Building Elevations"

Tips and common issues:

• If Revit is installed in a non-default path, update the Revit API references in RevitMcpPlugin.csproj accordingly.
• Ensure port 8080 is free and not blocked by firewalls when testing health and execute endpoints.
• Use the /health endpoint to confirm the server is running and connected to Revit.
• The MCP server relies on the ExternalEvent pattern for thread-safe Revit API access; long-running tasks should be designed to return promptly to avoid UI lag.
• When configuring Claude, keep the absolute path to index.js correct and escape backslashes in JSON.
• If you modify tools, rebuild the MCP server with tsc to propagate changes.
• Environment variables can be extended for authentication, host, or plugin behavior if needed.