SVG2PNG

You have an MCP server that converts SVG code to PNG images. It runs as a local, composable service that can be started by an MCP client and integrated with other MCP components using the MCP protocol.

How to use

Use your MCP client to connect to the SVG to PNG MCP Server and send SVG data to request PNG output. The server exposes an interface that accepts SVG input and returns a PNG image. You can place the server in your workflow alongside other MCP services, enabling automated rendering of SVG assets into PNG files for thumbnails, previews, or asset pipelines.

How to install

Prerequisites you need before installing: Python, a virtual environment tool, and internet access to install dependencies.

# Install Smithery client (if you want automatic client setup)
npx -y @smithery/cli install @longbowzz/svg2png_mcp --client claude

Create and activate a Python virtual environment to isolate dependencies.

# Create a virtual environment
python -m venv venv

# Activate the virtual environment
# macOS/Linux:
source venv/bin/activate
# Windows:
.\venv\Scripts\activate

Install required Python packages from the dependencies file.

pip install -r requirements.txt

Configuration and running tips

Configure the MCP server by providing an absolute path to the Python interpreter inside your virtual environment and the absolute path to the server script. This ensures MCP clients can locate and start the server reliably.

{
  "mcpServers": {
    "svg2png": {
      "command": "/absolute/path/to/venv/bin/python",
      "args": [
        "/absolute/path/to/svg2png_mcp/src/server.py"
      ]
    }
  }
}

Notes and requirements for the paths and environment variables are important. Use absolute paths for both the Python interpreter and the server script. This guarantees that MCP clients can reliably start the server.

Additional considerations

The server currently uses the CairoSVG conversion path by default for speed and simplicity. If you encounter font rendering issues or need full SVG feature support, you can switch to the Inkscape-based path, which offers more comprehensive rendering at the cost of setup complexity and runtime speed.

Core capabilities include asynchronous operation, error handling, and a dedicated SVG to PNG conversion routine. The server integrates with standard MCP clients and supports discovery and asynchronous calls.

Available tools

svg_to_png

Converts SVG data into PNG images using CairoSVG by default, with an optional Inkscape path for full SVG feature support.

server_interface

Provides an MCP-compatible interface to start, stop, and handle SVG-to-PNG conversion requests with asynchronous processing and error handling.