MCP Server
Icons for your AI coding agent.
SVGForge MCP exposes search and SVG export to Cursor, Claude Desktop, and other Model Context Protocol clients. Same Iconify catalog and API token as the VS Code extension — no local icon database.
How it works
-
Create a token
Sign in to the
Dashboard → API tokens
and create a token. Copy the
sf_…value once. -
Add the MCP server
Point your client at
npx -y svgforge-mcp(source on GitHub) with envSVGForge_API_KEY. -
Ask the agent
Examples: search
lucide home, fetch React/Vue/Svelte code, list your collections.
Cursor config
In Cursor open Settings → Customize → MCPs, then add:
{
"mcpServers": {
"svgforge": {
"command": "npx",
"args": ["-y", "svgforge-mcp"],
"env": {
"SVGForge_API_KEY": "sf_xxx",
"SVGForge_API_BASE": "https://svgforge.dev"
}
}
}
}
Tools
search_icons— keyword / prefix searchget_icon— SVG, React, Vue, Svelte, or Data URIlist_icon_sets— browse packsget_my_collections/get_custom_icons— requires token (Pro for private uploads)sanitize_svg/svg_to_data_uri— local utilities
Privacy & access
- Public search and get work without a token; collections and custom icons need
sf_…. - The bridge only calls the SVGForge HTTPS API — it does not scan your disk or upload project files.
- Write tools (add to collection) stay off unless you set
SVGForge_MCP_ALLOW_WRITE=1. - Revoke a token anytime from the Dashboard.
Prefer a GUI?
The same token works in the VS Code extension, Chrome extension, and Figma plugin. Use the web app for collections and browser-local SVG tools.