For engineering teams running SOLIDWORKS PDM Professional

A SOLIDWORKS PDM MCP server that reads vault files, data cards and where-used on the customer's own server

Pexon builds a SOLIDWORKS PDM connector so Claude, ChatGPT or Copilot can read files, data cards and where-used on the customer's own Professional vault. The 2026 installation guide says this Web API server is Professional only and defaults to HTTP port 65453. No Dassault MCP server for the vault was named on the pages opened on 21 November 2026.

SOLIDWORKS PDMbrowse_folderget_file_infoget_file_datacardAgentruns as theperson asking

What we build

A first SOLIDWORKS PDM tool list, written as the manifest your IT team signs

Built on what Dassault Systèmes documents: files, folders, file data cards, top-level file references, where-used parents, workflows. Backends named below are documented resources; "confirmed in blueprint" means the vendor documentation sits behind a login and the resource is checked against your release first.

# solidworks-pdm-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
  browse_folder:     # vault name, folder id -> files and folders in that folder
    backend: GET api/{vaultName}/folders/{folderId}/browse
    mode: read
  get_file_info:     # vault name, file id, version, folder id -> file information
    backend: GET api/{vaultName}/files/{fileId}/{version}/info?folderId={folderId}
    mode: read
  get_file_datacard: # vault name, file id, version, folder id -> data card
    backend: GET api/{vaultName}/files/{fileId}/{version}/datacard?folderId={folderId}
    mode: read
  get_references:    # vault name, file id, version, config id, folder id -> top-level references
    backend: GET api/{vaultName}/files/{fileId}/{version}/references?configId={configId}&folderId={folderId}
    mode: read
  get_where_used:    # vault name, file id, version, config id, folder id -> parent files
    backend: GET api/{vaultName}/files/{fileId}/{version}/whereused?configId={configId}&folderId={folderId}&anyVersion={anyVersion}
    mode: read
  list_workflows:    # vault name -> workflows in the vault
    backend: GET api/{vaultName}/workflows
    mode: read
audit: every call logged with user, tool, arguments and the SOLIDWORKS PDM response

The manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.

Checked 21 November 2026

SOLIDWORKS PDM at a glance: interfaces, access and what exists for AI

What we found
InterfacesSOLIDWORKS PDM Professional Web API (REST/JSON, docs public)
AuthenticationPOST api/{vaultName}/authenticate sends Username and Password. The Python sample on that page reads JwtString and sends Authorization: Bearer on the next call. The sample host is machine_name and a port the reader must set. The 2026 installation guide's default HTTP port is 65453. The connector calls the customer's server with the person who asked.
Vendor MCP serverNo vendor server. No SOLIDWORKS or Dassault page opened on 21 November 2026 names an MCP server for the PDM vault. A GitHub repository search that day for the name solidworks pdm mcp returned no repository. PDMShell and xLM Solutions ship their own servers. Those are not Dassault's.
Vendor AI assistantNone found.
Other connectorsBlue Byte's PDMShell and xLM Solutions both ship a SOLIDWORKS PDM MCP server, and neither is from Dassault; PDMShell can run modifying commands, while the xLM page says its server is read-only unless an administrator enables editing.

Dassault Systèmes (FR). Engineering teams that keep CAD models and other documents in one indexed vault on the company's server, with versions and workflows. The product page, read on 21 November 2026, describes SOLIDWORKS PDM that way. It describes PDM Professional as the edition for distributed teams, with browser access, email notifications, BOM support and multi-CAD. No installed-base count was on that page. The 2026 installation guide calls Dassault Systèmes a French société européenne and prints a Vélizy-Villacoublay address.

Why SOLIDWORKS PDM is hard for agents

Where a SOLIDWORKS PDM connection needs engineering, not configuration

01 · Edition

The Web API server is PDM Professional only

The 2026 installation guide says to install IIS 7 or higher, select SOLIDWORKS PDM Professional, then select Web API Server. The HTTP port may be any value from 0 to 65535. The default written there is 65453. PDM Standard is a different edition on the product page and does not get this server.

