image2svg-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_image_to_svgA | Convert a raster image (PNG, JPG, or WEBP) to SVG vector format. Accepts either base64-encoded image data or a URL. Returns the SVG content as a string. Adjust tracing parameters to control the fidelity and complexity of the output. |
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 1 tool
With only one tool, there is no risk of confusion or overlap. The tool's purpose is clearly defined and distinct.
The single tool name follows a consistent verb_noun pattern (convert_image_to_svg). No inconsistency is possible with only one tool.
The server is scoped to a single conversion task, so one tool is reasonable. However, it feels slightly minimal; additional tools for parameter adjustment or batch processing could be beneficial.
The tool covers the core conversion operation but lacks auxiliary tools for e.g., managing tracing parameters or validating outputs. This is a minor gap given the focused domain.