MCPpedia last refreshed this data
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"revit-mcp": {
"args": [
"run",
"--project",
"C:\\path\\to\\src\\RevitMcp.Server\\RevitMcp.Server.csproj"
],
"command": "dotnet"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Model Context Protocol (MCP) server that connects Autodesk Revit 2025+ to AI assistants like Claude. Query elements, create views, manage sheets, and modify parameters — all through natural language.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in design
3D & AR SDK for Android, iOS, Web — API docs, samples, validation, and code generation.
MeiGen-AI-Design-MCP — Turn Claude Code / OpenClaw into your local Lovart. Local ComfyUI, 1,400+ prompt library, multi-direction parallel generation.
Generate game sprites and assets from text prompts for game development.
AI image generation and editing with prompt optimization and quality presets. Powered by Nano Banana
MCP Security Weekly
Get CVE alerts and security updates for ArchSmarterRevitMcpServer and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server that connects Autodesk Revit 2025+ to AI assistants like Claude. Query elements, create views, manage sheets, and modify parameters — all through natural language.
The system has two halves that communicate over a named pipe:
Claude Desktop / VS Code
│
│ stdio (JSON-RPC)
▼
┌─────────────────┐ Named Pipe ┌──────────────────┐
│ RevitMcp.Server │ ◄──── "revit-mcp-bridge" ──► │ RevitMcp.Addin │
│ (Console App) │ length-prefixed JSON │ (Revit Add-in) │
└─────────────────┘ └──────────────────┘
│
Revit API calls
(main thread only)
RevitMcp.Server is a standalone console app that speaks MCP over stdio. Claude Desktop launches it automatically.
RevitMcp.Addin loads inside Revit, runs a named-pipe listener on a background thread, and marshals all Revit API calls to the main thread via ExternalEvent.
RevitMcp.Core contains the shared contracts, command names, and handler implementations used by both sides.
| Tool | Description |
|---|---|
get_elements | Retrieve elements, optionally filtered by category (default limit: 100) |
get_element_by_id | Get detailed info for a single element including bounding box and location |
get_element_parameters | List all parameters and values for an element |
get_selected_elements | Get currently selected elements in the active view |
set_parameter | Set a parameter value on an element |
delete_elements | Delete elements with preview mode (set confirm=true to execute) |
| Tool | Description |
|---|---|
open_view | Open a view by ID or name |
create_plan_view | Create a floor plan or ceiling plan for a level |
create_elevation_view | Create an elevation at a location and direction |
create_section_view | Create a section defined by origin, direction, and dimensions |
create_schedule_view | Create a schedule for a category with optional field selection |
| Tool | Description |
|---|---|
create_sheet | Create a new sheet with a title block |
add_view_to_sheet | Place a view on a sheet as a viewport |
| Tool | Description |
|---|---|
get_project_info | Get project metadata (name, number, client, address, etc.) |
analyze_model_statistics | Get element counts by category, family, type, and level |
get_current_view_info | Get active view details (type, scale, detail level, etc.) |
export_room_data | Extract rooms with area, volume, perimeter, and department data |
Build the entire solution:
dotnet build RevitMcpServer.sln -c "Debug R25"
Build the server only:
dotnet build src/RevitMcp.Server/RevitMcp.Server.csproj
Publish the server for deployment:
dotnet publish src/RevitMcp.Server -c Release -o ./publish
The add-in's post-build step automatically copies the DLL and .addin manifest to Revit's add-in folder.
Build the RevitMcp.Addin project with a Revit 2025 configuration (Debug R25 or Release R25). The post-build event copies the output to:
%APPDATA%\Autodesk\REVIT\Addins\2025\RevitMcp.Addin\
Add the server to your Claude Desktop config (claude_desktop_config.json):
{
"mcpServers": {
"revit-mcp": {
"command": "dotnet",
"args": ["run", "--project", "C:\\path\\to
... [View full README on GitHub](https://github.com/kilkellym/ArchSmarterRevitMcpServer#readme)