For machine builders, panel shops and plant engineers running WSCAD ELECTRIX
A WSCAD MCP server gives Claude, ChatGPT or Copilot named tools for WSCAD ELECTRIX projects, pages, articles and parts lists. No vendor WSCAD MCP server exists as of 29 October 2026; the AI Copilot answers only inside ELECTRIX. Pexon builds six tools, five read-only, on the Automation Interface add-on.
Why WSCAD is hard for agents
01 · Desktop
The Automation Interface runs against a licensed WSCAD installation on a Windows host. That it runs in the background without a user present is the useful part; it still needs that host, so the connector needs an ELECTRIX machine your IT team operates and patches.
02 · Licensing
The Automation Interface is an add-on available with the Professional, Installation, BA Project and Ultimate products, and it needs the Project Wizard add-on to generate circuit diagrams. PLM/ERPsync needs User Rights as a prerequisite, and User Rights has to be added to every licence at the site. WSCAD publishes this scope but no price, so which route is open depends on the licences in your building, and the blueprint settles that with WSCAD first.
03 · Docs
WSCAD documents what each add-on does, but nothing about the data model, authentication or endpoints is readable in public, and the manuals ship inside a licensed installation. That is why every tool below is confirmed against your installation in the blueprint instead of quoted from a doc portal. That check is the first week's work, and its result is written down whether it comes out yes or no.
04 · Writes
A wrong article or symbol change propagates into panel build and wiring. The connector therefore reads, and the one change tool drafts a proposal that an engineer applies in ELECTRIX.
Checked 29 October 2026
| What we found | |
|---|---|
| Interfaces | Automation Interface (add-on) (an external configurator starts WSCAD in the background and the plans are generated; no format or protocol published, docs not published) · PLM/ERPsync (add-on) (scheduled one-way sync into the WSCAD parts database, docs not published) · PRO.FILE PLM (add-on) (project check-in and check-out against PROCAD PRO.FILE, docs not published) · Point interfaces to automation tooling (vendor-specific export and import, docs not published) |
| Authentication | Not documented in public. The Automation Interface runs as a background process against a licensed WSCAD installation on a Windows host, so it carries that installation's licence rather than a per-user token. Per-user restriction comes from the User Rights add-on, which WSCAD states has to be added to every licence at the site, and since version 7.4.1.7 on 7 August 2026 functions locked by User Rights cannot be run through the AI Copilot either. |
| Vendor MCP server | No vendor server. No WSCAD MCP server exists from the vendor as of 29 October 2026: a site search on wscad.com for MCP and for Model Context Protocol returns nothing, and the release notes do not mention it. The AI Copilot is an assistant inside ELECTRIX, not an interface for agents outside the product. |
| Vendor AI assistant | AI Copilot, in ELECTRIX since version 7.3.0.16 on 18 November 2024, and current in the ELECTRIX AI 2026 line, version 7.4.1.16 of 21 October 2026: it answers questions and runs instructions in the product. Version 7.4.0.17 on 12 February 2026 added a menu item WSCAD calls "Eigenes Wissen", which answers from uploaded PDF, TXT and DOCX files for one project or across all of them, plus article import from wscaduniverse.com by article number. |
| Other connectors | None found. A GitHub and web search on 29 October 2026 turned up no third-party WSCAD MCP server; the CAD servers that exist target OpenSCAD and AutoCAD-style DWG and DXF files. For EPLAN, by contrast, community repos drive a licensed desktop seat. |
WSCAD GmbH, part of the Buhl group (DE). Electrical and controls engineering teams at machine builders, plant engineering firms, panel shops and building-automation contractors; WSCAD states more than 40,000 users across machinery and plant engineering, building automation and the electrical trades.
What we build
WSCAD GmbH, part of the Buhl group does not publish its interface reference, so every backend below is confirmed against your installation in the blueprint before a tool is built.
# wscad-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
list_projects: # folder or workspace -> WSCAD projects with name and path
backend: confirmed in blueprint
mode: read
get_project_pages: # project -> pages with type and description
backend: confirmed in blueprint
mode: read
find_articles: # project, article number or device tag -> page references
backend: confirmed in blueprint
mode: read
get_parts_list: # project -> parts list with quantities
backend: Automation Interface documentation output, confirmed in blueprint
mode: read
export_documentation: # project -> PDF documentation set
backend: Automation Interface PDF creation, restored in version 7.4.1.16
mode: read
propose_article_change: # article, replacement number -> draft change the engineer confirms in ELECTRIX
backend: confirmed in blueprint
mode: propose
audit: every call logged with user, tool, arguments and the WSCAD responseThe manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.
One interface per row
01
an external configurator starts WSCAD in the background and the plans are generated; no format or protocol published. Documentation is not published. runs in silent mode, so ELECTRIX need not be open and no user need be present; needs the Project Wizard add-on to generate circuit diagrams, and is available with the Professional, Installation, BA Project and Ultimate products
02
scheduled one-way sync into the WSCAD parts database. Documentation is not published. compares product data in an ERP or PLM source against the WSCAD parts database at an adjustable interval and logs every access; parts data only, and it needs the User Rights add-on as a prerequisite
03
project check-in and check-out against PROCAD PRO.FILE. Documentation is not published. integrates document management and product data transfer with PRO.FILE; the one documented route out of WSCAD into a PLM system rather than into a parts database
04
vendor-specific export and import. Documentation is not published. Siemens TIA Portal, M-Print PRO and Clip Project Planning, added with SUITE X Service Pack 3; couplings for specific downstream tools, not a general API
WSCAD holds the records. An assistant without a governed way in answers from whatever someone pasted into the chat. The connector is the governed way in: named operations, the person's own permissions, every call logged.
When this is the wrong page
The dividing line is not how many people ask, it is where they ask. If everyone with a question has ELECTRIX open and a licence, the AI Copilot inside the product is the shorter path and this page is the wrong one. A connector is right when the people asking sit outside WSCAD, in Claude, ChatGPT or Copilot, in purchasing, service or project management, when every call has to be logged against a named person, or when WSCAD data only answers the question together with ERP or PLM.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your WSCAD owners and checks every backend against your release and licence. Week two tests whether a person's own WSCAD permissions reach through the connector. You keep the manifest and a costed build plan, whoever builds it. All prices are net and exclude VAT.
What we need from you: a named WSCAD administrator, a test or sandbox system we may call, and one business owner who can say which questions the assistant should answer first. The first production connector is usually a use-case pilot from €15,000; it runs in your environment, and the code is yours.
No. WSCAD ships no MCP server as of 29 October 2026: a site search on wscad.com for MCP and for Model Context Protocol returns nothing, and the release notes do not mention it. What WSCAD does ship is an AI Copilot inside ELECTRIX, which has answered questions and run instructions in the product since version 7.3.0.16 in November 2024 and can answer from uploaded PDF, TXT and DOCX files since February 2026. That assistant lives inside the product. A server that lets Claude, ChatGPT or Copilot read WSCAD data from outside has to be built against the Automation Interface, which is what this page describes.
The blueprint is a fixed €4,900 over two weeks: it settles which add-ons you hold, which objects the Automation Interface can actually read on your installation, and which tools survive that. The build is quoted after the blueprint, because WSCAD publishes no interface reference and a quote before the blueprint would be a guess dressed as a number.
Whether the Automation Interface reads project data back out, or only drives generation. WSCAD documents what each add-on does, but not its data model, and the public material describes generating complete plans from configurator data and producing documentation in silent mode. It does not document a query surface. The five read tools are therefore confirmed against your installation in the blueprint, not promised from a document.
Then you get that in writing, with what WSCAD answered, and the blueprint tests the two other documented routes before it stops. One is the documentation the Automation Interface produces in silent mode, which is an export rather than a query surface and answers fewer questions. The other is PRO.FILE PLM, the add-on that checks projects and documents out of WSCAD into PROCAD PRO.FILE. The tool manifest and the costed build plan are yours either way, whoever ends up building the server.
The Automation Interface add-on, which WSCAD states is available with the Professional, Installation, BA Project and Ultimate products, plus the Project Wizard add-on it needs to generate circuit diagrams, and a Windows host with a licensed ELECTRIX installation it can drive. User Rights decides what each person may run and has to be added to every licence at the site. PLM/ERPsync matters when parts data comes from ERP, and it needs User Rights as a prerequisite. WSCAD publishes this scope but no price, so week one settles the licence question with WSCAD before anything is built.
No, not for a named customer. What this page carries is the method and WSCAD's own constraints, dated and sourced, not a track record on this system. What exists is adjacent: permission-aware retrieval in manufacturing, where each person's own rights decide what an assistant may answer, described under /customers, and the MCP server work under /claude-anthropic/mcp-server-development. The blueprint exists because the WSCAD-specific part is unproven, and it is priced as two weeks rather than as a project for the same reason.
Only as a proposal. Five of the six tools read. The sixth drafts an article change that an engineer applies in ELECTRIX, because a wrong article propagates into panel build and wiring. Write access to schematics on an agent's own authority is not something this connector offers, and asking for it is a reason to stop and rethink the workflow.
No, and how that is enforced is the connector's job rather than a WSCAD feature. The Automation Interface carries the licence of the installation it drives, not a per-user token, so the server has to map the asking person's identity onto their own User Rights itself, and whether that mapping works on your installation is what the blueprint tests. Claude, ChatGPT and Copilot never hold WSCAD credentials. WSCAD applies the same principle to its own assistant: since version 7.4.1.7 in August 2026, a function locked by User Rights cannot be run through the AI Copilot either.
Next step
Thirty minutes with the engineer who would build the connector, with your WSCAD administrator in the room if you like.