What we build
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.