Using IconVectors with Codex CLI

IconVectors 1.40 publishes a local MCP workflow for Codex CLI. Codex talks to IconVectorsMcp.exe, and that sidecar forwards tool calls to the running editor so prompts operate on the real document rather than detached SVG text.

Current public setup note: the example paths below use the Windows 1.40 release. The macOS MCP package is being prepared.

Before you begin

• Install and start IconVectors.exe.
• Confirm that C:\Program Files\Axialis\IconVectors\IconVectorsMcp.exe exists.
• If the helper bundle is installed, use Help -> Open MCP Files Folder and inspect %APPDATA%\Axialis\IconVectors\MCP\codex-implementation-instructions.md.

1. Start the editor

& 'C:\Program Files\Axialis\IconVectors\IconVectors.exe'

Start the desktop app first. In the standard setup, Codex launches IconVectorsMcp.exe --port 61337 and the editor keeps ownership of the document, rendering pipeline, and undo history.

2. Configure Codex CLI

Add an MCP entry to one of these files:

• ~/.codex/config.toml
• .codex/config.toml inside your project

[mcp_servers.iconvectors]
command = 'C:\\Program Files\\Axialis\\IconVectors\\IconVectorsMcp.exe'
args = ['--port', '61337']
cwd = 'C:\\Program Files\\Axialis\\IconVectors'
startup_timeout_sec = 20
tool_timeout_sec = 120

If you changed the bridge port in IconVectors, use the same value here.

3. Verify the connection

Good first prompts:

• Use IconVectors to call app.ping and report whether the editor is connected.
• Use IconVectors to call app.getInfo and summarize the current document state.
• Create a new 32x32 document named "test icon", draw a centered blue circle, and export it as SVG.

4. Next step

Once Codex can see the server, try the complete example in Create an Info Icon with Codex CLI. That walkthrough uses the exact prompt from the IconVectors MCP documentation and shows the result in both MP4 and GIF form.