Using IconVectors with Claude / Anthropic

Overview

IconVectors 2.00 for Windows works with Claude Desktop and Claude Code through a local stdio MCP server. Claude launches the supplied sidecar, which forwards calls over loopback to the running IconVectors desktop application.

Claude can inspect and edit the active document, work with Icon Explorer, render and export results, and use the Explorer Batch Starter operations. See MCP Integration for behavior shared by all supported clients.

Prerequisites

  • Start IconVectors 2.00 normally and leave it running.

  • Confirm IconVectorsMcp.exe exists beside the application.

  • For Claude Desktop, confirm Axialis-IconVectors-Claude.mcpb is in the installation folder.

  • The default bridge is 127.0.0.1:61337. Match a custom Options/McpPort value when necessary.

Configure Claude Desktop

The shipped .mcpb extension is the preferred setup:

  1. Open Settings ‣ Extensions ‣ Advanced settings ‣ Install Extension.

  2. Select C:\Program Files\Axialis\IconVectors\Axialis-IconVectors-Claude.mcpb.

  3. Check the extension and server in Settings, then approve it when prompted.

The path above is the normal installed-product example. Do not select IconVectorsMcp.exe in the extension installer. Manual Claude Desktop MCP configuration remains a client feature, but the supplied bundle avoids a second configuration recipe. Reinstall the current bundle after an IconVectors update when its packaged server metadata changes. Restart Claude Desktop only when troubleshooting requires it.

Configure Claude Code

Add a user-scoped stdio server from PowerShell:

claude mcp add --transport stdio --scope user iconvectors -- "C:\Program Files\Axialis\IconVectors\IconVectorsMcp.exe" --port 61337
claude mcp list

Options precede the server name; -- separates the sidecar command. Replace the path or port when needed.

Claude Code stores user-scoped servers in ~/.claude.json. A shared project server uses .mcp.json. Review project configuration before approving it. In a session, /mcp shows status and project-server trust choices; claude mcp reset-project-choices clears saved project approvals.

Verify the connection

For Claude Desktop, check the extension/server in Settings. For Claude Code, use claude mcp list and /mcp. Then call:

  • app_ping

  • app_getInfo

  • app_getCapabilities

  • app_get_workspace

Inspect the current Editor document and selection or the current Explorer folder before asking Claude to make a change.

Install instructions and the IconVectors skill

Copy claude-CLAUDE.md.template to CLAUDE.md or .claude/CLAUDE.md in a project. User instructions can live at ~/.claude/CLAUDE.md. If a repository already maintains shared instructions, CLAUDE.md can import them with @AGENTS.md.

Install the complete distributed iconvectors-mcp skill, including its references directory, at either:

  • project: .claude/skills/iconvectors-mcp/SKILL.md

  • user: ~/.claude/skills/iconvectors-mcp/SKILL.md

Keep CLAUDE.md concise. Do not paste the complete tool catalog into it.

First workflow

Try an inspected, bounded edit:

  1. Ask Claude to inspect document_getInfo and selection_get.

  2. Create one simple shape or change one selected element.

  3. Reinspect the element, selection, and document.

  4. Save or export only to a native Windows destination that you explicitly requested.

For related active-document edits, use one history transaction and its exact returned txId. Save/export, replacement, and Explorer filesystem changes are not covered by document Undo.

Working with 155 tools

Claude is naming-compatible with 155/155 production IconVectors tools. Use the canonical underscore names; no Claude-specific rename is required.

Claude Code uses Tool Search for large MCP catalogs and publishes no fixed per-server count ceiling, so IconVectors needs no server-side Claude profile. Task-focused client selection can still reduce ambiguity. Prefer bounded queries and minified SVG: Claude Code warns for MCP output above 10,000 tokens, uses a default maximum of 25,000 tokens, and can adjust that maximum with MAX_MCP_OUTPUT_TOKENS.

Approval and safety

Project servers require approval. A permission pattern such as mcp__iconvectors__* can cover the server, but broad auto-approval is not appropriate for Save As, export, document replacement, Explorer file changes, or batch apply. Start with prompts and inspect, mutate, then verify.

When Claude should keep SVG content in its own environment, request document_getSvg and let the client handle the returned text. When IconVectors writes a file, use a native Windows path such as C:\Users\name\Downloads\icon.svg. A Claude sandbox path such as /mnt/user-data/... is not visible to the desktop application.

Troubleshooting

Claude Desktop server is missing

Confirm the .mcpb is installed and enabled, then inspect Extensions or Developer settings. Reinstall the current bundle and restart only if needed.

Claude Code server is missing

Run claude mcp list and use /mcp. Check scope, command path, and project trust.

Connection is refused or times out

Start IconVectors, match the port, and check that another application instance did not claim it. MCP_TIMEOUT controls Claude Code server startup; the IconVectors sidecar separately uses a 10-second application- bridge I/O timeout.

Wrong document, workspace, or selection

Inspect state again. Do not force a replacement, invent a selection, or assume an accepted Explorer navigation has settled.

Logs or output are needed

Use Claude Desktop Developer/extension diagnostics or Claude Code /mcp status. The IconVectors contract does not publish a separate sidecar log file. Use bounded results when catalog or output pressure appears.

For current client behavior, see the official Claude Code MCP documentation.