VectorMagic MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VECTOR_MAGIC_EXE | No | Path to vmde.exe or to its folder. If Vector Magic is not in the default location, set the path to vmde.exe. | C:\Program Files (x86)\Vector Magic\vmde.exe |
| VECTOR_MAGIC_LOAD_TIMEOUT | No | Seconds to open the image. | 90 |
| VECTOR_MAGIC_SAVE_TIMEOUT | No | Seconds to write the file. | 120 |
| VECTOR_MAGIC_VECTORIZE_TIMEOUT | No | Seconds per vectorization pass. Raise this value for timeouts with huge photos. | 300 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vectorize_imageA | Convert a bitmap image (PNG, JPG, GIF, BMP, TIFF, PSD, TGA...) into an editable vector file with Vector Magic Desktop Edition. Uses Vector Magic's fully automatic mode, then optionally changes the level of detail and colour mode, and writes SVG, AI, EPS, PDF, DXF or EMF (or a re-rendered PNG/JPG/BMP/TIF). Returns the output path, a summary of what Vector Magic detected (image type, detail, number of colours) and a preview image of the vector result. Takes ~10-30 s per image; large photos take longer. Files are never overwritten unless overwrite is true. |
| vectorize_batchA | Vectorize many images in one call with the same options (one Vector Magic run per image, sequentially). Give either input_paths or input_dir (non-recursive; only supported image types are picked). Outputs go to output_dir, or next to each input. Returns one result per image; a failure does not stop the batch. |
| get_vector_magic_statusA | Check that Vector Magic Desktop Edition is installed and usable: executable path, version, Vector Magic windows already open (the connector never touches them; it starts its own), supported input/output formats and timeouts. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools target clearly distinct operations: single-image conversion, batch conversion, and environment/health status. There is no overlap or plausible misselection between vectorize_image and vectorize_batch since the scope difference (one vs many) is explicit.
All names use snake_case with a verb_noun pattern (vectorize_image, vectorize_batch, get_vector_magic_status). The verbs differ meaningfully but the convention is uniform and predictable.
Three tools is a tight, well-scoped surface for an image-to-vector conversion service: one for a single file, one for batches, one for environment checks. It is slightly lean but each tool clearly earns its place.
The core lifecycle of vectorizing images (single, batch) plus a status/preflight check is covered, and format support is reported via status. Minor gaps like querying or re-rendering prior results without re-running are acceptable workarounds.