Claude Code
Add CADshift once at user scope, so it is there in every project.
Add it
PowerShell
claude mcp add --scope user cadshift-autocad -- "$env:LOCALAPPDATA\Programs\CADshift\AutoCAD MCP\server\cadshift-mcp-autocad.exe"
Command Prompt (cmd)
claude mcp add --scope user cadshift-autocad -- "%LOCALAPPDATA%\Programs\CADshift\AutoCAD MCP\server\cadshift-mcp-autocad.exe"
Everything after -- is the command Claude Code runs. The shell expands the path before Claude Code sees it, so the stored entry has your real path.
Or let CADshift do it: --register claude-code (one command). It edits the same file, %USERPROFILE%\.claude.json, and only when Claude Code has already been set up for your account.
What it writes
The entry goes in the top-level mcpServers of %USERPROFILE%\.claude.json:
{
"mcpServers": {
"cadshift-autocad": {
"type": "stdio",
"command": "C:\\Users\\YOUR-NAME\\AppData\\Local\\Programs\\CADshift\\AutoCAD MCP\\server\\cadshift-mcp-autocad.exe",
"args": [],
"env": {}
}
}
}
Use the command above rather than editing this file by hand: Claude Code keeps a lot of other state in it.
Check it
claude mcp list
cadshift-autocad should show as connected. Inside a session, /mcp shows its status and tools. Open AutoCAD with a drawing and ask: “Use CADshift to list the layers in the open drawing.”
Remove it
claude mcp remove cadshift-autocad --scope user
Official guide: Connect Claude Code to tools via MCP.