Freecad

Created By
bonninra year ago
Overview

what is FreeCAD MCP?

FreeCAD MCP (Model Control Protocol) is a server-client interface that allows users to interact with FreeCAD, enabling command execution and information retrieval about the current FreeCAD document and scene.

how to use FreeCAD MCP?

To use FreeCAD MCP, configure the server using a JSON format, connect to the server via a socket, and send commands to retrieve scene information or execute scripts.

key features of FreeCAD MCP?

  • Retrieve detailed scene information including document properties and object details.
  • Execute arbitrary Python scripts within the FreeCAD environment.
  • Supports multiple operating systems with specific configuration examples.

use cases of FreeCAD MCP?

  1. Automating 3D modeling tasks in FreeCAD.
  2. Retrieving information about complex models for analysis.
  3. Running custom scripts to modify or create objects programmatically.

FAQ from FreeCAD MCP?

  • What is the purpose of FreeCAD MCP?

It simplifies the interaction with FreeCAD through a server-client architecture.

  • How do I install FreeCAD MCP?

Clone the repository, place the freecad_mcp directory in your FreeCAD modules directory, and restart FreeCAD.

  • Is FreeCAD MCP cross-platform?

Yes, it supports Windows, Linux, and macOS with specific configuration instructions.

Server Config

{
  "mcpServers": {
    "freecad": {
      "command": "/usr/bin/python3",
      "args": [
        "/home/USER/.FreeCAD/Mod/freecad_mcp/src/freecad_bridge.py"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
bonninr
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

32 minutes ago