Renga–Codex Bridge
Related Servers
Alternatives to Renga–Codex Bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server for Autodesk Revit (BIM) with 705+ API endpoints. Enables AI agents to create walls, place doors/windows, generate sheets, manage views, and produce construction documents via the Model Context Protocol. Uses named pipes for zero-crash Revit integration.22MIT
- FlicenseNot gradedqualityCmaintenanceNode.js MCP server enabling AI assistants to interact with Autodesk Revit for model operations, data queries, and sketch-to-building generation via LLM.231 npm-
- -licenseNot gradedqualityNot gradedmaintenanceConnects MCP clients like Claude, Codex, and Cursor to a running Autodesk Revit session for typed BIM queries, verified model edits, family authoring, exports, and Power BI workflows. It is open-source, Apache-2.0, and designed for reliable, verified outcomes.-
- AlicenseAqualityBmaintenanceAn MCP server that lets users query, validate, convert, and compare IFC/BIM files using natural language. Runs fully locally and integrates with AI agents like Claude.8MIT
- AlicenseAqualityCmaintenanceHardened MCP server for Autodesk Revit enabling LLMs to inspect and manipulate Revit models via pyRevit, with token authentication and capability profiles.261MIT
- FlicenseAqualityBmaintenanceCAD-engineering MCP tool server for parametric modeling, DFM validation, mechanical calculations, and more. Enables code-CAD builds (build123d/CadQuery), model inspection, meshing, and mechanical calculators via MCP stdio.11-
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.