Skip to main content
Glama
SVGForge MCP

SVGForge MCP

by liqiang88

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SVGForge_API_KEYNoPersonal token `sf_…` from Dashboard → API tokens. Required for private tools.
SVGForge_API_BASENoAPI origin (no trailing slash).https://svgforge.dev
SVGForge_MCP_ALLOW_WRITENoSet `1` to enable `add_to_collection`.off

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_iconsB

Search SVGForge / Iconify icons by keyword. Returns icon keys (prefix:name) and brief meta. Prefer a prefix (e.g. lucide) for faster results.

get_iconA

Fetch a single icon as raw SVG or auto-generated React / Vue / Svelte / Data URI code.

list_icon_setsB

List available SVGForge icon packs (Lucide, Tabler, etc.).

get_my_collectionsA

List collections for the authenticated SVGForge user. Requires SVGForge_API_KEY.

get_custom_iconsA

List private custom icons for the authenticated Pro user. Requires SVGForge_API_KEY and Pro plan.

sanitize_svgA

Sanitize raw SVG: strip script tags, event handlers, dangerous URLs, and DOCTYPE/ENTITY payloads.

svg_to_data_uriA

Convert raw SVG into a Data URI for CSS background-image or HTML img src.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation4/5

Search vs. fetch vs. list are clearly separated, and the three listing tools (icon sets, user collections, custom icons) are scoped to distinct resources by name and description. Minor overlap: get_icon can emit a Data URI while svg_to_data_uri also produces one, and get_my_collections vs. get_custom_icons could be momentarily conflated by an agent unfamiliar with the SVGForge model.

Naming Consistency4/5

Five tools follow a clean verb_noun pattern (search_icons, get_icon, list_icon_sets, get_my_collections, get_custom_icons). sanitize_svg and svg_to_data_uri deviate into verb_object / object_to_object forms, but all names remain snake_case and self-explanatory.

Tool Count5/5

Seven tools is well within the ideal range and every tool serves a distinct role: discovery, retrieval, set/collection listing, and two SVG post-processing utilities. Nothing feels padded or missing at the count level.

Completeness4/5

The read/search/transform lifecycle is covered end to end: find icons, inspect sets, access private collections, and sanitize/convert output. Gaps exist on the write side — there is no way to upload or manage custom icons or create/modify collections — but for a fetch-and-prepare server these are workable omissions.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues