svg2vector

This MCP server converts SVG files into Android Vector Drawable XML. It exposes a tool named convert_svg_to_vector that accepts an SVG file path (local or URL) and outputs an Android Vector Drawable XML file. The server supports SVG inputs from local files, remote URLs, and SVG assets exported from Figma MCP. You can run the server via the npm package svg2vector-mcp and connect to it from an MCP client like Claude Desktop. Usage examples show converting local SVGs, remote SVGs, or SVGs exported from Figma MCP, with the resulting XML written to the specified output path. When integrated into an MCP workflow, this server helps bridge design assets to Android-ready vector drawables by converting shapes such as paths, rectangles, circles, polygons, and lines into vector paths while preserving stroke and fill properties.

Prerequisites:

• Node.js and npm installed on your system
• Access to install global npm packages

Option A: Install from npm (recommended)

• Run: npm install -g svg2vector-mcp
• Start the server (example): svg2vector-mcp

Option B: Install from source

• Clone the repository: git clone <your-repo>
• Enter the project directory: cd svg2vector-mcp
• Install dependencies: npm install
• Link the package globally (for development workflow): npm link
• Start the server (example): node src/index.js

If you want to connect via MCP, ensure your client configuration points to the running server (see the usage section for examples).

Tips and notes:

• The server focuses on converting SVG elements to Android Vector Drawables. Supported elements include path, rect, circle, polygon, line (all converted to paths) and g groups. Unsupported features include text, gradients, filters, animations, ellipses, polylines, embedded images, and clipping paths.
• Output is compatible with Android API 21+.
• When integrating with Figma MCP, you can export SVGs from Figma and then run the converter to generate the corresponding Android vector XML.
• If you encounter issues, refer to troubleshooting guidance in the README (e.g., missing viewBox, invalid SVG root). You can also programmatically use the converter via the provided API to catch and inspect errors.
• If you install from source, remember to run npm install to fetch dependencies before starting the server.