Fusion Native MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FUSION_MCP_ENDPOINT | No | The endpoint of the Fusion MCP server | http://127.0.0.1:27182/mcp |
| FUSION_MCP_STATE_DIR | No | Directory to store state files for the Fusion MCP server | .fusion_mcp_state |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fusion_new_designB | Create a separate unsaved design. Supply the current document ID if one is open; the default requires no open active document. |
| fusion_capabilitiesA | Discover native tool schemas from the running Fusion installation. |
| fusion_inspectB | Read active document identity, design counts, parameters, feature health and CAM counts. |
| fusion_api_docsA | Search the installed Fusion API docs by regular expression, including adsk.cam. |
| fusion_documentsA | List open documents with creation IDs for explicit activation and edit targeting. |
| fusion_activate_documentA | Activate exactly one already-open document by creation ID. Reject duplicate IDs; never save or close other documents. |
| fusion_open_archiveA | Open a local F3D/F3Z archive in a new document; preserve other open documents. Reinspect returned document identity before editing. |
| fusion_active_commandB | Inspect any active command dialog and its current inputs. |
| fusion_execute_pythonA | Run Python defining run(context) inside Fusion. Supports all installed API namespaces. Mutations require document id from fusion_inspect and a unique operation_id. Repeat the same id/request to retrieve its prior result without executing again. Exceptions may leave partial changes. Inspect results separately; succeeded means the script returned, not that geometry or machining correctness was verified. Script code is trusted local code, not sandboxed. Use explicit units in scripts. |
| fusion_operation_statusC | Retrieve persisted operation status without retrying it. |
| fusion_acknowledge_operationA | After inspecting/recovering uncertain effects, record the outcome and unblock later edits. This neither cancels execution nor undoes changes. Verify that Fusion has finished first. |
| fusion_screenshotC | Capture the current viewport without changing its direction. |
| fusion_model_overviewA | Read parameter expressions, timeline, feature diagnostics and component structure. For large designs prefer paginated entity queries. |
| fusion_query_entitiesA | Discover geometry and re-usable entity tokens. Faces/edges require a body scope; profiles/points/curves require sketch scope. Filters are exact, never choose an ambiguous result silently. |
| fusion_set_parameterC | Create a user parameter or edit an existing user/model parameter expression, then recompute. |
| fusion_create_sketchA | Create a dimension-driven rectangle or circle at the component origin, and require full constraint. Returns profile references. |
| fusion_constrain_sketchA | Apply Fusion AutoConstrain to an existing sketch and report whether it became fully constrained. Geometry may be adjusted. |
| fusion_create_featureA | Create extrude/revolve/sweep/loft, fillet/chamfer/shell, booleans, or patterns. Query entity tokens first; supply their owning component. Inspect feature health after edits. |
| fusion_create_holesC | Create depth-limited simple holes at selected sketch points. |
| fusion_validate_designB | Report unhealthy features, underconstrained sketches and numeric body checks. This does not certify manufacturability. |
| fusion_recomputeB | Recompute the design and report remaining problems; does not invent replacements for broken references. |
| fusion_check_interferenceC | Analyze interference between explicit bodies/occurrences, excluding coincident faces. |
| fusion_assemblyC | Create/instance components or add rigid, revolute or slider as-built joints with optional motion limits. |
| fusion_bomB | Return a flattened component bill of materials and occurrence quantities. |
| fusion_exportA | Export STEP, STL, F3D archive, sketch DXF, or BOM JSON to a new absolute path. Existing destinations are rejected. |
| fusion_cam_inventoryC | Read CAM setups, operations, errors, toolpath validity and NC programs. |
| fusion_cam_browse_libraryC | Browse tool/post library folders and asset URLs; omit URL for the Fusion library root. |
| fusion_cam_toolsC | Read tool definitions with fingerprints to detect changes between selection and use. |
| fusion_cam_create_setupA | Activate Manufacture and create a milling setup with relative-box stock and a box-point WCS origin. Machine and fixtures are not automatically selected. |
| fusion_cam_parametersB | Inspect installed CAM parameter names and expressions on an operation or setup. |
| fusion_cam_create_operationB | Create a CAM operation with an explicitly selected tool and parameter expressions. Valid toolpaths must be generated and checked separately. |
| fusion_cam_generateA | Start asynchronous toolpath generation and return a job ID. Poll fusion_cam_job; do not resubmit on timeout. |
| fusion_cam_jobA | Poll generation completion and toolpath validity without blocking Fusion's main thread. Jobs become unknown after a Fusion restart. |
| fusion_cam_create_nc_programC | Experimental, not yet live-validated: prepare an NC program with a chosen post and empty output folder; does not post-process yet. |
| fusion_cam_post_processC | Experimental, not yet live-validated: post-process the explicitly configured NC program to its empty output folder. Inspect results and machine/post suitability before machining. |
| fusion_create_drawingA | Experimental, not yet live-validated: create an automatic cloud drawing from an already saved design, with configurable standard, sheet and auto-dimensions. Requires the installed Drawing API; may start a cloud job. |
| fusion_assembly_treeB | Read exact nested occurrence paths, component definitions, repeated-instance counts and external-link flags. |
| fusion_component_contextB | Inspect an existing component's native/proxy geometry, model parameters, feature origins, state fingerprint and all affected occurrence paths. |
| fusion_edit_component_parametersA | Edit only the selected component's existing model parameters. Reject stale state, foreign parameters, external links and unacknowledged repeated instances. Recompute and check new feature errors; return before/after definition states. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 39 tools
While many tools are distinct, several overlap in purpose: fusion_inspect and fusion_model_overview both read design health and parameters; fusion_create_sketch and fusion_constrain_sketch both affect sketches; fusion_cam_inventory and fusion_cam_parameters both inspect CAM data. Additionally, fusion_cam_create_nc_program and fusion_cam_post_process are experimental with unclear boundaries, and fusion_create_feature and fusion_create_holes both create geometry.
The naming is inconsistent: most tools follow the fusion_verb_noun pattern (e.g., fusion_screenshot, fusion_create_sketch), but there are deviations like fusion_bom and fusion_documents, which are nouns rather than verb-object. Also, fusion_cam_create_setup vs fusion_create_feature mixes 'cam_create' and 'create' prefixes, and fusion_cam_browse_library uses a bare verb 'browse' without a noun suffix, breaking the pattern.
With 39 tools, the server is heavily overloaded for a CAD/CAM MCP. The scope is broad (design, CAM, drawings, assembly), but the tool count far exceeds the typical well-scoped MCP, and several experimental tools (fusion_cam_create_nc_program, fusion_cam_post_process, fusion_create_drawing) are not live-validated, padding the count. A more modular design with separate design and CAM servers would be more appropriate.
The tool set covers core design (sketch, feature, parameters, assembly) and CAM workflows (setup, operation, toolpath generation, NC), but there are notable gaps: no explicit delete/cleanup operations, no direct sketch editing beyond auto-constrain, no material specification, and no inspection tools for assembly constraints beyond creation. Experimental tools like drawing creation lack verification steps, leaving dead ends in workflows.