Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Renga–Codex Bridge Copy sample.rnp, set the 3400 mm wall height to 3600 mm, save, reopen, and verify."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Independent, unofficial local MCP integration for Codex and Renga BIM. Codex interprets the task; this package provides typed COM operations, geometry, native documentation and saved-result verification. No AI API key, second agent service or design chat application is required.
0.2.0 preview — verified subset for Renga Professional 9.3.32980.0. Real local CLI and MCP scenarios create and edit native BIM objects, then save, close, reopen and check the requested values. See the scoped native evidence and testing instructions; hosted CI does not run Renga. Computer Use and mouse/keyboard emulation are prohibited for advertised API coverage. Renga and its SDK must be installed/licensed separately. No vendor binaries, SDK-generated wrappers, private models or credentials are shipped.
Windows x64, Python3.11+, installed Renga and separately downloaded SDK:
.\scripts\install.ps1 -PythonExe 'C:\path\to\python.exe' -SdkPath 'C:\path\to\RengaSDK'Read Russian installation or English installation, capabilities, previous work analysis and repository research.
Related MCP server: mcp-server-for-revit
flowchart LR
Codex --> MCP[stdio MCP server]
MCP --> Worker[serialized isolated STA worker]
Worker --> Adapter[typed local COM adapter]
Adapter --> Renga[Renga-owned project process]
Renga --> Verify[save / close / reopen / UUID and value checks]Core modules: session/safety/audit, SDK loading, BIM operations, geometry, catalogs, native drawings/exports, verification, deterministic plan helpers. API coordinates are millimeters; area m² and volume m³ are labelled explicitly.
The 21 MCP tools cover status and capabilities; inspection and catalogs; validated plans and disposable-copy previews; geometry and area verification; project copy, SaveAs and metadata; native drawing content, PDF, IFC and view rendering; rectangle plans and facade spacing. The complete names and verified boundaries are in CAPABILITIES.md.
New in 0.2: bridge_create_levels_project creates a new native project with
explicit nonzero levels and an optional orthogonal native Axis grid through
the official IFC importer. Own temporary slab carriers are removed; saved
native types, names, identities and elevations are checked after reopening.
Axis coordinates are verified through a fresh native IFC export, because the
tested Axis has no supported direct baseline getter. This bootstrap does not
merge levels/axes into an existing project or move existing level elevations.
The room_marker plan action positions a Room's intrinsic marker in global XY;
it does not create a standalone Tag. See level/grid plans.
.\.venv\Scripts\renga-bridge.exe doctor
.\.venv\Scripts\renga-bridge.exe inspect --project 'C:\your\test-root\sample.rnp'
.\.venv\Scripts\renga-bridge.exe apply --project 'C:\your\test-root\sample.rnp' --plan examples\rectangle.json --new
python -m pytest -m 'not integration' -qAutonomous writes are confined to RENGA_BRIDGE_WRITE_ROOT. Existing-file
edits receive verified backups and native undo transactions. Dependent hosts
and some calculated geometry need several applied batches before the final
save; failed plans discard unsaved changes, rather than promising a single
in-memory undo for every category. There is no MCP
blanket authorization bypass. Copy saved user files into the dedicated working
directory before editing; never run vendor sample scripts against user files.
Codex translates a task into an explicit millimeter-based JSON plan, inspects existing IDs/styles, validates the plan, optionally previews it on a copy, applies it and reads the reopened result. See operation plans. Reconnect the MCP server or start a new Codex session after installation to refresh its catalogue. Real stdio MCP and Codex discovery tests distinguish new-version coverage from historical 0.1.0 current-chat evidence; see the dated public proof.
Это инфраструктура доступа Codex к настоящей Renga через MCP и типизированный
COM API. Все операции выполняются локально, без Computer Use. Публикуемое
покрытие ограничено фактически проверенными возможностями. Автоматические
размеры/маркеры и создание автоматических помещений нельзя имитировать
текстом или изображениями. Новый проект с заданными ненулевыми уровнями и осями
создаётся через bridge_create_levels_project. Изменение отметок существующих
уровней по-прежнему отклоняется. Встроенный маркер помещения перемещается через
room_marker; это отдельная возможность от создания нового Tag.
MIT applies to our own source. See NOTICE for third-party and Renga SDK boundaries. This project does not represent Renga Software.
Create/edit models only under configured write root. Backup, undo transaction, save/reopen and requested-value checks included. Coordinates mm.
Inputs: project (required), operations (required), new.
Return release scope; research and actual local integration evidence are distinguished.
Inputs: no named parameters.
Inspect existing native styles/materials/scales/layouts/schedules before selecting actual IDs.
Inputs: project (required), collection.
Copy saved native project to a NEW writable destination and open the copy in an isolated process.
Inputs: output (required), project (required).
Create actual drawings with embedded level views and optional existing native schedules/text titles; no fake dimensions or tags.
Inputs: project (required), drawings (required).
Create a NEW native .rnp with levels at explicit elevation_mm and optional orthogonal Axis grid via official IFC import. Verify saved native identities/heights and fresh exported grid coordinates; remove own carriers. Does not modify existing level elevations.
Inputs: levels (required), project (required), grid.
Export IFC4 using Renga API to a new protected output path.
Inputs: output (required), project (required).
Export native drawings to one PDF using Renga API; requires a NEW output path inside write root.
Inputs: output (required), project (required), drawing_uuids.
Calculate explicit window offsets and piers in millimeters without mutating a model.
Inputs: count (required), width (required), length (required), end_pier, +1 more.
Extract genuine native mesh vertices/triangles in millimeters.
Inputs: project (required).
Read saved native UUIDs, parameters/definitions, quantities. Numeric IDs can change on SaveAs.
Inputs: project (required), kind, limit, offset, +1 more.
Read native drawing parameters and object persistent identities.
Inputs: project (required).
Apply proposed edits to a NEW disposable native copy, preserving the saved source file.
Inputs: output (required), project (required), operations (required).
Read actual native project Code/Name/Stage/Description and persistent project UUID.
Inputs: project (required).
Prepare an explicit generic four-wall/room/floor operation plan. Does not mutate Renga.
Inputs: depth, width, height, thickness.
Render a native view through IScreenshotService; no mouse, keyboard or Computer Use calls.
Inputs: output (required), project (required), width, height, +1 more.
Native SaveAs to a NEW protected destination; source disk file unchanged, UUIDs checked after reopen.
Inputs: output (required), project (required).
Back up, edit four native project metadata fields, save and verify after reopen; resource undo is not guaranteed.
Inputs: values (required), project (required).
Probe installed Renga in a new owned STA process; never attach to the user's session.
Inputs: no named parameters.
Validate plan structure without native mutation. This is NOT a native solver preview.
Inputs: operations (required).
Compare native room/floor areas with triangle calculations and explicit targets; conservative AABB candidates only.
Inputs: project (required), expected_areas, collision_types.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Scored across 21 tools
Tool purposes are mostly distinct: plan preparation, validation, preview-on-copy, native apply, export, render, and query operations target different objects. Some ambiguity remains among read-side tools such as bridge_inspect, bridge_project_info, bridge_catalogs, and bridge_inspect_drawings, though descriptions clarify their scopes.
All tool names use the same bridge_ prefix and snake_case style, which is highly consistent. However, the naming pattern mixes nouns, verbs, and verb_noun forms rather than following a strict verb_noun convention throughout.
21 tools falls into the 16–25 range that is borderline heavy for an MCP server. While each operation is distinct and the native CAD/BIM domain is complex, the set could likely be consolidated into fewer query and plan tools.
The set covers read, plan, validate, preview, apply, verify, export, render, save/copy, and status operations across the native project lifecycle. Explicit delete/close operations and some direct element-editing beyond plan application are missing, but these are minor gaps for the stated bridge purpose.
Headless CAD engine & MCP server for 2D/3D drafting, solids, DXF/SVG export, and automation.
An MCP server that audits the fairness of construction and renovation estimates in Japan. Provides fair-price ranges, overcharge detection, and verifiable unit-cost data based on JCCDB (65,520 items across 402 categories, CC BY 4.0, DOI-backed).
MCP Spec Compliance MCP — audits any MCP server.json against the official Model Context Protocol
A paid remote MCP for OpenAI Codex context compressor, built to return verdicts, receipts, usage log