Svg Tracer
Turn PNG or JPG logos and UI bitmaps into crisp SVG assets inside Claude Code or Cursor without leaving the agent chat.
Overview
com.pulsemcp/svg-tracer is a MCP server for the Build phase that converts bitmap images to SVG vector graphics using potrace tracing.
What is this MCP server?
- Converts bitmap images to SVG via potrace tracing exposed as MCP tools
- Runs as stdio npm package @pulsemcp/svg-tracer-mcp-server (npx -y)
- Suited for logos, screenshots, and simple illustrations that need vector output
- Version 0.1.2 from PulseMCP productionized svg-tracer subfolder
- MCP integration—not a standalone design app or browser automation skill
- Server version 0.1.2
- npm package @pulsemcp/svg-tracer-mcp-server with stdio transport
- Tracing engine: potrace for bitmap-to-SVG conversion
What problem does it solve?
Raster icons and logos block clean responsive UI and force manual retracing in separate design tools.
Who is it for?
Indie builders who need quick SVG conversion for favicons, logos, and simple UI glyphs while coding the frontend.
Skip if: Photo-realistic art, complex gradient illustrations, or teams that need full vector editing and layer control in Figma.
What do I get? / Deliverables
Your agent can produce scalable SVG files from bitmaps during frontend tasks without leaving the MCP-enabled editor.
- SVG vector output derived from supplied bitmap images
- Agent-callable tracing workflow wired into your MCP config
- Scalable assets ready for React, Vue, or static site icon folders
Recommended MCP Servers
Journey fit
Vector asset prep sits in Build when you are shaping UI, favicons, and marketing graphics before or during frontend work. Frontend builders need scalable icons and illustrations; potrace-based tracing is a direct frontend asset pipeline step.
How it compares
MCP tracing integration, not a browser automation skill or a hosted design marketplace.
Common Questions / FAQ
Who is com.pulsemcp/svg-tracer for?
Solo builders and small teams using Claude Code, Cursor, or similar agents who want bitmap-to-SVG conversion inside the coding workflow.
When should I use com.pulsemcp/svg-tracer?
Use it during Build frontend work when you have PNG or JPG assets that must become SVG for components, PWA icons, or sharp marketing pages.
How do I add com.pulsemcp/svg-tracer to my agent?
Register the stdio server with npx -y @pulsemcp/svg-tracer-mcp-server in your MCP client config per PulseMCP server.json runtimeHint.