02 · Identity

The JWT is the person who asked

Authenticate posts Username and Password. The Python sample reads JwtString from the response and sends it as Authorization Bearer. That sample signs in as Admin with an empty password. The empty Admin login is a help placeholder. The connector uses the asking person's credentials against the customer's IIS host.

03 · Shape

The same read is written twice in the help

The overview lists many file reads twice, once with folderId in the path and once with folderId in the query. The tools use the query form for file info, the data card, references and where-used, and the path form for folder browse. The blueprint checks the help for the release that is installed before a path is kept.

04 · Writes

Checkout and check-in are on the same service

The overview documents checkout, undo checkout, check-in, delete, change state and saving a data card, next to the reads. Those operations stay off the manifest. GET download gets the file itself and is not a tool. A question that needs a write goes back to the person in PDM.

SOLIDWORKS PDM 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.

What the connector answers, and what it will not do

Questions it answers

  • Which files and folders are in this folder?
  • What does this file's data card say for this version?
  • Which parent files use this file?

What it will not do

  • Check out a file, undo a checkout, check a file in, delete a file or a folder, change a workflow state, or save a data card. Those operations are on the Web API overview and stay off the manifest.
  • Download the file bytes. The overview documents GET download and it is not a tool.
  • Read SOLIDWORKS PDM Standard through this server. The installation guide limits the Web API server to Professional.

When this is the wrong page

If the files are in Autodesk Vault, Teamcenter, Windchill or 3DEXPERIENCE, use that connector. If the task is driving the SOLIDWORKS desktop to build a part, that is a CAD-client server, not this vault. SOLIDWORKS PDM reads files, data cards and where-used on the customer's own PDM Professional Web API. Checkout, check-in and file download stay off this page. PDMShell and xLM ship their own MCP servers; neither is Dassault, and neither is this connector.

Start with the Readiness Blueprint.

Two weeks, €4,900 fixed price. Week one agrees the tool list with your SOLIDWORKS PDM owners and checks every backend against your release and licence. Week two tests whether a person's own SOLIDWORKS PDM 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 SOLIDWORKS PDM 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.

Sources: PDM Pro Web API overview · Getting Started · Authenticate · Installation Guide 2026 · SOLIDWORKS PDM product page · PDMShell MCP server · xLM SOLIDWORKS PDM MCP Server. Read 21 November 2026. Vendor documentation changes; verify against the current release.

Questions SOLIDWORKS PDM teams ask before the first tool call

Does SOLIDWORKS ship an MCP server for PDM?

Not one named on the product page, the Web API overview, Getting Started, the authenticate operation or the 2026 installation guide, all read on 21 November 2026. A GitHub search that day for a repository named solidworks pdm mcp returned none. PDMShell and xLM Solutions ship their own servers. Those are not Dassault's.

What can an assistant read from SOLIDWORKS PDM?

Files and folders in a folder, file information, the file data card, top-level references, where-used parents, and the workflows in the vault. Those are GET operations on the 2025 Web API overview read on 21 November 2026. Checkout, check-in, delete, state changes, data-card saves and file download stay off the manifest.

Whose permission does the SOLIDWORKS PDM connector use?

The customer's. Authenticate posts that person's Username and Password, and the help sample sends the returned JwtString as a Bearer token. The call goes to the customer's own IIS server. The help's Admin sample with an empty password is a placeholder, not the login this connector uses.

What does a SOLIDWORKS PDM connector cost?

The two-week Readiness Blueprint is fixed at €4,900: the tool list, the vault's Web API server, identity tested end to end, and a costed build plan. The production connector is usually a use-case pilot from €15,000. Prices are net, excluding VAT.

Not a sales call. An architecture call.

Thirty minutes with the engineer who would build the connector, with your SOLIDWORKS PDM administrator in the room if you like.

The connector catalogue lists this vault next to Autodesk Vault and Teamcenter. Vault is the other on-premises PDM. Teamcenter is the PLM when the released record lives there instead.