mcp-svg-marp
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_svg_to_marpB | Convert an SVG file to a Marp presentation |
| analyze_svgB | Analyze an SVG file and suggest Marp presentation structure |
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 2 tools
Each tool has a clearly distinct purpose: one analyzes an SVG to suggest a Marp structure, the other converts an SVG to a Marp presentation. There is no functional overlap or ambiguity.
Both tool names follow a consistent snake_case verb_noun pattern: convert_svg_to_marp and analyze_svg. The naming is predictable and clearly indicates the action and target.
With only 2 tools, the server feels slightly thin for a conversion-oriented domain. However, the tools are tightly focused and cover the primary workflow, making the count borderline but defensible.
The core workflow of analyzing an SVG for structure and then converting it to Marp is fully covered. Minor gaps exist, such as no tool for managing multiple conversions or editing Marp output, but these are not dead ends for the main purpose.