What are the runtime and dependency requirements?
Windows, SolidWorks 2026, .NET Framework 4.8, and Python 3.x. The adapter requires the FastMCP package. The execution layer communicates over REST at `http://localhost:5000`.
@eyfel
Basic information
This MCP server integrates with SolidWorks API and structuring it into Claude-compatible context streams.
Documentation reviewed 2026-10-25
The eyfel repository now describes SolidPilot: a SolidWorks execution layer with a Python MCP adapter. It is not a generic cross-platform CAD server.
The current requirements specify Windows and SolidWorks 2026. Build and run the C# execution layer, install the Python adapter dependencies and configure the adapter path. Check the upstream version requirements before reusing an older SolidWorks setup.
These notes check the linked documentation, not a live authenticated connection. Suggested checks are steps for you to run.
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
An MCP server that lets AI models work with SolidWorks at the CAD feature level. It converts user intent into a CAD-neutral intermediate representation, then a deterministic compiler lowers it into concrete SolidWorks operations. Designed for any MCP-capable AI client (Claude, OpenClaw, OpenAI agents, local LLMs).
Requires Windows, SolidWorks 2026, .NET Framework 4.8, and Python 3.x. Build the C# execution layer with MSBuild, run it as a headless server on http://localhost:5000, then run the Python adapter with FastMCP. Register the adapter with an MCP-capable AI client by adding an entry to its mcpServers config (e.g., Claude Desktop’s claude_desktop_config.json). Restart the client after any config change.
Windows, SolidWorks 2026, .NET Framework 4.8, and Python 3.x. The adapter requires the FastMCP package. The execution layer communicates over REST at `http://localhost:5000`.
It raises the abstraction level: the AI reasons in terms of CAD features (e.g., “put a hole in the top face”), not individual API methods. A deterministic compiler converts that intent into the concrete SolidWorks operations, reducing the number of model calls per request.
No. The IR schema is drafted and an experimental path exists behind a flag (`SOLIDPILOT_ENABLE_IR=true`), but the full compiler (especially the reference resolver) is not yet implemented. The current working path uses low-level MCP tools directly.
The adapter communicates with the execution layer via plain REST. MCP sits at the top as the AI-client-facing boundary. No authentication mechanism is mentioned; the server is assumed to run locally.
Early alpha. Part-modeling tools are most mature. Drawing tools are a maturing capability. The strategic IR+compiler path is not yet built. Section views are experimental and not reliable under automation.

B2B competitive intelligence, live sales battlecards, 5-axis ICP prospect fit scoring, and tech stack teardowns over MCP and REST with cited public-web evidence.

A free remote MCP server for The Living Bread. Bible passages read word for word from a stored public domain text with an evidence label, keyword search and cross references, real churches, gatherings and prayer groups w
Free moving quotes for AI agents from Next Generation Movers, a licensed interstate mover (USDOT 3764697). US long-distance nationwide and local DC/MD/VA. Indicative ballpark price and booking options; optional $0.01 x40
Painless E2E Automation for Mobile and Web
🚀 The fast, Pythonic way to build MCP servers and clients.
Comments