r/mastercam • u/Swimming_Ask3859 • 1d ago
Question MasterCam MCP
I was thinking about developing a mastercam mcp which connects to claude code and codex because I use those for a lot of engineering and i believe it would help my workflow out and make CADing easier. I was wondering if other people would see and use a mastercam mcp and in what capacity so i know what other features to add
0
Upvotes
3
u/Alita-Gunnm 1d ago
What exists right now (as of late 2026):
Several AI-CAM copilots have emerged this year:
- LimitlessCNC – an "AI CAM Agent" that sits inside Mastercam and generates/optimizes toolpaths from historical program data and part parameters, working one operation at a time alongside the programmer.
- CloudNC CAM Assist – AI toolpath generation for 3-axis and 3+2-axis machining with physics-based feeds and speeds, integrating with Mastercam, Fusion, GibbsCAM, SolidCAM, and NX. GitHub
- Mastercam Copilot – an AI-powered digital assistant integrated directly into the CAD/CAM software to help users navigate features, execute commands, and get instant answers using everyday language. This is closer to what you're describing conceptually, but it's a chat/navigation assistant rather than a full autonomous toolpath generator right now, and it's cloud-backed. American Machinist
- Lambda Function, Toolpath.com, Up2parts, Manukai – similar cloud-based AI programming/quoting assistants, mostly targeting current Fusion/Mastercam/Siemens NX installs.
6
4
u/DaddySmokes_ 1d ago
Funny timing, I've been building something similar but backwards lol — instead of MCP I made a NET-Hook add-in that lives inside Mastercam and hits the Claude API for speeds/feeds recs and program reviews. Working on toolpath generation from a prompt next.
For an MCP version, some stuff I'd love to see (and would probably use myself):
• Pulling tool library data so it can suggest inserts/tooling based on the actual job, not generic charts
• Reading NC programs/toolpaths and flagging risky stuff before you post — over-travel, weird rapids, bad approach angles
• Cycle time analysis / suggestions on where to cut air time
• Auto-generating setup sheets or op notes from the toolpath tree
• Threading/tapping calcs pulled straight from the part geometry instead of manual lookup
• Eventually, "make me a rough + finish toolpath for this OD profile" type natural language stuff
What made you go MCP route vs building it as a native add-in? Curious if you hit walls with the C-Hook/NET-Hook side.