Md2svg-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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| markdown_to_svgC | mardown转换为svg图片 |
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 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.