build123d MCP

The materials explicitly state that no keys or environment variables are required, and no API tokens, account credentials, or third-party authorizations are mentioned, so credential exposure and abuse risk appears minimal.

No remote endpoints are declared, and the materials do not indicate sending user geometry data or prompts to external services; based on the available information, there is no clear data egress path.

The system flags executes-code, and the feature description includes execute/render/export, indicating normal MCP capability to run code locally or launch related processing workflows; this is typical for such tools, but it should be used in a controlled environment.

By its described functionality, the tool likely needs access to local geometry inputs and to write exported files or render outputs; the materials do not show data access beyond normal CAD workflow needs or any clearly excessive authorization, but local file read/write still warrants workspace isolation.

The source is an official registry listing, with an auditable open-source repository and updates within the last year, all of which reduce risk. Although the community star count is low and the license is not stated, this suggests limited maturity rather than a standalone high-risk red flag.