Local stdio MCP integration for the proprietary IconVectors SVG editor. Requires a separate installation. Public repository contains documentation and configuration examples.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
One-click editor setup isn’t available for this listing yet — we don’t have a confirmed install command, and we’d rather show nothing than point your editor at the wrong package or host. Follow the project’s own setup instructions, linked above.
Manual Client & Custom JSON ConfigExpand JSON â–¾
No confirmed setup config for this listing yet. We only publish a config block when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for Axialis IconVectors MCP, and we’d rather show nothing than a guess you’d paste into your client. Follow the project’s own setup instructions for the current steps.
Documentation Overview
Axialis IconVectors MCP
This repository contains documentation and configuration examples for the MCP integration available in Axialis IconVectors. It does not contain the IconVectors application source code.
Introduction
Axialis IconVectors 2.0 exposes SVG editing capabilities through the Model Context Protocol (MCP). Compatible AI coding agents can inspect and operate the running desktop application and its SVG documents.
IconVectors is proprietary software, installed separately. This documentation repository is named iconvectors-mcp.
On Windows, the MCP client launches IconVectorsMcp.exe as a separate local process and communicates with it over stdio. Start IconVectors normally first and leave it running. The companion connects to the application over local TCP at 127.0.0.1:61337 by default. This application connection is not an HTTP MCP URL.
This diagram describes the user workflow only.
Supported AI coding agents
The official IconVectors documentation provides Windows setup instructions for all eight clients below. Each guide includes the configuration location, a minimal example and connection checks.
| Client | Configuration guide |
|---|---|
| OpenAI Codex | Codex |
| Claude Code | Claude Code |
| Cursor | Cursor |
| VS Code / GitHub Copilot | VS Code / GitHub Copilot |
| Gemini CLI | Gemini CLI |
| Kiro | Kiro |
| Cline | Cline |
| GitHub Copilot CLI | GitHub Copilot CLI |
What can an agent do?
The MCP tools cover these areas:
| Area | Operations |
|---|---|
| Application state | Check connectivity, application information, capabilities and active workspace. |
| SVG inspection | Read document information and SVG content; inspect DOM elements, selection and styles. |
| Selection and editing | Select elements; create shapes and paths; change attributes, fills, strokes and transforms. |
| Document operations | Create or open documents, save changes and export requested output. |
| Repetitive editing | Align, duplicate, group, recolor and apply supported path operations. |
| Cleanup | Inspect SVG cleanup findings and explicitly request the supported conservative fixes. |
| Preview and history | Render previews; use Undo/Redo and transactions for supported document edits. |
| Explorer navigation | Inspect the active folder, entries and selection; navigate to folders, parents or children, and move through folder history. |
| Explorer file operations | Create and rename direct-child folders; delete an empty direct-child folder; copy selected SVG file paths to the OS clipboard; paste, duplicate and group SVG files. |
| Explorer batch operations | Plan and apply palette changes, icon resizing and stroke changes to selected SVG files. |
Available capabilities depend on the installed IconVectors version. Use MCP tool discovery and app_getCapabilities; obtain exact arguments from the installed tool schemas rather than inferring them from these summaries. A command being available in the user interface does not guarantee that an MCP tool exposes it.
Document Undo does not reverse saving/exporting or Explorer filesystem changes. Creating, opening or replacing a document clears document Undo history. Review targets and destinations before requesting these operations. Explorer batch operations require a plan, review of that plan, then application of its returned identifier. See the official MCP guide for the documented limits.
Style setters also update application drawing defaults. For an edit confined to one object, inspect its current style and use an explicit element target with a DOM attribute or style patch.
Requirements
- An installed, running copy of IconVectors 2.0 with its matching MCP executable.
- A local MCP client able to launch a stdio process on the same machine.
- Permission to use the client and its MCP integration; organization policy may restrict this.
- The correct executable path and application port.
See the official download page for current Windows, macOS and Linux releases and requirements. The configuration examples in this repository cover native Windows integration.
Getting started
For native Windows:
- Install IconVectors using the official download page.
- Start IconVectors normally and leave it open.
- Confirm that
IconVectorsMcp.exeexists in the installation directory. - Add the server using the guide for your client.
- Let the client start the MCP process. It should discover tools from that process.
- Ask the agent to call
app_ping,app_getInfo,app_getCapabilitiesandapp_get_workspace. - Check that the application, workspace and document are the intended targets before requesting an edit.
Client configuration
The guides use this normal Windows installation path:
The examples explicitly pass the documented default application port:
Replace the executable path if your installation differs. If the application's Options/McpPort setting has changed, use the same port in the client configuration. Preserve existing server entries when adding IconVectors.
No custom host argument is needed for this local default setup.
Use the client-specific file format: Codex uses TOML, VS Code uses a servers JSON object, and several other clients use mcpServers. The installed iconvectors-mcp-tools.json is a tool reference, not a client connection configuration.
Example workflow
Begin with a read-only request:
After reviewing the result, request a bounded change:
Finally, explicitly request saving or exporting to your chosen local destination. Reinspect object targets after structural changes. Use a history transaction only for compatible document edits, with the transaction identifier returned by the tool.
Documentation
- Official MCP integration guide
- Client configuration guides
- Troubleshooting
- IconVectors product information
- Official downloads
Use the command reference and tool schemas supplied with your installed version. Where available, Help > Open MCP Files Folder opens the installed helper documents.
Troubleshooting
If the server is missing, check the client configuration location and executable path. If tools appear but calls fail, check that IconVectors is running and the ports match. Restart or reload the client connection when it has not picked up a configuration change.
A client running in a cloud environment, container or WSL does not automatically share the desktop application's local connection or filesystem. This repository documents local stdio integration, without a remote HTTP service.
See troubleshooting for connection, discovery, version and workspace checks.
About this repository
This repository contains public documentation, configuration examples and integration guidance. It does not distribute the IconVectors application, its proprietary implementation, or an independently runnable MCP server. Install the application separately from the official website.
The guides follow the official IconVectors MCP documentation and client setup guides. Use the documentation and tool schemas corresponding to your installed application version.
The configuration files are examples for a client you control. Reading or cloning this repository does not install or enable the integration.
Related MCP Servers
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Axialis IconVectors MCP
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/axialis-iconvectors-mcp)HTML Embed
<a href="https://allmcps.com/mcp/axialis-iconvectors-mcp"><img src="https://allmcps.com/api/badge/axialis-iconvectors-mcp?style=directory" alt="Axialis IconVectors MCP on AllMCPs" /></a>Technical Specs & Signals
CategoryDeveloper Tools
35Quality signal: Fair · 35/100How this signal is calculated ▾
Server availabilityNot measured
Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership8/20
Documentation & tools17/30
Adoption & activity1/15
Community engagement0/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.
Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.