Md2svg-mcp
# Md2svg-mcp
A Model Context Protocol (MCP) server that converts Markdown text to SVG images.
## Overview
This MCP server provides a tool to transform Markdown content into SVG format. It supports various Markdown elements, including headings, lists, code blocks, and tables. The server can be easily integrated into any MCP client, allowing users to visualize Markdown content in a scalable vector graphic format.
## Features
- **Markdown Parsing**: Converts Markdown text to structured blocks.
- **SVG Generation**: Renders Markdown elements as SVG elements.
- **Customization**: Supports customizable output dimensions, padding, and colors.
- **MCP Integration**: Compatible with any MCP client.
## Installation
```json
{
"mcpServers": {
"md2svg-mcp": {
"command": "uvx",
"args": [
"md2svg-mcp"
]
}
}
}
```
## Configuration
The `markdown_to_svg` tool supports the following parameters:
- `md_text`: The Markdown text to be converted.
- `output_file`: The output SVG file name (default: `output.svg`).
- `width`: The width of the SVG image (default: `720`).
- `padding`: The padding around the SVG content (default: `50`).
## Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as converting markdown to SVG images, making it unambiguous in isolation.
The single tool name 'markdown_to_svg' follows a clear verb_noun pattern (convert markdown to SVG). With only one tool, consistency is inherently perfect as there are no other names to compare against.
A single tool is too few for most practical server purposes, as it limits functionality and flexibility. While it might suffice for a very narrow task like markdown-to-SVG conversion, it feels thin and under-scoped for typical MCP server use cases.
For the narrow domain of markdown-to-SVG conversion, the single tool covers the core function. However, there are obvious gaps such as configuration options (e.g., styling, sizing), error handling tools, or complementary operations like SVG validation or batch processing, making the surface notably incomplete for broader agent workflows.