MCP.Market

Pynet Bridge MCP server

by RAEN-DT·io.github.RAEN-DT/pynet-mcp-bridge·v1.7.1·3 stars

MCP implementation to connect AI agents with the PyNet Platform for BIM/Engineering automation.

A91/100grade A
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
Growing

3 stars263 downloads/wk

Reviews

Write one

Nobody has reviewed Pynet Bridge yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Pynet Bridge tools (24, 7 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • check_plugin_status

    Handshake ping to verify the plugin listener is responsive.

  • configure_output_window

    Toggles the visibility of the PyNet log/output window.

  • create_pynet_modulewrite action

    Creates a new custom Tab (ButtonsModule) in the Ribbon.

  • delete_pynet_modulewrite action

    Permanently deletes a module and all its contents.

  • delete_script_buttonwrite action

    Permanently removes a ScriptButton from a module by Id.

  • deploy_script_buttonwrite action

    Installs a new ScriptButton into a specific module (Name, Script, Icon, Tooltip).

  • get_buttons_data

    Lists all script buttons for a specific module ID.

  • get_output_window_status

    Checks if the output window is currently available/visible.

  • get_pynet_ui_layout

    Fetches the full UI structure (ButtonsModules and ScriptButtons).

  • list_active_instances

    Scans the system for running host processes (Autodesk, Rhino, PyNET for Tekla/Presto) with an active PyNet IPC pipe.

  • send_commandwrite action

    Direct script execution in the PyNet engine (Target PID, Script Name, Content).

  • send_command_by_pathwrite action

    Executes a script file directly by path in the PyNet engine, without sending content inline.

  • update_script_buttonwrite action

    Updates metadata for an existing ScriptButton or moves it to another module.

  • viewer_clear

    Clears highlights and ghosting in the open viewer.

  • viewer_fit

    Fits the camera to all models in the open viewer.

  • viewer_get_properties

    Reads element properties (name, model, psets) from the loaded package's properties.json.

  • viewer_get_state

    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.

  • viewer_highlight_clash

    Highlights a clash (element(s) A red, element(s) B green) and isolates the rest away.

  • viewer_isolate

    Isolates (hides everything except) the given pnt_ids in the open viewer.

  • viewer_isolate_models

    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.

  • viewer_list_clashes

    Reads the loaded package's clashes.json — the data source, NOT the viewer/IFC.

  • viewer_load_package

    Loads a .pnt into the open viewer and returns a summary read from clashes.json.

  • viewer_select

    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.

  • viewer_status

    Reports whether a PyNet BIM Viewer is open in VS Code (port, package, data dir).

Public scan report

scanner v0.1.10 · 2026-10-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan6 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Pynet Bridge compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 85% of 48,255 servers
Tools
24
the typical server has 7
Tools that change things
29%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
3
more than 80% of 28,688 servers
Downloads a week
263
more than 79% of 12,191 servers with a package

What its tools let an agent do: 17 read · 1 create · 1 change · 2 delete · 2 send or post · 1 run or deploy

Install Pynet Bridge in Claude Code, Cursor or VS Code

claude mcp add pynet-mcp-bridge -- uvx pynet-mcp-bridge
Add to Cursor

What the publisher says

From the Pynet Bridge repository's README, as published. We do not edit it. Read it on GitHub

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), enabling AI to generate, execute, and refine BIM workflows autonomously.

Available integrations include Navisworks Manage, Revit, Civil 3D, Rhino, Tekla Structures (2023–2026) and RIB Presto (budgets, COM 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.

⭐ 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.

🔄 How it works

  1. The user describes a task in natural language.
  2. The AI generates a Python script.
  3. PyNet Bridge validates and sends the script.
  4. The PyNet plugin executes it inside Autodesk.
  5. 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:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Pynet Bridge: common questions

Is Pynet Bridge MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the Pynet Bridge safety report
How do I install Pynet Bridge?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Pynet Bridge need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Pynet Bridge maintained?
The last commit was 12 days ago (2026-10-23). The latest release is v1.7.1.
How does Pynet Bridge compare with other MCP servers?
safety score 91/100 (higher than 85% of 48,255 servers); tools 24 (the typical server has 7); tools that change things 29% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.