Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

FreeCAD MCP

PYPI · FREECAD-MCP

Control FreeCAD from MCP clients: create and edit models, run Python and FEM analyses.

Available components

0 this week 59 Trust /100

Last scanned (12 hours ago)

Scores higher than 53% of PyPI servers

Category Design and Media

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 30 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability36
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 4715 tokens (~277/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_object" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 20 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 19 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 18 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 17 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 16 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 14 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 12 Nov 26 44

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed pypi/freecad-mcp@0.1.31

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 30 packages
Packages resolved 30
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 17 exposed · ~4,703 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_document ~92

Create a new document in FreeCAD. Args: name: The name of the document to create. Returns: A message indicating the success or failure of the document creation. Examples: If you want to create a document named "MyDocument", you can use the following data. ```json { "name": "MyDocument" } ```

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

create_object ~1,308

Create a new object in FreeCAD. ``obj_type`` must name a type registered in FreeCAD's C++ type system, such as "Part::", "PartDesign::" or "Fem::" types. A number of FreeCAD features are implemented in Python rather than C++ and so are not registered types; of those, these are supported here through dedicated factories, and each requires the properties listed beside it: Part::Tube InnerRadius, OuterRadius, Height Draft::Circle Radius Draft::Rectangle Length, Height Draft::Polygon FacesNumber, Radius Draft::Wire Points (list of {x, y, z}), optional Closed Any other Python-implemented type (Draft::Point, Draft::Ellipse, ...) must be built with ``execute_code`` instead. Note that the Draft factories name objects themselves, so for those the returned object_name will differ from the requested obj_name, which is applied to the object's Label instead. Always use the returned name in later get_object/edit_object calls. Args: doc_name: The name of the document to create the object in. obj_type: The type of the object to create (e.g. 'Part::Box', 'Part::Cylinder', 'Part::Cut', 'PartDesign::Body', etc.). obj_name: The name of the object to create. obj_properties: The properties of the object to create. include_screenshot: Whether to return a screenshot of the model (default True). Set to False to save tokens when visual feedback is not needed, e.g. for intermediate steps in a longer sequence of changes. view_name: The view orientation of the returned screenshot (default "Isometric"). Pick the view that best shows the change being made. Returns: A message indicating the success or failure of the object creation and a screenshot of the object. Examples: If you want to create a cylinder with a height of 30 and a radius of 10, you can use the following data. ```json { "doc_name": "MyCylinder", "obj_name": "Cylinder", "obj_type": "Part::Cylinder"…

NameTypeReqDescription
analysis_name–––
doc_namestringyes–
include_screenshotboolean––
obj_namestringyes–
obj_properties–––
obj_typestringyes–
view_namestring––

No output schema declared.

No examples provided.

delete_object ~172

Delete an object in FreeCAD. Args: doc_name: The name of the document to delete the object from. obj_name: The name of the object to delete. include_screenshot: Whether to return a screenshot of the model (default True). Set to False to save tokens when visual feedback is not needed, e.g. for intermediate steps in a longer sequence of changes. view_name: The view orientation of the returned screenshot (default "Isometric"). Pick the view that best shows the change being made. Returns: A message indicating the success or failure of the object deletion and a screenshot of the object.

NameTypeReqDescription
doc_namestringyes–
include_screenshotboolean––
obj_namestringyes–
view_namestring––

No output schema declared.

No examples provided.

edit_object ~209

Edit an object in FreeCAD. This tool is used when the `create_object` tool cannot handle the object creation. Args: doc_name: The name of the document to edit the object in. obj_name: The name of the object to edit. obj_properties: The properties of the object to edit. include_screenshot: Whether to return a screenshot of the model (default True). Set to False to save tokens when visual feedback is not needed, e.g. for intermediate steps in a longer sequence of changes. view_name: The view orientation of the returned screenshot (default "Isometric"). Pick the view that best shows the change being made. Returns: A message indicating the success or failure of the object editing and a screenshot of the object.

NameTypeReqDescription
doc_namestringyes–
include_screenshotboolean––
obj_namestringyes–
obj_propertiesobjectyes–
view_namestring––

No output schema declared.

No examples provided.

execute_code ~288

Execute arbitrary Python code in FreeCAD. Args: code: The Python code to execute. include_screenshot: Whether to return a screenshot of the model (default True). Set to False to save tokens when the code does not change the model's appearance, e.g. analytical or computational scripts whose result is printed output, or intermediate steps in a longer sequence of changes. view_name: The view orientation of the returned screenshot (default "Isometric"). Pick the view that best shows the change being made. timeout: Positive finite seconds for each of the queue and GUI execution budgets, overriding the 90 s default for this call (capped at 1800). Raise it for slow work that must run on the GUI thread, such as importing or exporting a large STEP assembly. Without it the call reports a timeout while the task keeps running, and the result is lost even though the work finishes. Prefer execute_code_async for heavy pure-geometry work that touches neither the document nor the GUI. Returns: A message indicating the success or failure of the code execution, the output of the code execution, and a screenshot of the object.

NameTypeReqDescription
codestringyes–
include_screenshotboolean––
timeout–––
view_namestring––

No output schema declared.

No examples provided.

execute_code_async ~572

Execute Python code in FreeCAD without waiting for completion. Use this ONLY for long-running background computations that do NOT touch the FreeCAD GUI or mutate the FreeCAD document tree directly. This tool runs the submitted code in a background thread and returns immediately. Because it does not run on FreeCAD's main GUI thread, the code must NOT directly call FreeCADGui APIs, manipulate the active view or selection, create or edit document objects, change object properties, call doc.recompute(), or save documents. FreeCAD documents and the Coin3D scenegraph are not thread-safe: writing to them from this thread races the GUI thread and can wedge FreeCAD's event loop, after which the RPC server stops responding entirely and FreeCAD must be restarted. Every document or view write must instead be handed to the GUI thread through the injected commit() helper: commit(fn, timeout=120) -> fn's return value Scripts share a live namespace. Saved functions can use commit() in later async calls; calling it from execute_code or a GUI callback raises immediately. Coordinate concurrent scripts that intentionally modify the same variables. commit() queues fn on the GUI thread, waits for it, and raises RuntimeError if dispatch fails or times out. Example: fused = base.fuse(addition).removeSplitter() # slow, safe in background def apply(): # runs on the GUI thread obj.Shape = fused doc.recompute() commit(apply) For code that is not dominated by heavy geometry computation, use execute_code instead. execute_code runs entirely on the FreeCAD GUI thread and is the safe default for normal FreeCAD automation. Use execute_code_async only when the heavy part is long-running OCCT geometry (e.g. fuse/cut/loft on already-fetched shapes) or other CPU-bound computation that would exceed execute_code's 90 s GUI-thread budget. Typical usage pattern: 1. Fetch shapes into module-level variables first (via execute_cod…

NameTypeReqDescription
codestringyes–

No output schema declared.

No examples provided.

execute_code_headless ~293

Run a FreeCAD Python script in a separate headless `freecadcmd` process. Use this for OCCT work that can crash or block FreeCAD: helical threads (makeHelix + makePipeShell), lofts and sweeps, booleans with many or B-spline tools, long parametric rebuilds. A native OpenCascade crash here only kills the helper process; the GUI and its open documents survive, and the tool reports the crash signal and the script's output. The script runs on the MCP server machine, independently of --host, in a fresh process without GUI: import FreeCAD/Part yourself, open documents from disk (FreeCAD.openDocument(path)), save results with doc.save()/saveAs() or Shape.exportBrep(). Nothing from the execute_code namespace is available. Print progress to stdout; it is returned when the process ends. After the script saved a .FCStd that is open in the GUI, call reload_document(doc_name) to show the result. Args: code: Complete Python script for freecadcmd. timeout: Positive finite seconds to wait before killing the process (default 600). Partial output is preserved on timeout. Returns: Exit status, crash/timeout diagnosis and the script's printed output.

NameTypeReqDescription
codestringyes–
timeoutnumber––

No output schema declared.

No examples provided.

get_async_status ~113

Report the state of background jobs started by execute_code_async. Does not use the FreeCAD GUI thread, so it answers even while a job runs. Args: job_id: The id returned by execute_code_async. Empty lists all running jobs and up to 20 recently completed jobs. Returns: For one job: its state (running/done/failed), the error and traceback when it failed. History is held in memory until FreeCAD exits.

NameTypeReqDescription
job_idstring––

No output schema declared.

No examples provided.

get_object ~159

Get an object from a document. You can use this tool to get the properties of an object to see what you can check or edit. Args: doc_name: The name of the document to get the object from. obj_name: The name of the object to get. include_screenshot: Whether to return a screenshot of the document (default True). Set to False to save tokens when only the object data is needed. view_name: The view orientation of the returned screenshot (default "Isometric"). Returns: The object and a screenshot of the object.

NameTypeReqDescription
doc_namestringyes–
include_screenshotboolean––
obj_namestringyes–
view_namestring––

No output schema declared.

No examples provided.

get_objects ~144

Get all objects in a document. You can use this tool to get the objects in a document to see what you can check or edit. Args: doc_name: The name of the document to get the objects from. include_screenshot: Whether to return a screenshot of the document (default True). Set to False to save tokens when only the object data is needed. view_name: The view orientation of the returned screenshot (default "Isometric"). Returns: A list of objects in the document and a screenshot of the document.

NameTypeReqDescription
doc_namestringyes–
include_screenshotboolean––
view_namestring––

No output schema declared.

No examples provided.

get_parts_list ~21

Get the list of parts in the parts library addon.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_rpc_status ~88

Get RPC and FreeCAD GUI-dispatch health. This tool does not use FreeCAD's GUI thread, so it remains available after a GUI operation times out. A ``stuck`` state identifies the operation that is still running and indicates that FreeCAD may need to be restarted. ``version_check`` is "ok" or says whether the addon or the server needs updating.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_view ~187

Get a screenshot of the active view. Args: view_name: The name of the view to get the screenshot of. The following views are available: - "Isometric" - "Front" - "Top" - "Right" - "Back" - "Left" - "Bottom" - "Dimetric" - "Trimetric" width: The width of the screenshot in pixels. If not specified, uses the viewport width. height: The height of the screenshot in pixels. If not specified, uses the viewport height. focus_object: The name of the object to focus on. If not specified, fits all objects in the view. Returns: A screenshot of the active view.

NameTypeReqDescription
focus_object–––
height–––
view_namestringyes–
width–––

No output schema declared.

No examples provided.

insert_part_from_library ~154

Insert a part from the parts library addon. Args: relative_path: The relative path of the part to insert. include_screenshot: Whether to return a screenshot of the model (default True). Set to False to save tokens when visual feedback is not needed, e.g. for intermediate steps in a longer sequence of changes. view_name: The view orientation of the returned screenshot (default "Isometric"). Pick the view that best shows the change being made. Returns: A message indicating the success or failure of the part insertion and a screenshot of the object.

NameTypeReqDescription
include_screenshotboolean––
relative_pathstringyes–
view_namestring––

No output schema declared.

No examples provided.

list_documents ~27

Get the list of open documents in FreeCAD. Returns: A list of document names.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

reload_document ~253

Close and re-open a document to pick up external file changes. Use this AFTER the document's .FCStd file has been modified by something outside of FreeCAD's GUI process — for example, a headless `freecadcmd` script that edited and saved the file. The open GUI document is otherwise unaware of on-disk changes; this tool closes the stale in-memory copy and reopens the file from disk so the GUI shows current geometry. Args: doc_name: The name of the open document to reload. Must match the name shown by ``list_documents``. Returns: A message confirming the document was reloaded, or describing the failure (document not loaded, no associated file, etc). FreeCAD names the reopened document after the file stem, which can differ from ``doc_name`` ("HandleConcept3D" saved as handle-concept-3d.FCStd reopens as handle_concept_3d); the reply names the document you should use from then on. Examples: ```json { "doc_name": "chassis" } ```

NameTypeReqDescription
doc_namestringyes–

No output schema declared.

No examples provided.

run_fem_analysis ~623

Run the CalculiX solver on an existing Fem::FemAnalysis container and return summary results. Prerequisites in the document, all created with `create_object`: - A Part-derived solid (e.g. Part::Box, PartDesign::Body) acting as the geometry. - A Fem::AnalysisPython container. - A material: type "Fem::MaterialCommon" with analysis_name set (built with ObjectsFem.makeMaterialSolid) and its Material given as a dict with units, e.g. {"Name": "Steel", "YoungsModulus": "210 GPa", "PoissonRatio": "0.3", "Density": "7900 kg/m^3"}. A dict read from the material library can come back empty; give the values. - A mesh: type "Fem::FemMeshGmsh" with analysis_name, Shape (the geometry) and CharacteristicLengthMax / CharacteristicLengthMin; it is generated when created. A section needs several elements across its thickness, or bending stress comes out far too low. - At least one Fem::ConstraintFixed and one Fem::ConstraintForce (or ConstraintPressure) whose References are faces of the geometry. - Set Force with its unit, e.g. "1000 N": create_object/edit_object reject unitless values. In existing documents and execute_code, a plain number uses millinewtons, so Force = 1000 applies 1 N. The force acts along the normal of the loaded face unless Direction links an edge or face; Reversed flips it. A SolverCcxTools is auto-created if the analysis has none. The reply lists mechanical loads captured in the same GUI operation as the solve (in N and MPa, with faces and direction). A failed load read stops the solve. Direction can be set to {"object_name": "Beam", "edge": "Edge1"}. The solver runs synchronously on the FreeCAD GUI thread and blocks all other RPC calls for its duration; do not fan out parallel requests. Returns max von Mises stress (MPa), max/min displacement (mm), node count, and the working directory CalculiX wrote to. On failure, returns the prerequisite-check or solver error along with the working directory for triage. Args: doc_name: Name…

NameTypeReqDescription
analysis_namestringyes–
doc_namestringyes–
include_screenshotboolean––
timeoutinteger––
view_namestring––

No output schema declared.

No examples provided.

Install

How do I install the FreeCAD MCP server?

FreeCAD MCP runs locally as a PyPI package, launched with uvx freecad-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · freecad-mcp

# add to Claude Code
claude mcp add neka-nat-freecad-mcp -- uvx freecad-mcp
Common questions

What is the FreeCAD MCP server?

FreeCAD MCP is listed in the public MCP registry as io.github.neka-nat/freecad-mcp. Control FreeCAD from MCP clients: create and edit models, run Python and FEM analyses. This page covers its PyPI package (freecad-mcp).

Is the FreeCAD MCP server safe to use?

FreeCAD MCP scores 59 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the FreeCAD MCP server expose?

FreeCAD MCP exposes 17 tools: create_document, create_object, edit_object, delete_object, execute_code_async, and 12 more. Their descriptions and schemas cost roughly 4,703 tokens of context every time the server is loaded.

Is the FreeCAD MCP server still maintained?

FreeCAD MCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the FreeCAD MCP server under?

FreeCAD MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the FreeCAD MCP server?

VerifyMCP ran 15 checks on FreeCAD MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about FreeCAD MCP: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.