Rocketsmith
- 18 repo stars
- Updated April 22, 2026
- ppak10/RocketSmith
RocketSmith is an MCP extension and Claude Code plugin that orchestrates OpenRocket, build123d, and PrusaSlicer so agents can design, simulate, and slice model rockets.
About
RocketSmith exposes a model-rocket design, simulation, and fabrication toolchain to coding agents via an MCP extension bundled as a Claude Code marketplace plugin. It connects OpenRocket, build123d, and PrusaSlicer and closes the loop by updating simulations with measured printed-part weights. Reach for it when you want agents to design, simulate, and prepare printable rocket parts rather than hand-driving each desktop tool. Setup expects uv, GitHub SSH access, and verifying the MCP server after plugin install.
- OpenRocket flight simulation plus build123d parametric CAD
- PrusaSlicer FDM slicing in one agent-facing MCP extension
- Feeds printed part weights back into simulation
- Claude Code plugin install with /mcp verification
Rocketsmith by the numbers
- Data as of Jul 26, 2026 (Skillselion catalog sync)
/plugin marketplace add ppak10/RocketSmithAdd your badge
Show developers this marketplace is listed on Skillselion. Paste this into your README.
| repo stars | ★ 18 |
|---|---|
| Last updated | April 22, 2026 |
| Repository | ppak10/RocketSmith ↗ |
How do you let an agent drive rocket simulation, CAD, and slicing tools as one closed-loop workflow?
MCP-backed agent toolchain linking OpenRocket simulation, build123d CAD, and PrusaSlicer with post-print weight feedback loops.
Who is it for?
Developers automating model-rocket design who already use or can install OpenRocket, build123d, and PrusaSlicer.
Skip if: Software-only projects with no physical rocket toolchain or hosts that cannot run the MCP server and dependencies.
What you get
Designs, simulations, slice jobs, and stability checks reflect real printed weights fed back into OpenRocket.
Recommended Marketplaces
FAQ
What prerequisites does the README list?
uv for Python environment management and a GitHub SSH key to clone the plugin repository.
How is it exposed to Claude Code?
As a marketplace plugin whose MCP server you confirm with /reload-plugins and /mcp.
What does the closed loop mean?
Real printed-part weights are fed back into simulation for post-build stability verification.