FreeCAD MCP can create, edit, and delete FreeCAD objects and documents., The `execute_code` tool can run arbitrary Python code inside FreeCAD, so only use it with trusted prompts and human review., Remote connections can bind the RPC server beyond localhost when enabled; keep allowed IPs narrow and restart the RPC server after changing access settings., FEM analysis and part-library insertion can create files, use local compute, and modify active FreeCAD documents., Screenshots and active-view feedback can expose proprietary CAD models or unreleased product designs.
Privacy notes
CAD geometry, object names, document structure, screenshots, Python code, prompts, RPC host settings, FEM summaries, part-library selections, and tool outputs may be visible to the MCP client and model provider., FreeCAD documents may contain proprietary product designs, measurements, manufacturing details, customer data, or safety-critical engineering assumptions., Avoid enabling remote access or auto-start behavior on shared networks unless the allowed IP list and host firewall are reviewed., Keep generated CAD files and screenshots out of shared prompts, logs, and repositories unless they are approved for disclosure.
Author
neka-nat
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-05
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
5 safety and 4 privacy notes across 5 risk areas. Review closely: network access, third-party handling.
5 areas
SafetyGeneralFreeCAD MCP can create, edit, and delete FreeCAD objects and documents.
SafetyExecution & processesThe `execute_code` tool can run arbitrary Python code inside FreeCAD, so only use it with trusted prompts and human review.
SafetyNetwork accessRemote connections can bind the RPC server beyond localhost when enabled; keep allowed IPs narrow and restart the RPC server after changing access settings.
SafetyLocal filesFEM analysis and part-library insertion can create files, use local compute, and modify active FreeCAD documents.
SafetyGeneralScreenshots and active-view feedback can expose proprietary CAD models or unreleased product designs.
PrivacyThird-party handlingCAD geometry, object names, document structure, screenshots, Python code, prompts, RPC host settings, FEM summaries, part-library selections, and tool outputs may be visible to the MCP client and model provider.
PrivacyGeneralFreeCAD documents may contain proprietary product designs, measurements, manufacturing details, customer data, or safety-critical engineering assumptions.
PrivacyNetwork accessAvoid enabling remote access or auto-start behavior on shared networks unless the allowed IP list and host firewall are reviewed.
PrivacyLocal filesKeep generated CAD files and screenshots out of shared prompts, logs, and repositories unless they are approved for disclosure.
Safety notes
FreeCAD MCP can create, edit, and delete FreeCAD objects and documents.
The `execute_code` tool can run arbitrary Python code inside FreeCAD, so only use it with trusted prompts and human review.
Remote connections can bind the RPC server beyond localhost when enabled; keep allowed IPs narrow and restart the RPC server after changing access settings.
FEM analysis and part-library insertion can create files, use local compute, and modify active FreeCAD documents.
Screenshots and active-view feedback can expose proprietary CAD models or unreleased product designs.
Privacy notes
CAD geometry, object names, document structure, screenshots, Python code, prompts, RPC host settings, FEM summaries, part-library selections, and tool outputs may be visible to the MCP client and model provider.
FreeCAD documents may contain proprietary product designs, measurements, manufacturing details, customer data, or safety-critical engineering assumptions.
Avoid enabling remote access or auto-start behavior on shared networks unless the allowed IP list and host firewall are reviewed.
Keep generated CAD files and screenshots out of shared prompts, logs, and repositories unless they are approved for disclosure.
Prerequisites
FreeCAD installed and available on the machine running the FreeCAD add-on.
The repository's `addon/FreeCADMCP` directory copied into the correct FreeCAD add-on directory for the platform.
FreeCAD restarted, MCP Addon workbench selected, and the RPC server started.
uvx available to the MCP client runtime.
Remote connection settings, allowed IPs, and host flags reviewed before controlling FreeCAD from another machine.
FreeCAD MCP connects Claude-compatible MCP clients to FreeCAD through a FreeCAD
add-on and Python MCP server. It can create documents, create and edit objects,
delete objects, execute Python code inside FreeCAD, insert parts from the
FreeCAD parts library, capture the active view, inspect objects, list parts,
and run FEM analysis on an existing analysis.
The upstream README documents copying the addon/FreeCADMCP directory into the
platform-specific FreeCAD add-on directory, restarting FreeCAD, starting the RPC
server from the MCP Addon workbench, and launching the MCP server with
uvx freecad-mcp.
These sources were reviewed on 2026-06-05. Prefer the live repository,
README, package metadata, and PyPI metadata for current add-on paths, tool list,
remote-connection behavior, Python package version, and launch commands.
Features
Create new FreeCAD documents.
Create, edit, inspect, and delete FreeCAD objects.
Execute Python code inside FreeCAD.
Insert parts from the FreeCAD parts library.
Capture screenshots of the active FreeCAD view.
List available parts and current document objects.
Run CalculiX FEM analysis on an existing FreeCAD FEM analysis.
Use text-only feedback mode to reduce token usage.
Configure remote RPC connections with explicit allowed IPs.
Installation
Install the FreeCAD add-on first by copying addon/FreeCADMCP from the
repository into the appropriate FreeCAD add-on directory for your platform.
Restart FreeCAD, select the MCP Addon workbench, and start the RPC server.
Ask Claude to create a basic CAD document from a natural-language description.
Inspect or modify existing FreeCAD objects.
Generate quick design iterations while reviewing each tool call.
Insert standard parts from the FreeCAD parts library.
Capture the active view for design feedback.
Run a FEM analysis summary on a prepared FreeCAD analysis.
Safety and Privacy
FreeCAD MCP can directly modify CAD documents and run arbitrary Python code
inside FreeCAD. Treat it as a powerful local application-control bridge, not a
read-only viewer. Review tool calls before allowing object deletion, code
execution, remote RPC access, FEM solver runs, or changes to important models.
CAD files and screenshots may reveal product designs, dimensions, tolerances,
manufacturing details, or customer projects. Keep the RPC server local by
default, use strict allowed IPs for remote access, and avoid sharing extracted
model data with a model provider unless the design is approved for disclosure.
Duplicate Check
No neka-nat/freecad-mcp entry, freecad-mcp package entry, or matching source
URL was found in content/mcp.
Show that FreeCAD MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/freecad-mcp-server)
How it compares
FreeCAD MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
Connect Claude to a Google Colab runtime. Colab MCP starts a local FastMCP server and websocket proxy, waits for an authorized Colab-origin browser connection, then exposes the session's notebook and runtime tools to your MCP client over stdio.
Django extension that exposes MCP endpoints and stdio transport for Django apps, with declarative model query tools, custom toolsets, DRF create/list/ update/delete tool publishing, serializer output, and MCP inspection.
FastAPI-native package that exposes FastAPI endpoints as Model Context Protocol tools while preserving schemas, docs, and existing authentication dependencies.
✓FreeCAD MCP can create, edit, and delete FreeCAD objects and documents.
The `execute_code` tool can run arbitrary Python code inside FreeCAD, so only use it with trusted prompts and human review.
Remote connections can bind the RPC server beyond localhost when enabled; keep allowed IPs narrow and restart the RPC server after changing access settings.
FEM analysis and part-library insertion can create files, use local compute, and modify active FreeCAD documents.
Screenshots and active-view feedback can expose proprietary CAD models or unreleased product designs.
✓Colab MCP runs a local websocket proxy and waits for a Google Colab browser session to connect before proxying session tools.
The server creates a bearer-style proxy token and accepts a single authorized Colab-origin websocket connection at a time.
A connected Colab runtime can execute code and interact with notebooks, outputs, files, variables, packages, and mounted resources depending on the session and tools exposed by Colab.
Use disposable notebooks or reviewed development sessions before allowing Claude to run code or inspect outputs.
Avoid connecting notebooks that have access to production data, cloud credentials, private datasets, paid accelerators, or long-running jobs unless the workflow has explicit approval.
✓Django MCP Server can expose Django model querysets, custom Python methods, DRF create/list/update/delete views, serializers, resources, and low-level FastMCP tools to an MCP client.
Published DRF create, update, and delete tools can mutate application data if their serializers, views, and authentication rules permit it.
The README notes that built-in DRF authentication classes, permission classes, filter backends, and pagination are disabled for published DRF tools in favor of MCP authentication; review this carefully before reusing production views.
Query tools can evaluate QuerySets and return database records; restrict queryset scope and fields before exposing sensitive models.
Require confirmation and application-level authorization before exposing write tools, email-sending methods, admin-like actions, or tools that touch customer, employee, financial, health, or regulated data.
✓FastAPI-MCP can expose real API operations as tools; do not blindly expose admin, destructive, payment, credential, or production-write endpoints.
Preserve and test FastAPI authentication dependencies before letting agents call protected tools.
Review request models, side effects, rate limits, and authorization boundaries for each endpoint.
Prefer explicit allowlists and non-production deployments for early MCP testing.
Privacy notes
✓CAD geometry, object names, document structure, screenshots, Python code, prompts, RPC host settings, FEM summaries, part-library selections, and tool outputs may be visible to the MCP client and model provider.
FreeCAD documents may contain proprietary product designs, measurements, manufacturing details, customer data, or safety-critical engineering assumptions.
Avoid enabling remote access or auto-start behavior on shared networks unless the allowed IP list and host firewall are reviewed.
Keep generated CAD files and screenshots out of shared prompts, logs, and repositories unless they are approved for disclosure.
✓Notebook code, prompts, outputs, logs, variables, datasets, file paths, runtime metadata, package lists, browser session details, and generated websocket tokens can be visible to the MCP client and model provider.
Colab notebooks may contain API keys, OAuth tokens, mounted Drive paths, secrets in environment variables, private model weights, customer data, or unpublished research.
Local log files are created under a temporary Colab MCP log directory by default unless a log directory is specified.
Review Google Colab, MCP client, model provider, and organization retention policies before sending notebook or runtime context to an assistant.
✓Django sessions, request headers, model names, field names, primary keys, QuerySet results, serializer output, DRF request bodies, custom tool arguments, and tool responses can be exposed to the MCP client.
Exposed models may contain user accounts, permissions, customer records, orders, messages, files, logs, internal notes, audit trails, or application-specific secrets.
Remote streamable HTTP deployments can move application data outside the original Django UI and audit path if MCP auth, OAuth metadata, and retention are not configured correctly.
Stdio usage can still expose data through local MCP client logs, transcripts, and tool traces.
Keep MCP endpoint access, serializer fields, queryset filters, and tool docstrings intentionally narrow for each app.
✓Request schemas, response schemas, OpenAPI docs, route names, validation errors, and endpoint outputs may be visible to the MCP client and model.
Endpoint calls can expose user data, internal identifiers, tokens in payloads, and business logic.
Keep API credentials, service secrets, and test-user tokens out of prompts, repository files, and logs.
Prerequisites
FreeCAD installed and available on the machine running the FreeCAD add-on.
The repository's `addon/FreeCADMCP` directory copied into the correct FreeCAD add-on directory for the platform.
FreeCAD restarted, MCP Addon workbench selected, and the RPC server started.
uvx available to the MCP client runtime.
uv or uvx available to run the server from the GitHub repository.
Local MCP client that supports `notifications/tools/list_changed`.
Google Colab account and browser session you are authorized to use.
Local machine access, because upstream documents that the MCP client must run locally.
Django 4 or 5 application with Python 3.10 or newer.
mcp_server added to INSTALLED_APPS and mcp_server.urls included in the Django URL configuration.
Review of which Django models, querysets, custom methods, DRF views, serializers, and request context should be exposed to MCP clients.
Authentication classes configured through DJANGO_MCP_AUTHENTICATION_CLASSES before exposing non-public data over streamable HTTP.
Python 3.10 or newer, with Python 3.12 recommended by the project.
Existing FastAPI application or a reviewed FastAPI service design.
uv or pip for installing fastapi-mcp.
Clear endpoint allowlist and authentication policy before exposing API operations to an agent.