SVGR MCP Server
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_svg_to_reactB | Convert SVG content or file to React component using SVGR |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| svg_to_react_native | Convert SVG to React Native component with TypeScript and named export |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is singular and well-defined.
The single tool name follows a clear verb_noun pattern (convert_svg_to_react) and is descriptive of its function.
With only one tool, the server feels minimally scoped. While the tool is not trivial, the server would benefit from additional tools (e.g., for configuration or batch processing) to better serve its domain.
The tool covers the core conversion task for both SVG content and files, but lacks options for customizing SVGR parameters or handling complex workflows. Minor gap in configurability.