Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"Revit Connector": {
"args": [
"run",
"--with",
"mcp[cli]",
"mcp",
"run",
"/absolute/path/to/main.py"
],
"command": "uv"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
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.
Click any tool to inspect its schema.
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 / developer-tools
Manage Supabase projects — databases, auth, storage, and edge functions
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
MCP server for using the GitLab API
MCP Security Weekly
Get CVE alerts and security updates for Mcp Server For Revit Python and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
This repo is aimed at:
It contains:
The system runs as two separate servers working together in a chain:
Claude / LLM Client
|
| MCP Protocol (stdio or HTTP)
v
main.py (MCP Server)
|
| HTTP requests (localhost:48884)
v
pyRevit Routes (REST API running inside Revit)
|
| Revit API calls
v
Revit Application
main.py is the MCP server. It speaks the MCP protocol so that Claude (or any MCP-compatible client) can call tools. When a tool is called, main.py translates it into an HTTP request and forwards it to Revit.
pyRevit Routes is a lightweight REST API that runs inside the Revit process. It receives those HTTP requests, executes Revit API code (since it has direct access to the running instance), and returns JSON responses.
They never conflict because they serve different roles, speak different protocols, and listen on different ports.
Note: The Launch & Document tools (
launch_revit,list_revit_installations) are the exception — they run entirely on the MCP side, usingsubprocessto start Revit and then polling the pyRevit Routes health endpoint until the bridge is ready.
main.py):revit-mcp-python.extension/):startup.pyrevit_mcp/ directorytools/):tools/__init__.py| Tool Name | Status | Category | Description |
|---|---|---|---|
get_revit_status | ✅ Implemented | Status & Connectivity | Check if the Revit-MCP API is active and responding |
get_revit_model_info | ✅ Implemented | Model Information | Get comprehensive information about the current Revit model |
list_levels | ✅ Implemented | Model Information | Get all levels with elevation information |
get_revit_view | ✅ Implemented | View & Image | Export a specific Revit view as an image |
list_revit_views | ✅ Implemented | View & Image | Get a list of all exportable views organized by type |
place_family | ✅ Implemented | Family & Placement | Place a family instance at specified location with custom properties |
list_families | ✅ Implemented | Family & Placement | Get a flat list of available family types (with filtering) |
list_family_categories | ✅ Implemented | Family & Placement | Get a list of |