Fusion MCP Servers Explained: Desktop, Data and Compute — and Where CAM Fits
Autodesk now has three MCP servers for Fusion. With the public beta of Fusion Compute MCP, announced on 15 September 2026, an AI agent can build parametric models, program CAM and post NC code in a Fusion session running in the cloud. The names are close enough to be confusing — Fusion MCP, Fusion Data MCP, Fusion Compute MCP — and they do different jobs.
This guide explains what each server does, what an agent can actually do in CAM today, and the limits of the beta. It also covers the question every CNC programmer will ask next: once an agent has posted the NC code, who checks that the machine can actually run it? That is the step Eureka MCP adds.
What MCP Means for Fusion
The Model Context Protocol (MCP) is an open standard for connecting AI applications to external tools and data. Instead of describing what you should click, an agent connected to an MCP server can discover what the software can do and then do it.
For Fusion, that means an AI assistant such as Claude, or an agent running in VS Code, can create sketches and features, set up manufacturing operations and generate toolpaths by calling Fusion directly. As Autodesk puts it, the MCP server "provides the environment and the tools, not the intelligence": what gets done depends on the model driving it.
The Three Fusion MCP Servers
| Server | Works on | Purpose |
|---|---|---|
| Autodesk Fusion MCP | The Fusion desktop client on your machine | Real-time, local design and make actions |
| Autodesk Fusion Data MCP | The data around your designs | Hubs, projects, folders, permissions, properties and metadata |
| Autodesk Fusion Compute MCP | Fusion sessions in Autodesk's cloud | One or more cloud sessions, each agent with its own Fusion environment |
The practical difference between the first and the third is where the work happens. Fusion MCP operates the Fusion you have open on your desktop: you watch the agent work, and it uses your session. Fusion Compute MCP gives each agent its own Fusion in the cloud, so your desktop client stays free — and several agents can work in parallel. Fusion Data MCP doesn't model or machine anything; it manages where designs live and who can access them.
What an Agent Can Do with Fusion Compute MCP
Fusion Compute MCP exposes more than 7,000 endpoints of Fusion's TypeScript API behind a single execute tool. According to Autodesk, an agent session starts in seconds and can run for up to an hour, covering:
- Parametric modeling — create, read, update and delete sketches and features: extrusions, revolves, fillets, chamfers, patterns.
- Manufacturing — setups, CAM templates, toolpaths and posted NC code.
- Assemblies — components, occurrences, transforms and joints.
- Documents and export — open, save and browse hubs and projects in Fusion Team; export STL or STEP.
Autodesk's CAM example is telling: an agent designs a two-part injection-molded enclosure, builds a family mold with core and cavity, then programs face, adaptive roughing and parallel finishing on both plates. The toolpaths generate in about six and a half seconds — a design-to-manufacturing chain driven end to end from a chat window.
Your agent posted the NC code. Now verify it on the machine.
Eureka MCP lets the same AI agent run the program on a digital twin of your CNC machine, read the collisions and errors, fix the code and simulate again — before anything reaches the spindle.
Request Eureka MCP early access →Beta limits and requirements
- An Autodesk account, an active Fusion licence and a Fusion Team hub.
- Two concurrent sessions per user; one hour maximum per session; sessions stop after 15 minutes idle.
- Sessions queue when the service is at capacity.
- Sessions are temporary: anything you want to keep must be saved to Fusion Team or exported before the session ends.
Autodesk says to expect these limits to change during the beta. The connection details and current documentation are in Autodesk's announcement.
Which Fusion MCP Server for a CAM Workflow?
Use Fusion MCP (desktop) when you want to work alongside the agent: you see each step in your own Fusion, and whatever it produces stays on the computer where your other tools run.
Use Fusion Compute MCP when the agent should work on its own, or when several agents run in parallel — exploring variants, programming multiple parts — without tying up your desktop.
Add Fusion Data MCP when the agent also has to organize the results: projects, folders, permissions and metadata.
From Posted NC Code to the Machine
A posted NC program is not the end of the chain. It is the file the machine will actually execute, and its safety depends on things the toolpath alone doesn't show: the post-processor output, the controller's interpretation of each block, the machine's kinematics and travel limits, the fixture and the tool holders.
Machine simulation is not among the capabilities Autodesk lists for Fusion Compute MCP. When an AI agent — not a person — has produced the program, verifying it on the machine becomes more important, not less: there may be no programmer who has looked at every line.
The missing step: an agent can now go from model to posted NC code in minutes. Before that program reaches a real machine, it should run on a digital twin of that machine.
This is where Eureka MCP fits. It connects the same MCP-compatible agent to Eureka Virtual Machining, so the agent that posted the program can also load it into Eureka, simulate it on the CNC digital twin, read the collisions and errors, correct the program and simulate again:
model, CAM, post
CNC digital twin
If the simulation finds a problem, the agent reads the result, corrects the program and runs it through Eureka again — until the program runs clean.
We have run Eureka MCP with Claude Code and in VS Code with the GitHub Copilot and Codex extensions. With Fusion Compute MCP, remember that sessions are temporary: save or export the posted program before the session ends, so it can be verified.
Eureka MCP is in early access. Request access to connect your AI agent to CNC simulation.
Frequently Asked Questions
What is the difference between Fusion MCP and Fusion Compute MCP?
Fusion MCP drives the Fusion desktop client running on your machine, in real time. Fusion Compute MCP runs Fusion sessions in Autodesk's cloud, so an agent works in its own environment without occupying your desktop — and several agents can work in parallel.
Can an AI agent generate G-code with Fusion Compute MCP?
Yes. Autodesk lists setups, CAM templates, toolpaths and posted NC code among the manufacturing capabilities available to agents.
What do I need to use Fusion Compute MCP?
An Autodesk account, an active Fusion licence, a Fusion Team hub and an MCP-compatible AI client. Autodesk mentions Claude, Antigravity and VS Code among the tools you can use.
Does Fusion Compute MCP simulate the CNC machine?
Machine simulation is not among the capabilities Autodesk lists for Fusion Compute MCP. To check what the machine will actually do with the posted program — kinematics, travel limits, fixtures, controller behavior — run it in a machine simulator such as Eureka, which AI agents can operate through Eureka MCP.
Is Fusion Compute MCP production-ready?
It is a public beta with limited access: two sessions per user, one hour per session, and queues at capacity. Autodesk expects the limits to change as the service scales.