Ask Claude for an icon and you usually get detached SVG text you still have to paste, fix, and re-check by hand. Connect Claude to IconVectors over the local MCP bridge and Claude works inside the running editor instead: it inspects the live document, creates and edits geometry, runs document_analyzeCleanupSvg, renders previews, and exports code or files directly.
This guide covers both clients. Claude Desktop (Windows and macOS) installs a single .mcpb extension bundle; Claude Code (all platforms, and the only option on Linux) registers the same stdio bridge from the command line.
1 - Start IconVectors first
Launch the IconVectors build you want Claude to control before starting the Claude workflow. The MCP sidecar talks to the running editor on the local machine.
2 - Claude Desktop setup
Claude Desktop is available on Windows and macOS. On Linux, use Claude Code with the local stdio MCP server instead.
Claude Desktop now uses the supplied Axialis-IconVectors-Claude.mcpb extension bundle. On Windows the file ships beside IconVectors.exe in the application folder.
Windows
- Start
IconVectors.exe. - Open Claude Desktop.
- Go to Settings -> Extensions -> Advanced settings -> Install Extension....
- Select
C:\Program Files\Axialis\IconVectors\Axialis-IconVectors-Claude.mcpb. - Restart Claude Desktop.
macOS
Use the Axialis-IconVectors-Claude.mcpb bundle that ships with the application package, then install it through the same Claude Desktop extension dialog.
Linux
Claude Desktop is not available on Linux. Skip the extension flow and use the Claude Code setup below.
3 - Claude Code setup
Claude Code still uses the explicit MCP command-line registration flow. Configure the same bridge the desktop app uses.
Windows
claude mcp add --transport stdio --scope user iconvectors -- "C:\Program Files\Axialis\IconVectors\IconVectorsMcp.exe" --port 61337
macOS
claude mcp add --transport stdio --scope user iconvectors -- /Applications/IconVectors.app/Contents/MacOS/IconVectorsMcp --port 61337
Linux
claude mcp add --transport stdio --scope user iconvectors -- /usr/bin/IconVectorsMcp --port 61337
4 - Verify the connection
For Claude Desktop, verify the extension from Settings -> Extensions, Settings -> Developer, or inside a chat via + -> Connectors. Then run a short smoke test:
Use IconVectors to call app_ping.Use IconVectors to call app_getInfo.Use document_getSvg if Claude should keep the SVG content in its own workspace.Use document_analyzeCleanupSvg and report any cleanup issues in the current icon.
5 - Saving and export guidance
When Claude asks IconVectors on Windows to save or export files, give it a native Windows path such as C:\Users\Marc\Downloads\home-icon.svg. Do not use /mnt/user-data/... paths for the Windows desktop app. If Claude should only inspect or preview the result, prefer document_getSvg.
6 - Helper files
Use Help -> Open MCP Files Folder to open the installed helper bundle. Windows helper files are usually under %APPDATA%\Axialis\IconVectors\MCP. macOS helper files are usually under ~/Library/Application Support/Axialis/IconVectors/MCP. Linux helper files are usually under ~/.local/share/Axialis/IconVectors/MCP. The files most relevant to Claude are claude-implementation-instructions.md, iconvectors-mcp-command-reference.md, and claude-CLAUDE.md.template.
Related guides
- Using IconVectors with Codex CLI
- Using IconVectors with Cursor
- Using IconVectors with VS Code Copilot
Start Making SVG Icons Today with IconVectors
Download the fully-functional 30‑Day Free Trial and unlock your icon design workflow.
Version 1.70 for Windows, macOS, and Linux