Guide for the IT approval
What IT and data protection need to know before CadPilot is used on an engineering workstation: which data goes where, what stays local, how it is installed and which safeguards exist.
This guide does not replace a review by your IT, your data protection officer and the contract terms of your GitHub Copilot plan. All statements about CadPilot’s behaviour have been checked against the source code; the first test with a real CATIA installation is still pending.
1. The set-up in one sentence
GitHub Copilot in VS Code (a cloud service) plans the steps, CadPilot (a local Python process with user rights) carries them out through the Automation interface (COM) in the running CATIA V5 session.
| Component | Where it runs | Task |
|---|---|---|
| VS Code with GitHub Copilot | locally, the language model in GitHub/Microsoft data centres | understands the request, selects tools, writes the answer |
| CadPilot (MCP server) | locally, own Python process, user rights | provides 93 tools, checks calls, drives CATIA |
| CATIA V5 | locally | computes and saves as usual |
2. Which data leaves the computer
CadPilot itself opens no network connection; it only talks to VS Code via standard input and output. What goes to the Copilot service is sent by VS Code: the chat history including the tool results.
| Data | Sent to Copilot? | Examples |
|---|---|---|
| Your requests in the chat | yes | “Base plate 140 × 90 × 4 mm with four holes …” |
| Tool list and descriptions | yes | names, parameters, descriptions – no model data |
| Tool results | yes | document, feature and parameter names, parameter values, measured values (volume, mass, distances), part numbers and properties, bills of materials, file paths (e.g. open documents) |
| CAD files | no | CadPilot uploads no files; exports and screenshots are only saved in the working folder, only the file path is returned |
| Geometry as a whole | no | no meshes, surfaces or solid models are transferred – only the requested values |
Important: safe mode hides paths and values only in CadPilot’s log file. The tool results sent to Copilot still contain them – they are the purpose of the tool. For confidential projects, clarify in advance whether this information may go to the Copilot service.
3. What happens on the computer
- User rights: CadPilot runs as a normal user process started by VS Code. No services, no autostart entries, no administrator rights.
- Access to CATIA: only via the Automation interface of the running session of the same user. If CATIA is not running, CadPilot starts it on the first tool call (behaviour of the base project).
- Files: in safe mode (the set-up default) saving and export only go to the working folder
%USERPROFILE%\CATIA_MCP_Work, never over existing files; opening can be limited to approved folders. - Log:
catia_mcp.login the program folder; in safe mode without paths and values. The path can be changed withCATIA_MCP_LOG_FILE; empty disables the file. - Recording: recording all CATIA calls (for testing) is off by default. When switched on it contains model data; paths are anonymised by default.
4. Installation and origin of the software
- Python from python.org, installed in the user profile; plus a separate virtual environment for CadPilot.
- Packages from the Python Package Index (PyPI):
mcp(MIT),jsonschema(MIT),pywin32(PSF) and their dependencies. Themcppackage includes libraries for HTTP transports that CadPilot does not use. - Offline installation is possible: download the packages in advance and install from a local folder (guide in the project,
docs/ANLEITUNG_COPILOT.md, German). - It is based on the open-source project catia-v5-mcp-server (MIT); CadPilot is kept in a private repository. Every change goes through an automated check on Windows with all tests, strict type checking and a vulnerability scan of the dependencies (pip-audit); Dependabot reports new versions of the dependencies.
5. Safeguards
| Mechanism | Effect |
|---|---|
| Safe mode | Saving and export only in the working folder, no overwriting, opening only from approved folders, log without paths and values. A typo in the switch prevents the start instead of silently disabling protection. |
| Input validation | Every call is checked against the tool’s description before CATIA sees it. |
| Effect check | After material features the volume is measured again; a feature without effect counts as an error. |
| Journal and undo | Parameter changes and new features of the session can be listed and undone. |
| Time limit | If CATIA hangs, for example on a dialog, CadPilot reports it and sends no further commands. |
| Instructions to Copilot | Project rules forbid unreliable tools, estimated values and statements about strength or release. |
6. Recommendations for the approval
- Use a Copilot plan with business terms and check its rules on data use and retention.
- In organisations with Copilot Business or Enterprise the use of MCP servers can be controlled by policy – clarify whether it is enabled.
- Start with one pilot user and test models, no customer or project data.
- Keep safe mode switched on (default) and limit the read folders to the test models.
- Switch recording on only when needed and check the file before passing it on.
- Take updates only from the checked project state.
7. Status and open points
All statements above have been checked against the source code and in automated tests. The first test with a real CATIA installation is still open; tools listed as “limited” or “not reliable” in the handbook should be treated accordingly. Details on safe mode are in the handbook, chapter 4.