I have been working on RAPS (Rust Autodesk Platform Services CLI), an open-source tool designed to replace the fragile scripting usually required to automate CAD workflows in the cloud.
If you have ever worked with Autodesk APIs (formerly Forge), you know the pain of using the official Node.js or Python SDKs in CI/CD pipelines. You often end up with massive node_modules folders, dependency conflicts, and boilerplate code just to handle OAuth tokens or poll for job completion.
We built RAPS in Rust to provide a single-binary, zero-dependency solution that is safe by default for enterprise automation.
Key Technical Features: - Zero-Dependency: Statically linked binary. No need to install Python, pip, Node, or npm on your build agents. - Async/Polling Abstraction: Most CAD translation jobs are asynchronous. RAPS includes a wait flag that handles the polling loop and rate limits (HTTP 429) automatically, turning complex async logic into a single synchronous command. - Resumable Uploads: Automatically handles chunking and parallel uploads for multi-gigabyte Revit and DWG files. - CI/CD Ready: Maps API states to POSIX exit codes for reliable pipeline control in tools like GitHub Actions.
AI and Model Context Protocol (MCP): Perhaps most interestingly, RAPS is now an MCP Server. It supports Anthropic's open standard, allowing LLMs to natively see and touch the Autodesk ecosystem. Instead of writing scripts, you can use an agent to find all Revit files in a specific bucket older than 30 days and archive them.
The goal is to bridge the gap between raw API endpoints and the operational needs of modern DevOps, moving from imperative scripting to declarative infrastructure.
Would love to hear your thoughts on using Rust for API wrappers or how you are handling large-file operations in CI/CD.
Repo: https://github.com/dmytro-yemelianov/raps Docs: https://rapscli.xyz