PyNet Bridge
PyNet Bridge lets AI clients discover and control running desktop BIM hosts via PyNet: execute validated Python scripts, manage ribbon UI/buttons, monitor/configure output, and drive a local BIM viewer.
Discover active host processes and verify the PyNet IPC/plugin listener.
Execute inline scripts or script files in a target host PID with timeout control, subject to the README's static import/call/assembly whitelist.
Check and toggle the PyNet output/log window.
Read the PyNet ribbon UI layout, create/delete custom tabs/modules, and list/deploy/update/delete script buttons.
Query BIM Viewer status; list clashes; load .pnt packages; get state, models, selected pnt_id, and element properties/psets with pagination/search/filtering.
Control the viewer: highlight clashes red/green, select/isolate elements, isolate models, fit camera, and clear highlights/ghosting.
Enables interaction with Autodesk Tools (Navisworks and Revit) through the PyNet Platform, allowing for dynamic UI deployment (custom Ribbon tabs and buttons), Python script execution, BIM process automation, and real-time detection of active Autodesk instances.
PyNet Bridge is the execution layer that allows AI models to control desktop BIM tools in real-time.
It connects Natural Language â Python â desktop BIM tools (Navisworks, Revit, AutoCAD, Rhino, Tekla Structures, RIB Presto, AVEVA UE), enabling AI to generate, execute, and refine BIM workflows autonomously.
Available integrations include Navisworks Manage, Revit, Civil 3D, Rhino, Tekla Structures (2023â2026), RIB Presto (budgets, COM API) and AVEVA UE (E3D Design .NET API).
This bridge acts as the connective tissue between AI logic and the desktop APIs of those hosts, allowing for dynamic UI creation, script execution, and BIM process automation using natural language.
đŦ Demos & Tutorials
See PyNet Bridge in action â these recordings show the full natural-language â BIM-action workflow inside live Autodesk models.
Demo | Description | Video |
â Autonomous BIM Coordination (Revit + Navisworks) | Claude Code drives Revit and Navisworks simultaneously to audit models, resolve clashes by tolerance rules, generate geometry, and self-correct API errors in real time. | |
PyNET + Codex Integration | How to configure PyNet Bridge with Codex and query into Navisworks. |
â Featured: Autonomous BIM Coordination
In this technical demo, Claude Code connects to Navisworks and Revit at the same time to run a full coordination workflow end-to-end:
Engineering criteria as a Skill â the AI applies tolerance rules to decide which interferences to auto-approve.
Real-time data auditing â validates model integrity and detects missing parameters (
PYNET_Classification) before coordinating.Autonomous geometry generation â generates architectural sleeves (pasatubos) directly in Revit, with precise spatial rotation to match pipe angles.
Self-healing code â hits a live Revit API data-type exception, analyzes the failure, rewrites the script on the fly, and completes the task.
Related MCP server: A2A MCP Server
đ How it works
The user describes a task in natural language.
The AI generates a Python script.
PyNet Bridge validates and sends the script.
The PyNet plugin executes it inside Autodesk.
Results are returned back to the AI.
This is what turns AI from a chatbot into an execution engine for BIM.
đ What makes PyNet Bridge powerful
AI â Action: Turns AI-generated code into real actions inside Navisworks/Revit
Real-time Execution: Run scripts instantly without leaving the BIM environment
Dynamic UI Creation: Let AI create tools, buttons and workflows on the fly
Reliable Communication: Fast and stable, entirely local
Model-Aware Automation: Operates directly on live BIM models
đ ī¸ Installation
â Option A â Automatic installer (recommended)
Open PowerShell and run:
irm https://raw.githubusercontent.com/RAEN-DT/PyNetBridge/main/install.ps1 | iexThis will automatically:
Check Python 3.10+ is installed
Install
uvif missing, thenpynet-mcp-bridgefrom PyPI withuv(neverpip)Auto-detect and configure all installed AI clients:
Claude Desktop (standard and Microsoft Store versions)
Claude Code (VS Code extension / CLI)
Cline (VS Code extension)
Roo Code (VS Code extension)
Codex CLI (
~/.codex/config.toml)
The pynet-mcp-bridge package includes:
Package | Purpose |
pynet-mcp-bridge | MCP server that connects AI models with desktop BIM tools via PyNET |
mcp[cli] (1.x) | Model Context Protocol SDK and CLI tools |
psutil | System process detection (finds running Autodesk instances) |
Restart your AI client(s) after installation to apply changes.
đĻ Python Libraries Starter Pack (optional)
Install the recommended Python libraries for PyNET scripting:
irm https://raw.githubusercontent.com/RAEN-DT/PyNetBridge/main/install-libraries.ps1 | iexThis installs:
Library | Purpose |
pandas | Data analysis and manipulation |
plotly | Interactive charts and visualizations |
matplotlib | Static plots and graphs |
dash | Web dashboards from Python |
These are the third-party libraries listed under Allowed Python Imports. Standard library modules (
json,sys,re, etc.) are already included with Python.
Prerequisites
PyNet Platform plugin installed in Navisworks/Revit.
Python 3.10 or higher â python.org â Python 3.14 is supported.
uv â docs.astral.sh/uv â required. The Claude Desktop extension (
.mcpb) launches the server withuvx pynet-mcp-bridge, souvmust be installed and on yourPATH. Install it withwinget install astral-sh.uv. Withoutuv, the extension will fail to start.Git â git-scm.com â required for VS Code extensions (Claude Code, Cline, Roo Code) to function correctly.
For Cline / Roo Code: VS Code â code.visualstudio.com
đ§ Option B â Manual installation
1. Install the package:
uv tool install pynet-mcp-bridgeUse uv only â do not install with pip. A pip copy lands in a different interpreter from the
pynet-bridge launcher, so upgrades and fixes silently miss the environment that actually runs.
2. Configure Claude Desktop:
Add the following to your claude_desktop_config.json:
Standard:
%APPDATA%\Claude\claude_desktop_config.jsonMicrosoft Store:
%LOCALAPPDATA%\Packages\Claude_*\LocalCache\Roaming\Claude\claude_desktop_config.json
{
"mcpServers": {
"pynet-bridge": {
"command": "pynet-bridge",
"args": []
}
}
}3. Configure Claude Code (VS Code extension):
Add to %USERPROFILE%\.claude.json:
{
"mcpServers": {
"pynet-bridge": {
"type": "stdio",
"command": "pynet-bridge",
"args": []
}
}
}4. Configure Cline:
Add to %APPDATA%\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json:
{
"mcpServers": {
"pynet-bridge": {
"type": "stdio",
"command": "pynet-bridge",
"args": []
}
}
}5. Configure Roo Code:
Add to %APPDATA%\Code\User\globalStorage\rooveterinaryinc.roo-cline\settings\mcp_settings.json:
{
"mcpServers": {
"pynet-bridge": {
"type": "stdio",
"command": "pynet-bridge",
"args": []
}
}
}6. Configure Codex CLI:
Add to %USERPROFILE%\.codex\config.toml:
[mcp_servers.pynet-bridge]
command = "C:/Users/<user>/.local/bin/pynet-bridge.exe"
args = []đ ī¸ Available MCP Tools
These tools allow AI to fully control the PyNet environment, from UI creation to script execution and system monitoring. Once connected, the AI will have access to the full suite of PyNet tools:
đ§ Core capabilities exposed to AI
đ System & Connection
list_active_instances: Scans the system for running Autodesk processes with an active PyNet connection.
check_plugin_status: Handshake ping to verify the plugin listener is responsive.
đī¸ Module (Tab) Management
get_pynet_ui_layout: Fetches the full UI structure (ButtonsModules and ScriptButtons).
create_pynet_module: Creates a new custom Tab (ButtonsModule) in the Ribbon.
delete_pynet_module: Permanently deletes a module and all its contents.
đ Button Management
get_buttons_data: Lists all script buttons for a specific module ID.
deploy_script_button: Installs a new ScriptButton into a specific module (Name, Script, Icon, Tooltip).
update_script_button: Updates metadata for an existing ScriptButton or moves it to another module.
delete_script_button: Permanently removes a ScriptButton from a module by Id.
đģ Execution & Console Control
send_command: Direct script execution in the PyNet engine (Target PID, Script Name, Content).
get_output_window_status: Checks if the output window is currently available/visible.
configure_output_window: Toggles the visibility of the PyNet log/output window.
đ§ BIM Viewer Control (VS Code)
Drives the PyNet BIM Viewer open in VS Code. Reads clash data from the loaded .pnt package and controls the 3D view over a local (127.0.0.1) connection â nothing leaves your machine.
viewer_status: Reports whether a PyNet BIM Viewer is open (port, package, data dir).
viewer_list_clashes: Reads the loaded package's
clashes.jsonand returns each clash with itspnt_ididentifiers.viewer_load_package: Loads a
.pntinto the open viewer, pushes the models, and returns a summary.viewer_highlight_clash: Highlights a clash pair by
pnt_id(element A red, element B green).viewer_fit: Fits the camera to all models in the viewer.
viewer_clear: Clears highlights and ghosting in the viewer.
đĄ Usage Examples
These are realistic prompts you can give your AI client once PyNet Bridge is connected.
Example 1 â Discover a running model and query it (read-only)
Prompt: "Connect to my open Navisworks model and tell me how many items are in the current selection."
The AI calls list_active_instances to find the running Navisworks process (e.g. Navisworks (PID 12345)), then calls send_command with a short Python script that reads the active document's selection. Expected output: a message like Current selection contains 42 items.
Example 2 â Run a clash-detection summary
Prompt: "Give me a summary of clash test results in the open model and export the counts as a table."
The AI calls list_active_instances, then send_command with a script that iterates the DocumentClash results using the whitelisted Autodesk.Navisworks.Clash assembly and returns counts per test. Expected output: a table such as Test 'Structure vs MEP': 17 active, 3 resolved.
Example 3 â Build a custom ribbon tool on the fly
Prompt: "Create a new ribbon tab called 'QA' and add a button that runs my hide-empty-layers script."
The AI calls create_pynet_module (returns a new module ID), then deploy_script_button with the button name, script path, icon and tooltip. Expected output: Button 'Hide Empty Layers' deployed to module QA. â visible immediately in the Autodesk ribbon.
âšī¸ Every script sent via
send_command/send_command_by_pathis first validated by the built-in static analyzer (see Safe AI Execution). Scripts that violate the import/call whitelist are rejected before reaching Autodesk.
đĄī¸ Safe AI Execution
PyNet Bridge includes a built-in validation layer that ensures all AI-generated scripts are safe and controlled before execution.
â Prevents unsafe operations
â Blocks unauthorized system access
â Guarantees controlled interaction with BIM models
AI remains powerful, but within safe boundaries
Starting from v1.1.1, the MCP server includes a built-in static analyzer that validates every script before it reaches the host application. All scripts are parsed and inspected at the bridge level â rejected scripts never leave the MCP server.
Allowed CLR Assemblies
Only these .NET references are permitted via clr.AddReference:
Common:
System,System.Windows.Forms,System.Drawing,System.Collections.GenericNavisworks:
Autodesk.Navisworks.Api,.ComApi,.Interop.ComApi,.ClashRevit:
RevitAPI,RevitAPIUIAutoCAD / Civil 3D / Map 3D:
AcMgd,AcCoreMgd,AcDbMgd,AecBaseMgd,AecPropDataMgd,AeccDbMgd,ManagedMapApiRhino:
RhinoCommon,Rhino.UI,EtoTekla Structures:
Tekla.Structures,.Model,.Drawing,.Datatype,.Dialog,.Catalogs,.PluginsRIB Presto: none needed â scripts drive Presto through the
__presto__scope variable (COM)AVEVA UE (E3D Design):
Aveva.Core.Database,.Geometry,.Utilities,Aveva.ApplicationFramework,.Presentation,PMLNetPyNet plugins:
Raen.Core.Pynet.*,Raen.{Product}.Pynet.*(any version â e.g.Raen.Core.Pynet.Resources,Raen.Navisworks.Pynet.2024,Raen.Civil3D.Pynet.2026,Raen.Rhino.Pynet.8,Raen.Tekla.Pynet.2026,Raen.Presto.Pynet,Raen.Aveva.Pynet.*)
Allowed Python Imports
clr, sys, json, re, time, datetime, pathlib, typing, threading, collections, xml, math, pandas, plotly, matplotlib, dash, webbrowser, psutil, functools, openpyxl, uuid, zipfile, io, mimetypes, difflib, csv, ifcopenshell, numpy, shapely, qgis, processing, pypdf, docx, rhinoscriptsyntax, scriptcontext
Allowed Python Submodules
Some modules are allowed at the submodule level only, preventing access to dangerous siblings:
Allowed | Blocked | Reason |
|
| Allow local HTTP serving, block outbound requests |
Blocked Python Imports
os, subprocess, shutil, socket, ctypes, pickle, importlib, urllib, signal, multiprocessing, tempfile, glob, inspect, code, codeop
Blocked Calls
eval, exec, compile, __import__, getattr, setattr, delattr, globals, locals, vars, breakpoint, open
Blocked Attribute Access
__builtins__, __subclasses__, __globals__, __code__
Any script that violates these rules is immediately rejected with a descriptive error message, without ever being sent to the plugin.
đ Project Structure
pynet_mcp/: Core MCP server logic (FastMCP).
pyproject.toml: Package configuration and dependency management.
đĨ Getting Started
Start building autonomous BIM workflows in minutes.
Install the bridge, connect your AI client, and turn natural language into real actions inside your models.
â FAQs
Have questions about installation, configuration, or usage? Check the full FAQ page:
đ PyNet FAQs
đ How This MCP Fits Into the Ecosystem
This MCP is part of a modular system designed to enable AI-driven BIM automation across desktop BIM tools.
This repository is designed to work alongside:
PyNet Platform â Executes scripts inside Navisworks, Revit, Civil 3D, Rhino, Tekla Structures, RIB Presto & AVEVA UE via Python.NET
PyNet Library â Gives the AI context with a Python scripts library
Together, these components enable:
Natural Language â AI â Python Script â PyNet â Host application â BIM Action
Component | Repository | Purpose |
PyNet Platform | Navisworks, Revit, Civil 3D, Rhino, Tekla Structures, RIB Presto & AVEVA UE plugin â hosts the Python.NET engine | |
PyNet Bridge (MCP) | This repo | MCP server - connects AI models to PyNET with including secure scripts validation |
PyNet Library | Script reference library and AI context |
đ Privacy Policy
PyNet Bridge runs entirely on your local machine. It does not collect, store, or transmit any personal data, telemetry, or analytics.
No data collection: The server does not send any information to RAEN Digital Tools or any third party.
Local-only communication: All communication between the MCP server and the PyNet plugin running inside Autodesk stays on your machine. No network sockets, no remote endpoints â nothing leaves your computer.
Your scripts and model data stay on your machine and are only processed by the AI client you have connected.
Full privacy policy: https://privacy.raendt.com/
đ Support
Issues / bug reports: GitHub Issues
FAQ: PyNet FAQs
Contact: info@raendt.com
đĨī¸ Platform Support
PyNet Bridge is Windows-only. It relies on Windows-specific local communication facilities and on desktop BIM applications (Navisworks, Revit, Civil 3D, Rhino, Tekla Structures, RIB Presto, AVEVA UE), which are Windows products. macOS and Linux are not supported.
đ License
This project is licensed under the MIT License.
mcp-name: io.github.RAEN-DT/pynet-mcp-bridge
Available Tools
24 toolscheck_plugin_statusBRead-only
Handshake ping to verify the plugin listener is responsive.
Inputs: pid (required). Returns: result
configure_output_windowCDestructive
Toggles the visibility of the PyNet log/output window.
Inputs: pid (required), is_available (required). Returns: result
create_pynet_moduleCDestructive
Creates a new custom Tab (ButtonsModule) in the Ribbon.
Inputs: pid (required), name (required). Returns: result
delete_pynet_moduleCDestructive
Permanently deletes a module and all its contents.
Inputs: pid (required), module_id (required). Returns: result
delete_script_buttonBDestructive
Permanently removes a ScriptButton from a module by Id.
Inputs: pid (required), button_id (required), module_id (required). Returns: result
deploy_script_buttonBDestructive
Installs a new ScriptButton into a specific module (Name, Script, Icon, Tooltip).
Inputs: pid (required), name (required), module_id (required), script_Path (required), +2 more. Returns: result
get_buttons_dataARead-only
Lists all script buttons for a specific module ID.
Inputs: pid (required), module_id (required). Returns: result
get_output_window_statusBRead-only
Checks if the output window is currently available/visible.
Inputs: pid (required). Returns: result
get_pynet_ui_layoutCRead-only
Fetches the full UI structure (ButtonsModules and ScriptButtons).
Inputs: pid (required). Returns: result
list_active_instancesARead-only
Scans the system for running host processes (Autodesk, Rhino, AVEVA UE, PyNET for Tekla/Presto) with an active PyNet IPC pipe.
Inputs: no named parameters. Returns: result
send_commandBDestructive
Direct script execution in the PyNet engine (Target PID, Script Name, Content).
Inputs: pid (required), content (required), timeout (required), script_name (required). Returns: result
send_command_by_pathADestructive
Executes a script file directly by path in the PyNet engine, without sending content inline.
Inputs: pid (required), timeout (required), file_path (required), script_name (required). Returns: result
update_script_buttonBDestructive
Updates metadata for an existing ScriptButton or moves it to another module.
Inputs: pid (required), name (required), tooltip (required), button_id (required), +4 more. Returns: result
viewer_clearARead-only
Clears highlights and ghosting in the open viewer.
Inputs: no named parameters. Returns: result
viewer_fitARead-only
Fits the camera to all models in the open viewer.
Inputs: no named parameters. Returns: result
viewer_get_propertiesARead-only
Reads element properties (name, model, psets) from the loaded package's properties.json.
Pass one or more pnt_ids to get their full properties (including psets) directly.
Called with no pnt_ids, returns a paginated lightweight index (pnt_id, name, model) instead
of every element â narrow it with model (exact model/discipline name, e.g. "Snowdon Towers
Sample HVAC") and/or search (case-insensitive substring of the element name), and page
through with limit/offset (default 200 per page, capped at 500). On a federated model
the unfiltered index can have tens of thousands of entries â always pass model or search
when you can, and use offset to page through the rest.
The data source is the .pnt's properties.json, NOT the viewer or IFC.
Inputs: limit, model, offset, search, +1 more. Returns: result
viewer_get_stateARead-only
Reads the viewer's last reported state: loaded models and the pnt_id of whatever the user currently has selected (click in the 3D view or the tree panel â null if nothing is selected). Use the returned pnt_id with viewer_get_properties for its details, or feed it into a clashes.json lookup to find what it clashes with.
Inputs: no named parameters. Returns: result
viewer_highlight_clashADestructive
Highlights a clash (element(s) A red, element(s) B green) and isolates the rest away.
Usually one pnt_id per side (a single clash pair), but either side accepts a list â e.g. one element (A) against every counterpart it clashes with (B), all shown at once.
Inputs: pnt_id_a, pnt_id_b. Returns: result
viewer_isolateADestructive
Isolates (hides everything except) the given pnt_ids in the open viewer.
Inputs: pnt_ids. Returns: result
viewer_isolate_modelsADestructive
Shows only the given model(s)/discipline(s) (by exact name, e.g. "Snowdon Towers Sample HVAC"), hiding every other loaded model. Cheaper than viewer_isolate for "just show me this discipline" requests â no need to resolve every element's pnt_id first. Get the exact model names from viewer_get_state's "models" list. Undo with viewer_clear.
Inputs: models. Returns: result
viewer_list_clashesARead-only
Reads the loaded package's clashes.json â the data source, NOT the viewer/IFC.
Returns each clash with the pnt_id identifiers needed to highlight it.
Inputs: no named parameters. Returns: result
viewer_load_packageBDestructive
Loads a .pnt into the open viewer and returns a summary read from clashes.json.
Inputs: pnt_path (required). Returns: result
viewer_selectADestructive
Highlights a set of elements in the open viewer by pnt_id, in neutral colours (yellow / blue) with nothing else hidden â a plain "look at these" pointer.
Pass a list of pnt_ids in pnt_ids (group A). Optionally pass a second list in
pnt_ids_b to highlight a second group in a distinct colour. Replaces any previous
selection. Use viewer_list_clashes / viewer_get_properties to obtain pnt_ids.
For a clash pair (red/green, with the rest of the model isolated away), use
viewer_highlight_clash instead.
Inputs: pnt_ids, pnt_ids_b. Returns: result
viewer_statusARead-only
Reports whether a PyNet BIM Viewer is open in VS Code (port, package, data dir).
Inputs: no named parameters. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogâĻ
TDQS
Scored across 24 tools
The viewer tools have the most potential for confusion (select vs highlight_clash vs isolate vs isolate_models vs clear), but the descriptions explicitly cross-reference each other and state when to prefer one over another, which resolves most of it. A few boundaries remain soft â check_plugin_status vs list_active_instances vs viewer_status all report 'is something alive', and configure_output_window vs get_output_window_status are near-mirror pairs â but they are separable.
Nearly everything follows verb_noun (get_, create_, delete_, update_, deploy_, list_, send_, configure_, check_), with a clean viewer_ namespace for the 3D side. Minor deviations: the ribbon/button noun is inconsistent ('buttons' in get_buttons_data vs 'script_button' in deploy/update/delete_script_button, and get_pynet_ui_layout is a noun-first outlier), and some tools carry a domain prefix while others do not.
24 tools is on the heavy side, and the surface spans four separate concerns (viewer control, ribbon/module management, IPC process discovery, script execution). The count is defensible given the breadth of the PyNet bridge, but a few low-value entries (viewer_fit, get_output_window_status) could be folded into neighbours.
Script buttons have full CRUD (deploy/update/delete/get_buttons_data), the viewer has load/state/properties/select/isolate/highlight/clear/fit, and execution has both inline and by-path variants. The main gap is module lifecycle: create_pynet_module and delete_pynet_module exist but there is no update/rename/reorder module tool, and there is no way to unload a package or detach from a running instance.
Maintenance
Related MCP Connectors
A2a Governance Bridge MCP Server by MEOK AI Labs
MCP federation gateway: route, govern and observe agent tools across clouds and MCP servers.
MCP Server for an Agent Task Marketplace
Telegram bridge for your MCP-compatible agent. Bidirectional, no LLM in our stack.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceControl AI agents creation and modification via MCP.-
- AlicenseAqualityFmaintenanceA bridge server that enables MCP-compatible AI assistants like Claude to seamlessly discover, communicate with, and manage A2A protocol agents.7113 PyPI146Apache 2.0
- AlicenseBqualityFmaintenanceA bridge server that connects Agent Communication Protocol (ACP) agents with Model Context Protocol (MCP) clients, enabling seamless integration between ACP-based AI agents and MCP-compatible tools like Claude Desktop.1665 PyPI24MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for cross-platform agent onboarding. Registers external agents, translates intents from LangChain, CrewAI, AutoGen, and A2A formats, and proxies cross-ecosystem transactions.MIT