A
licenseB
qualityD
maintenanceMCP server that allows FE/UI/Designers to retrieve SVG icons via the Iconify API by simply asking LLMs rather than manually searching websites.
3
30
4
MIT
Supericons
Supericons 代理插件
面向 AI 编码代理的语义化 SVG 图标搜索。
Supericons 帮助代理通过含义（而非仅仅通过文件名）来查找图标。使用它可以搜索 20,000 多个免费图标、检索 SVG 代码，并为应用导航、仪表板、工具和产品 UI 推荐图标集。
快速安装
在任何支持 MCP 的编码代理中使用此配置：
{
"mcpServers": {
"supericons": {
"command": "npx",
"args": ["-y", "supericons-mcp"]
}
}
}Related MCP server: brain-mcp-icon-visual
IDE 设置字段
如果您的 IDE 显示的是表单而不是 JSON 文件，请输入：
Name: supericons
Transport: stdio
Command: npx
Arguments:
-y
supericons-mcp如果您的 IDE 只有一个参数字段，请输入：
-y supericons-mcp免费图标搜索请将环境变量留空。
专业版设置
如需高级图标或专业工具，请添加此环境变量：
SUPERICONS_API_KEY=your_api_key_here请勿将 API 密钥粘贴到公开的问题、截图或共享配置文件中。
托管的 MCP 端点
托管端点：
https://mcp.supericons.dev/mcp服务器卡片：
https://mcp.supericons.dev/.well-known/mcp/server-card.json可用工具
search_icons
: 通过含义、标签、视觉描述、标签和同义词搜索免费图标库。
recommend_icons
: 为 UI 插槽（如仪表板导航、应用标签页、设置面板或产品功能）推荐图标。
get_icon
: 通过图标 ID 和库检索单个 SVG 图标。
list_libraries
: 列出可通过 Supericons MCP 使用的免费图标库。
示例提示词
Use Supericons MCP to find a database icon. Prefer Lucide outline icons and show the icon id, library, and SVG.Use Supericons MCP to recommend icons for an AI dashboard sidebar. The slots are model, prompt, dataset, evaluation, deployment, and monitoring. Prefer Lucide outline icons.链接
公共仓库范围
本仓库仅为代理目录和 IDE 用户提供轻量级的设置包装器。它不包含私有的 Supericons 网站源代码、完整的语义注册表、内部构建工作流、私有数据、服务密钥或高级图标资产。
Available Tools
3 toolsconvert_svg_to_pngBInspect
Convert an SVG string to PNG. Converter MCP is a Pro workflow tool.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| svg | Yes | Raw SVG string to render. | |
| locale | No | Optional locale for multilingual output. Supported values: zh-Hans, zh-Hant, ja, ko, es, de, pt, ar, hi, vi, th. | |
| background | No | Background color: `transparent` or a hex value like `#ffffff`. | transparent |
| targetWidth | No | Output width in pixels. |
TDQS
B3.3/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It only states the basic conversion action and does not disclose any behavioral traits like idempotency, side effects, permissions, or output characteristics.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short with two sentences, no redundancy. However, it could be improved by adding more detail without becoming verbose. It is appropriately sized but lacks depth.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations, no output schema, and 4 parameters with some defaults and enums, the description is too minimal. It does not explain return values, error conditions, or limitations, leaving the agent underinformed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all parameters. The description adds no additional meaning beyond the schema's parameter descriptions, meeting baseline expectations.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Convert an SVG string to PNG', which is specific with a verb and resource. It distinguishes from sibling tools 'inspect_converter_options' and 'preview_icons' by focusing on a direct conversion action.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no explicit guidance on when to use this tool over alternatives. The phrase 'Pro workflow tool' hints at advanced use but lacks clarity on context or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
inspect_converter_optionsAInspect
List the current Converter MCP options, workflow hints, and recommended starting combinations. Converter MCP is a Pro workflow tool.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| locale | No | Optional locale for multilingual output. Supported values: zh-Hans, zh-Hant, ja, ko, es, de, pt, ar, hi, vi, th. |
TDQS
A3.7/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden for behavioral disclosure. It describes the tool as listing options, which suggests a read-only operation, but does not explicitly state that it is non-destructive or mention any side effects. The behavior is straightforward but not fully transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description consists of two short, front-loaded sentences. The first states the purpose, and the second adds useful context about it being a Pro workflow tool. Every sentence serves a purpose with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given there is no output schema and no annotations, the description does not specify the output format (e.g., whether it returns a list or object) or how to interpret the options and workflow hints. It is adequate for a simple listing tool but lacks completeness for agents needing to parse the response.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has one parameter (locale) with 100% schema coverage, meaning the schema adequately describes it. The parameter description is included in the schema but not reiterated in the main description. The description adds no extra semantic meaning beyond what the schema provides, so baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'List' and the specific resource 'Converter MCP options', workflow hints, and recommended starting combinations. It distinguishes from sibling tools 'preview_icons' and 'convert_svg_to_png' by focusing on inspecting configuration rather than previewing or converting.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies that this tool is used to inspect options and workflow hints, but it does not explicitly state when to use it versus the siblings or provide any exclusions or prerequisites. The usage context is implied but not clarified.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
preview_iconsAInspect
Refine an icon result set or preview known icon refs. Use search_icons first for normal icon requests. Long icon lists are accepted and safely truncated to 12. Returns a browser preview page, direct PNG image URL, ready-made Markdown image snippet, and, when requested, an MCP image contact sheet.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Requested inline icon count. Values outside 1 to 12 are safely clamped with a warning. Numeric strings are accepted. | |
| query | No | Optional search query to preview visually, for example "license plate recognition camera scan car". | |
| style | No | Optional style preference. Unsupported values are ignored with a warning. | any |
| locale | No | Optional locale for multilingual search terms. Unsupported values are ignored with a warning. | |
| library | No | Optional library filter such as si (Supericons), mingcute, lucide, tabler, material, or simpleicons (Simple Icons). | |
| icon_refs | No | Optional fixed icon refs in library:id format. Arrays, a single ref, and comma-separated refs are accepted. Up to 100 are accepted, 24 appear on the browser preview, and 12 are rendered inline. Larger lists are safely truncated with a warning. | |
| include_image | No | When true, include a PNG contact sheet as MCP image content. Boolean strings are accepted. A preview_url is always returned. |
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses truncation of lists to 12, clamping of limit, acceptance of icon_refs up to 100, and returned items. It lacks explicit read-only or auth info, but the preview nature implies no side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise: two sentences front-loading purpose and usage, then listing capabilities. Every sentence adds value with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Without an output schema, the description sufficiently explains return types (preview page, PNG URL, Markdown snippet, contact sheet). It covers main use cases and edge cases like truncation. Could add example usage but is adequate for an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so baseline is 3. The description adds some behavioral context (truncation, clamping) but largely repeats schema info. No new parameter-specific meaning beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool refines icon result sets or previews known icon refs, using specific verbs and resources. It distinguishes from the sibling search_icons by advising to use that first for normal requests.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says 'Use search_icons first for normal icon requests,' providing a clear context for when to use this tool. However, it does not address exclusions for its sibling tools inspect_converter_options and convert_svg_to_png.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
A3.7/5.0
Disambiguation5/5
Each tool serves a distinct purpose: inspecting converter options, previewing icons, and converting SVG to PNG. No overlap in functionality.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern: inspect_, preview_, convert_. The naming is uniform and predictable.
Tool Count5/5
With 3 tools, the server is appropriately scoped for icon-related tasks. It covers configuration, preview, and conversion without unnecessary bloat.
Completeness2/5
The tool set is missing a search_icons tool, which is referenced in the preview_icons description as a prerequisite. This gap limits the workflow and indicates incompleteness for the domain.
Maintenance
ActivitySlowing
ResponsivenessSyncing
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Search open SVG icon packs and fetch exact SVG markup from coding agents through MCP.
Icons for agentic development: search & fetch 366,000+ open-source icons as SVG/PNG. No API key.
Pay-per-use tool marketplace for AI agents. Search, price-check, and call APIs via MCP.
Search & install 6,500+ AI agent skills from skills-hub.ai inside any MCP tool.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceVisual icon search, retrieval, and comparison for AI agents. Search 200k+ icons semantically, render side-by-side comparison grids, and retrieve raw SVG markup — all tools return images so vision-capable LLMs can see the icons.1
Svg/icons MCPofficial
AlicenseNot gradedqualityCmaintenanceEnables AI coding tools to search, inspect, recommend, and export SVG icons from svgicons.com for use in design systems, frontend projects, and AI-assisted workflows.MIT- FlicenseNot gradedqualityCmaintenanceMCP server for searching Material Design Icons, enabling AI agents to find icons by name, alias, category, or concept.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/curlymolelabs/supericons'
If you have feedback or need assistance with the MCP directory API, please join our Discord server