For IT departments
CADshift AI for AutoCAD lets an AI assistant (Claude Desktop, Claude Code, and Microsoft 365 Copilot or ChatGPT through the CADshift relay) work in AutoCAD 2025, 2026 and 2027. It is an AutoCAD plugin plus a local MCP server that the AI app starts. This guide is for the people who deploy and look after it. Nothing here needs an environment variable.
The same guide is in the policy templates zip, next to the Group Policy templates.
Downloads for IT
| Download | Link |
|---|---|
The installer (cadshift-autocad-mcp-X-Y-Z.exe) | cadshift.com/downloads/autocad-mcp/installer |
The MSI for deployment tools (cadshift-autocad-mcp-X-Y-Z.msi) | cadshift.com/downloads/autocad-mcp/msi |
| The Group Policy templates (ADMX) and this guide | cadshift-autocad-mcp-policy-templates.zip |
| The Microsoft 365 Copilot agent package | cadshift.com/downloads/autocad-mcp/copilot |
| The release manifest (version, SHA-256 of each file) | cadshift-autocad-mcp-latest.json |
Sign in first
Download the MSI once, signed in, and check it:
Get-AuthenticodeSignature .\cadshift-autocad-mcp-X-Y-Z.msi # Status Valid, signer CN=CADSHIFT PTY LTD
(Get-FileHash .\cadshift-autocad-mcp-X-Y-Z.msi -Algorithm SHA256).Hash # the manifest's msi.sha256
Then put it in Intune, Configuration Manager or a Group Policy software installation from your own share, the same as
any other MSI. The release manifest needs no sign-in, so a script can watch it for a new version, but each new MSI is
downloaded by a person.
What gets installed, and where
The installer is per user: it installs for the Windows account that runs it and never needs administrator rights. It
comes two ways, with the same content: cadshift-autocad-mcp-X-Y-Z.exe (the window users see, with the CADshift look of
the SOLIDWORKS and Inventor installers) and cadshift-autocad-mcp-X-Y-Z.msi (the per-user MSI inside it, for
deployment tools). Both take the same properties (below).
| What | Where |
|---|---|
| AutoCAD plugin (bundle) | %APPDATA%\Autodesk\ApplicationPlugins\CadshiftMcp.bundle (an AutoCAD trusted location: no SECURELOAD prompt) |
| MCP server, calculation engine and worker, bundled standards and data sources | %LOCALAPPDATA%\Programs\CADshift\AutoCAD MCP\server |
Setup helper (cadshift-autocad-setup.exe, the installer’s; cadshift-autocad-setup-cli.exe, its console twin for command lines and scripts: --register / --unregister / --list-clients / --configure) and install.json | %LOCALAPPDATA%\Programs\CADshift\AutoCAD MCP |
| Installed apps entry | the installer’s (CADshift AI for AutoCAD, publisher CADshift Pty Ltd, with Modify); an MSI deployed on its own has its own entry |
| What the installer remembers (the profile, which AI apps are connected) | HKCU\Software\CADshift\AutoCAD MCP\Setup |
| AI app entries | one cadshift-autocad server in each connected AI app’s MCP config (below); the file is backed up first (.cadshift-backup, and .cadshift-original from before CADshift first touched it) |
Requirements: AutoCAD 2025, 2026 or 2027 (it brings the .NET desktop runtime the installer and server run on), Windows 10 or 11, x64. Without the .NET 8 Desktop Runtime (x64) the installer refuses to install and says so; an uninstall then still removes the files but cannot release the licence seat or take the AI app entries out.
Silent install, upgrade, uninstall
Run the installer as the user (in their session), not as SYSTEM or another administrator: it installs into the profile of whoever runs it. In Intune that is a Win32 app with Install behavior: User; in Configuration Manager, Run with user’s rights; in a logon script, as the user.
rem Install or upgrade, no window. Connects the AI apps found for this user, and sets the company's shared folders.
rem (X-Y-Z is the version with dashes; property names are upper case)
cadshift-autocad-mcp-X-Y-Z.exe /quiet /norestart REGISTER=detected ^
SHARED_SOURCES=\\fileserver\cad\cadshift\data-sources ^
SHARED_STANDARDS=\\fileserver\cad\cadshift\standards
rem The same with the MSI (deployment tools that want an MSI)
msiexec /i cadshift-autocad-mcp-X-Y-Z.msi /qn REGISTER=detected SHARED_SOURCES=\\fileserver\cad\cadshift\data-sources
rem Change which AI apps are connected later (what Installed apps, Modify, Apply does)
cadshift-autocad-mcp-X-Y-Z.exe /repair /quiet REGISTER=claude-code UNREGISTER=claude-desktop
rem Uninstall (also what Installed apps runs): the exe with /uninstall /quiet, or for the MSI
msiexec /x cadshift-autocad-mcp-X-Y-Z.msi /qn
- A quiet install connects no AI app unless
REGISTERsays so, as before. The window instead shows the step Connect your assistant: each AI app with whether it was found on the PC, the ones found ticked. - Install, repair and uninstall need AutoCAD closed. While any AutoCAD (
acad.exe) runs for the user, the window asks to close it and retry; a quiet run fails (exit code 1603) and changes nothing: run it again once AutoCAD is closed (at logon, for example). The same when another program holds the plugin’s or the server’s files. An AI app running the server is stopped (it starts the server again when restarted). AI app entries are left as they are on upgrade and repair; settings, sign-ins and licence are kept. - Claude Desktop should be closed when the installer connects it (
REGISTER=claude-desktopordetected): Claude Desktop rewrites its settings file when it exits, and an instance that was open during the install can drop thecadshift-autocadentry.setup.logsays so when it finds Claude Desktop open; install at logon, or runcadshift-autocad-setup-cli.exe --register claude-desktopagain afterwards. - Uninstall releases the licence seat: once the uninstall has gone through (a failed or cancelled uninstall leaves
the product, the licence and the AI app entries as they were), it asks the licence server to release this computer’s
seat (so the licence can be used on another computer), then deletes
license.lic. Offline, or when the licence server refuses, the uninstall still completes and says the seat could not be released (in a message, and insetup.log); release it at cadshift.com then. Upgrades and repairs never release it. - Uninstall removes the plugin, the server, the Installed apps entry and the
cadshift-autocadentries (only where they still run the server this installer put there). It keeps the user’s settings, sign-ins and logs (below), and the installer settings keyHKCU\Software\CADshift\AutoCAD MCP; delete those for a clean slate. - Upgrading from 0.1 (the first preview’s setup): the installer replaces it in place (same folders), removes its
Installed apps entry (
CADshift.McpAutoCAD), and keeps its AI app entries. - Detection rule (Intune, ConfigMgr): the MSI’s product (upgrade code
{66E6372C-660C-4848-A3B2-1A728BB9E857}), or the file%LOCALAPPDATA%\Programs\CADshift\AutoCAD MCP\server\cadshift-mcp-autocad.exe. - The first AutoCAD start after a fresh install may only register the plugin; the CADshift ribbon tab appears from the next start.
Exit codes are the Windows Installer’s: 0 done, 3010 done but restart needed, 1602 cancelled, 1603 failed (a wrong
property value, AutoCAD open, files in use: the window and setup.log say which;
nothing is installed).
AI apps the installer connects
The installer finds these on the PC and lists only those found. An app is found only when the app itself is installed for
the user or for all users: its program where its installer puts it (per user under %LOCALAPPDATA%\Programs, or under
Program Files), its entry in Installed apps (HKCU or HKLM, 64- and 32-bit), its Microsoft Store package, or for a
command-line tool its command on PATH (not a Store app’s alias). A config folder alone never counts: uninstallers leave
them behind. Apps whose config folder is created by their first start (Claude Code’s .claude.json, Cursor, Windsurf /
Devin, LM Studio, AnythingLLM) are found only once they have been started for the user, so the installer never creates
their folders. It only reads; it never starts an app. setup.log says where each app it connected is installed.
Each entry is one stdio server, cadshift-autocad, running
%LOCALAPPDATA%\Programs\CADshift\AutoCAD MCP\server\cadshift-mcp-autocad.exe. Every other server and setting in the
file is kept, comments too (VS Code reads its file as JSONC), and a file that is not valid JSON is never rewritten.
| Id | App | Installed when | and started when this exists | MCP config it edits | Shape |
|---|---|---|---|---|---|
claude-desktop | Claude Desktop | %LOCALAPPDATA%\AnthropicClaude\claude.exe or its Installed apps key AnthropicClaude (classic install), or its Microsoft Store package Claude_pzs8sxrjxfjjc | (not needed) | %APPDATA%\Claude\claude_desktop_config.json (and the Store package’s copy) | mcpServers: command, args |
claude-code | Claude Code | %USERPROFILE%\.local\bin\claude.exe, npm’s claude.cmd, WinGet’s link, an Installed apps entry Claude Code, or claude on PATH | %USERPROFILE%\.claude.json | the same file (user scope, as claude mcp add --scope user) | mcpServers: type stdio, command, args, env |
cursor | Cursor | Cursor.exe in %LOCALAPPDATA%\Programs\cursor or Program Files\cursor, an Installed apps entry Cursor, or cursor on PATH | %USERPROFILE%\.cursor | %USERPROFILE%\.cursor\mcp.json (comments allowed, kept) | mcpServers: type stdio, command, args |
vscode | VS Code or VS Code Insiders (GitHub Copilot Chat, agent mode) | Code.exe (Code - Insiders.exe) in %LOCALAPPDATA%\Programs\Microsoft VS Code or Program Files\Microsoft VS Code (Insiders: ... Insiders), or an Installed apps entry Microsoft Visual Studio Code | (not needed) | %USERPROFILE%\.copilot\mcp-config.json (%COPILOT_HOME%\mcp-config.json when that is set; VS Code checks only one), which VS Code reads through its GitHub Copilot CLI discovery source (on by default; the chat.mcp.discovery.enabled setting); its profile mcp.json is not written (both would list CADshift twice). GitHub Copilot CLI reads the same file | mcpServers: type stdio, command, args (the fields VS Code documents; Copilot CLI takes stdio as its local type, every tool allowed by default) |
windsurf | Windsurf, now Devin Desktop | Windsurf.exe or Devin.exe in %LOCALAPPDATA%\Programs\Windsurf (...\Devin) or Program Files, an Installed apps entry Windsurf or Devin, or windsurf on PATH | %APPDATA%\devin (Devin’s user MCP file since Local 3.6, read by its Local agent and the legacy Cascade agent), or %USERPROFILE%\.codeium\windsurf (Windsurf before the rename, docs.windsurf.com) | mcp_config.json in that folder (comments allowed, kept) | mcpServers: command, args, disabledTools (23 specialised tools: the Cascade agent reaches at most 100 tools over all servers and CADshift has 113, so 90 stay on; any can be switched back on in its MCP panel) |
lm-studio | LM Studio (0.3.17 or later) | LM Studio.exe in %LOCALAPPDATA%\Programs\LM Studio or Program Files, or an Installed apps entry LM Studio | %USERPROFILE%\.lmstudio | %USERPROFILE%\.lmstudio\mcp.json | mcpServers: command, args |
anythingllm | AnythingLLM Desktop | AnythingLLM.exe in %LOCALAPPDATA%\Programs\AnythingLLM or Program Files, or an Installed apps entry AnythingLLM | %APPDATA%\anythingllm-desktop\storage (its documented Windows storage folder) | ...\storage\plugins\anythingllm_mcp_servers.json | mcpServers: command, args (its stdio shape; no type) |
The installer window asks the setup helper which apps are found (the same check as --list-clients and
REGISTER=detected), so the window, a quiet install and the command line always agree. An app that is not found, or not
yet started for the user, is never given a new file or folder, Claude Desktop included; --register then says so and
what to run once it is. An app installed where the installer does not look (a portable or custom-folder install without an
Installed apps entry) is connected with cadshift-autocad-setup-cli.exe --register <app> --force, which skips the install
check (the app must have been started once); the “not found” message says so.
An upgrade from 0.1.0, which also counted leftover config folders, disconnects the apps 0.1.0 connected that are not
installed: only CADshift’s entry is taken out of the file, everything else in it stays, and the app is recorded as not
connected. The default %USERPROFILE%\.copilot folder is removed only when it holds nothing but what CADshift wrote; in a
%COPILOT_HOME% folder only CADshift’s own mcp-config.json goes. No other run (a repair, a later upgrade, --register,
--unregister) ever disconnects an app because it was not found. A GitHub Copilot CLI user without VS Code who was
connected by 0.1.0 loses that connection on the upgrade; --register vscode --force puts it back.
Not found yet: Windsurf Next (the preview build, in its own folder) and VS Code Insiders installed with Scoop
(vscode-insiders). For the latter, --register vscode --force; Windsurf Next keeps its own config folder, which the
installer does not write, so add CADshift in its MCP settings. Jan is not
listed: its documentation describes MCP servers only in its own window (Settings, MCP Servers), with no config file to edit safely. On a PC, cadshift-autocad-setup-cli.exe --list-clients prints each id, whether
the app was found, whether it is connected, and its config file.
Microsoft 365 Copilot is not a file on the PC: it reaches AutoCAD through the CADshift relay. The installer’s window
offers Use with Microsoft 365 Copilot (off by default, never in a quiet run); ticked, its Success page has
Sign in now, the same browser sign-in as AutoCAD’s CADSHIFTSIGNIN. The tenant’s IT adds the CADshift app in the Teams
admin center (For IT: add CADshift to Microsoft 365 Copilot). The option is hidden when Group Policy turns the relay off (Relay, below); RELAY=off turns it off at
install for this account. There is no separate property: signing in needs the user.
ChatGPT reaches AutoCAD through the same relay and the same AutoCAD sign-in. The workspace admin adds CADshift once in ChatGPT (For IT: add CADshift to ChatGPT); nothing more is installed on the PC.
Installer properties
| Property | Values | Setting it writes |
|---|---|---|
REGISTER | AI app ids (comma-separated: claude-desktop, claude-code, cursor, vscode, windsurf, lm-studio, anythingllm), detected, all, none | which AI apps to connect (nothing unless asked) |
UNREGISTER | as above | disconnect AI apps (with /repair) |
SHARED_SOURCES | a full folder path, or none | SharedDataSourcesFolder |
GIS_SERVER | the server’s web address (https://…), or none | CompanyGisServer |
SHARED_STANDARDS | a full folder path, or none | SharedStandardsFolder |
UPDATE_CHECK | on, off | UpdateCheck |
UPDATE_URL | an https URL | UpdateManifestUrl |
LIVE_UPDATE | on, off | LiveUpdate |
FEEDBACK | on, off | Feedback |
RELAY | on, off | Relay |
Any setting takes default to remove the installer’s value. The properties write HKCU\Software\CADshift\AutoCAD MCP
(this Windows account). Settings for every user of the PC (HKLM\Software\CADshift\AutoCAD MCP) have no property: a
per-user installer run elevated would install into the administrator’s profile, so they are the setup helper’s
elevated --configure --all-users (below). A value may end with \ (the installer keeps every value whole); it cannot contain a double quote ("),
which stops the install with nothing changed. cadshift-autocad-mcp-X-Y-Z.exe /help lists them.
A common pattern: one elevated run per PC sets the company defaults for everyone, and the per-user install needs no settings. The setup helper does that without installing anything (it is in the policy templates zip, and installed with the product):
rem Elevated, once per PC (or push the same values by Group Policy, below)
cadshift-autocad-setup-cli.exe --configure --all-users --shared-standards "\\fileserver\cad\cadshift\standards" --update-check off
rem After an install, as the user: connect or disconnect AI apps, or list the helper's options
"%LOCALAPPDATA%\Programs\CADshift\AutoCAD MCP\cadshift-autocad-setup-cli.exe" --register claude-desktop
"%LOCALAPPDATA%\Programs\CADshift\AutoCAD MCP\cadshift-autocad-setup-cli.exe" --list-clients
"%LOCALAPPDATA%\Programs\CADshift\AutoCAD MCP\cadshift-autocad-setup-cli.exe" --help
cadshift-autocad-setup-cli.exe is the console twin of the installer’s helper: the same options, every run quiet, and
cmd or PowerShell wait for it, so its output and exit code are the command’s (--list-clients exits 1 when an app could
not be checked). cadshift-autocad-setup.exe is a Windows program for the installer: a prompt does not wait for it.
The helper’s exit codes: 0 done, 1 failed, 2 a program holds the files (close AutoCAD and run again), 4 wrong arguments, 5 --all-users without administrator rights; --relay-sign-in (the relay sign-in for Microsoft 365 Copilot and ChatGPT) also 6 the relay is turned off, 7 the sign-in did not complete.
Settings and where they come from
Each setting is resolved through these layers; the first that has a value wins:
- Group Policy (or Intune):
HKLM\Software\Policies\CADshift\AutoCAD MCP, thenHKCU\Software\Policies\CADshift\AutoCAD MCP. Shown locked in AutoCAD: the user cannot change it. - Installer:
HKLM\Software\CADshift\AutoCAD MCP(--configure --all-users), thenHKCU\Software\CADshift\AutoCAD MCP. - The user’s own choice in AutoCAD’s windows and commands (
%APPDATA%\CADshift\autocad-mcp\settings.json). - The built-in default.
There is no other layer on a customer PC: environment variables are never read (CADshift’s developer switches work only on its own developers’ PCs, with their test token). What sticks:
- Group Policy is enforced: the user cannot change it, and AutoCAD shows it locked.
- Installer settings come before the user’s choice: AutoCAD’s windows and commands cannot change them (the windows show
them as set by IT). Written with
--all-usersthey are in HKLM, which users cannot edit. Written per user (HKCU) they are in a key the user owns, so a user who edits their own registry can remove them: use Group Policy (or--all-users) for what must be enforced.
Settings are read when they are used, so a gpupdate applies without restarting AutoCAD (the update check reads its
setting once per AutoCAD start).
| Setting (registry value) | Type | Default |
|---|---|---|
SharedDataSourcesFolder | REG_SZ / REG_EXPAND_SZ | none |
What it does: The company’s shared data sources (web GIS services: cadastre, contours, utilities). The AI reads them and never changes them; curators change them in the Data sources window. none: no shared folder, and users cannot choose one | ||
CompanyGisServer | REG_SZ (a web address) | none |
What it does: The company’s own GIS server: an ArcGIS REST services directory (https://gis.example.com/arcgis/rest/services), an ArcGIS Enterprise or ArcGIS Online portal (https://gis.example.com/portal, https://example.maps.arcgis.com), one ArcGIS service, an OGC API - Features endpoint or a WFS. The server lists its layers, works out what each holds (roads, buildings, water, rail, elevation, imagery, cadastre) and where, keeps that list for a day, and uses matching layers as company sources: after the user’s own sources, before the built-in regional ones. A server that needs a sign-in is read with the user’s saved GIS sign-in (CADshift ribbon, GIS sign-in). Users can also enter one in the Data sources window; servers can be listed in the shared data sources folder too (a JSON file with {"gisServer": "https://…"}). none: no company server, and users cannot enter one | ||
SharedStandardsFolder | REG_SZ / REG_EXPAND_SZ | none |
| What it does: The company’s shared drafting standards. Same rules, in the Standards window | ||
UpdateCheck | REG_DWORD 1/0 | 1 |
| What it does: Once a day the plugin reads the release manifest and tells the user when a newer version exists. It never downloads or installs. Turn it off when IT rolls out updates | ||
UpdateManifestUrl | REG_SZ (https) | https://cadshift.com/downloads/autocad-mcp/cadshift-autocad-mcp-latest.json |
What it does: Where the update check looks: point it at an internal copy that you advance once you have tested a release. Only https is read. The notice shows the manifest’s download link when it is on cadshift.com, or, for another host, only when the address was set by Group Policy or --all-users (so a per-user value cannot send users to another site); otherwise it shows the product page | ||
LiveUpdate | REG_DWORD 1/0 | 1 |
| What it does: After a user edits by hand what a CADshift item was built from, the plugin starts the server briefly to redraw the item. Off: items are only marked OUT OF DATE | ||
Feedback | REG_DWORD 1/0 | 1 |
What it does: Product feedback (what the tools could not do, failed calls) to https://cadshift.com/api/mcp-feedback. It holds the users’ requests in their words; never drawings, files or passwords | ||
OverpassEndpoints | REG_SZ (https addresses, comma-separated, or none) | none set: overpass-api.de, then overpass.private.coffee |
What it does: The Overpass servers the AI asks for OpenStreetMap context when no better source covers a site. The request carries the site’s bounding box. Set your own instance to keep site extents on your network, or none (or an empty value, which counts as none, not as “not configured”) to turn OpenStreetMap context off (the AI is told, and uses company or regional sources). Policy only; users cannot change it. The answer to a context fetch names the server that served it. Addresses that are not https are ignored, and a list with none usable blocks the fetch rather than falling back to the public servers | ||
Relay | REG_DWORD 1/0 | 1 |
What it does: Lets a signed-in user reach their AutoCAD from Microsoft 365 Copilot or ChatGPT through the CADshift relay (an outgoing connection to cadshift.com) | ||
RegisterClients | REG_SZ: none, detected, all, or AI app ids (comma-separated) | (what REGISTER says) |
What it does: Policy only, read by the installer: which AI apps it connects. Overrides REGISTER and the Connect your assistant boxes | ||
Group Policy templates (ADMX)
From the policy templates zip copy CADshift.admx and CADshiftAutoCadMcp.admx to C:\Windows\PolicyDefinitions (or
the domain’s Central Store, \\<domain>\SYSVOL\<domain>\Policies\PolicyDefinitions) and en-US\*.adml to its en-US
folder. The policies are under Computer Configuration and User Configuration, Administrative Templates,
CADshift, AutoCAD MCP. Computer policy wins over user policy. CADshift.admx holds only the shared CADshift
folder that every CADshift product’s template uses; keep one copy.
Intune: Devices, Configuration, Create, Templates, Imported Administrative templates: import CADshift.admx
first, then CADshiftAutoCadMcp.admx (each with its ADML). Or set the registry values above with a remediation script;
the product reads the keys, however they were written.
Shared folders for standards and data sources
The company’s standards and data sources are JSON files in a shared folder, one file per standard or source. Every
user’s AI reads them; the AI can never change or delete them (one person’s AI must not change them for the whole
office). The people who look after them change them in AutoCAD: Data sources (CADSHIFTSOURCES) and Standards
(CADSHIFTSTANDARDS) on the CADshift ribbon. Each change made there is appended to cadshift-changes.log in the folder
(when, DOMAIN\user on PC, what, which item). Users keep their own private additions in their own folder
(%APPDATA%\CADshift\autocad-mcp\standards and \data-sources), which can shadow a company entry for them only.
Suggested NTFS permissions on, for example, \\fileserver\cad\cadshift\standards:
| Who | Permission | Why |
|---|---|---|
| CAD users (a group) | Read & execute, List folder contents, Read | The AI reads the company list |
| Curators (CAD managers) | Modify | They change it in AutoCAD’s windows; their edits are logged |
| Administrators, SYSTEM | Full control |
NTFS permissions are the only lock. A user without write access sees the shared list as read-only in the window
(with the reason); nothing fails. The folder’s Read-only attribute is not a lock (Windows ignores it on folders, and
Explorer sets it on any folder with a custom icon), so CADshift does not look at it. Curators need Create files / write
data to save; Delete only to remove or rename entries. For a change log nobody can rewrite, give curators Modify on
the JSON files but only Append data (no delete) on cadshift-changes.log, or turn on file auditing. Back the folder up
like any other company data.
When the shared folder cannot be reached (a laptop off the VPN, the server down), the AI keeps reading what it can (the built-in list and the user’s own), the windows say the company’s folder cannot be reached, and the AI refuses to add data sources or save standards until it can be: a check against the company’s list cannot be made, and an entry saved then would later hide the company’s one. A folder that does not exist is reported, never created by a read; a curator’s first save in the window creates it.
Upgrading from the first previews: if a user had chosen a shared folder in the Data sources window, that same folder
is now the company’s list, read-only to the AI: sources their AI added there are company sources from now on, changed
in the window. migration.log says so when it finds such a choice.
Network endpoints
All connections are outgoing HTTPS (443). Nothing listens on the network: the plugin and the server talk over a named pipe private to the Windows user.
| Endpoint | Used for | When |
|---|---|---|
license-management.com | the CADshift licence (trial start, activation, refresh every few hours) | always; the first run must be online once |
cadshift.com/downloads/autocad-mcp/ | the update check’s release manifest, and the installer download | daily unless UpdateCheck is off or UpdateManifestUrl points elsewhere |
cadshift.com/api/mcp-feedback | product feedback | unless Feedback is off |
cadshift.com (GeoConvert API) | converting GIS files (shapefiles, KML, GeoPackage) with the user’s own GeoConvert key | when a user imports such a file |
cadshift.com/mcp (relay) | Microsoft 365 Copilot, ChatGPT and other remote AI clients | only for users who signed in, unless Relay is off |
copernicus-dem-30m.s3.amazonaws.com, elevation.nationalmap.gov | terrain | when the AI fetches terrain |
overpass-api.de, overpass.private.coffee (Overpass; replaced by your own with OverpassEndpoints), nominatim.openstreetmap.org | OpenStreetMap context and address search | when the AI fetches context or looks up an address |
hdsc.nws.noaa.gov | NOAA Atlas 14 rainfall frequency (precipitation intensities for a return period in the United States) | when a stormwater analysis or sizing is given returnPeriod |
| the data sources’ own servers | web GIS data (government cadastre, contours, utilities…) | the built-in list (server\data-sources\*.json in the install folder), the company’s shared list, and any the users add |
| the AI app’s own service (Anthropic for Claude) | the conversation | the AI app, not CADshift |
The licence check uses the system proxy (WPAD, PAC or Internet Options). When a proxy answers 407 with Negotiate or NTLM,
it retries once with the signed-in user’s Windows credentials. Allow license-management.com through the proxy, DNS
filter and any HTTPS inspection: when it cannot be reached, the licence message says which of these stopped it.
What is stored per user
| Where | What |
|---|---|
%APPDATA%\CADshift\autocad-mcp (roams) | settings.json (the user’s own choices), standards\ and data-sources\ (their own), templates.json, geoconvert.key and gis-sign-ins.dat and relay.token (encrypted for the Windows user with DPAPI), license.lic (the signed licence) |
%LOCALAPPDATA%\CADshift\autocad-mcp (this PC) | plugin.log, setup.log, migration.log, server.path, update-check.json, feedback\queue.jsonl |
%LOCALAPPDATA%\CADshift\terrain-cache | downloaded terrain tiles (public data, kept under 512 MB; shared with other CADshift products) |
%TEMP%\cadshift-mcp | temporary meshes and conversions, deleted after use |
Early builds (0.1.0 previews) used CADshift\mcp instead of CADshift\autocad-mcp. The installer moves it when it
installs (AutoCAD must be closed), and the installed plugin finishes anything that was in use then: a file only in the old
folder is moved; when both have it the new one is kept and the old copy goes to CADshift\mcp.kept-by-migration;
settings.json is merged (the newer values win). The licence and sign-ins (license.lic, relay.token,
geoconvert.key, gis-sign-ins.dat) are copied, not moved, so an older copy of CADshift still running is not signed out;
the next release removes the old folder. Nothing is deleted. Each step is written to migration.log. The MCP server never
migrates, and neither do CADshift’s own developer builds and test runs.
The plugin starts the MCP server itself (live updates, the Copilot and ChatGPT relay, its windows) only from the installed folder
%LOCALAPPDATA%\Programs\CADshift\AutoCAD MCP\server, and, for a signed release, only an exe validly signed by the same
publisher as the plugin; server.path naming anything else is ignored and logged in plugin.log.
CADshift’s own developers and automated tests use a test token (never shipped; the product holds only its hash). With it, a process reads developer switches, may run with licensing off, and starts a server from any location. It is a CADshift secret, not something a customer receives: if it ever reaches a customer PC, treat it as leaked. CADshift rotates it (a new hash in a release) whenever it may have left its developers and CI, and at least with every major release.
Logs
%LOCALAPPDATA%\CADshift\autocad-mcp\setup.log: every install, upgrade, change and uninstall (what was checked, the AI apps, the licence release). The Windows Installer log:/log <file>on the exe,/l*v <file>with msiexec.%LOCALAPPDATA%\CADshift\autocad-mcp\plugin.log: the plugin’s start, its pipe, live updates, the update check (last ~200 KB).- The MCP server logs to the AI app’s MCP log (Claude Desktop:
%APPDATA%\Claude\logs\mcp-server-cadshift-autocad.log).
Checking a PC
In AutoCAD type CADSHIFT (or Status on the CADshift ribbon). The window shows whether an AI is connected, the
plugin and server versions, and every setting above with its value and where it came from: Policy (locked),
Installer, You (the user’s choice) or Default. Copy details puts the same as text on the clipboard for a
ticket; Open log folder opens the logs.
From a command prompt: reg query "HKLM\Software\Policies\CADshift\AutoCAD MCP", the same under HKCU, and
reg query "HKCU\Software\CADshift\AutoCAD MCP" show what policy and the installer set.
What to tell your users
- CADshift is on the CADshift tab of the AutoCAD ribbon. Open your AI app (for example Claude Desktop) and ask it about
the open drawing. Type
CADSHIFTin AutoCAD to see whether the AI is connected. - The first time the AI uses a CADshift tool, Claude asks for permission: choose Always allow.
- Every change the AI makes is one undo step:
Uundoes it. - The company’s standards and data sources are shared and the AI cannot change them. Ask your CAD manager to change one, or keep a private version in your own list.
- Passwords and keys (GIS sign-ins, the GeoConvert key) go in AutoCAD’s windows, never in the chat.
- Settings marked Policy in the status window are set by IT.
- Previous
- CADshift (status, account, licence)
- Next
- Troubleshooting