Renga–Codex Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RENGA_BRIDGE_WRITE_ROOT | No | Directory to which autonomous writes are confined. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bridge_statusC | Probe installed Renga in a new owned STA process; never attach to the user's session. |
| bridge_inspectC | Read saved native UUIDs, parameters/definitions, quantities. Numeric IDs can change on SaveAs. |
| bridge_apply_planC | Create/edit models only under configured write root. Backup, undo transaction, save/reopen and requested-value checks included. Coordinates mm. |
| bridge_create_levels_projectB | 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. |
| bridge_validate_planB | Validate plan structure without native mutation. This is NOT a native solver preview. |
| bridge_preview_on_copyC | Apply proposed edits to a NEW disposable native copy, preserving the saved source file. |
| bridge_geometryC | Extract genuine native mesh vertices/triangles in millimeters. |
| bridge_verifyC | Compare native room/floor areas with triangle calculations and explicit targets; conservative AABB candidates only. |
| bridge_catalogsB | Inspect existing native styles/materials/scales/layouts/schedules before selecting actual IDs. |
| bridge_create_drawingsC | Create actual drawings with embedded level views and optional existing native schedules/text titles; no fake dimensions or tags. |
| bridge_inspect_drawingsC | Read native drawing parameters and object persistent identities. |
| bridge_export_pdfB | Export native drawings to one PDF using Renga API; requires a NEW output path inside write root. |
| bridge_export_ifcC | Export IFC4 using Renga API to a new protected output path. |
| bridge_render_viewC | Render a native view through IScreenshotService; no mouse, keyboard or Computer Use calls. |
| bridge_copy_projectC | Copy saved native project to a NEW writable destination and open the copy in an isolated process. |
| bridge_save_asC | Native SaveAs to a NEW protected destination; source disk file unchanged, UUIDs checked after reopen. |
| bridge_project_infoC | Read actual native project Code/Name/Stage/Description and persistent project UUID. |
| bridge_set_project_infoC | Back up, edit four native project metadata fields, save and verify after reopen; resource undo is not guaranteed. |
| bridge_rectangle_planC | Prepare an explicit generic four-wall/room/floor operation plan. Does not mutate Renga. |
| bridge_facade_spacingB | Calculate explicit window offsets and piers in millimeters without mutating a model. |
| bridge_capabilitiesC | Return release scope; research and actual local integration evidence are distinguished. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
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.