hugeicons-mcp
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_iconsA | Find Hugeicons by name, tag or category. Returns names to pass to get_icon. |
| get_iconA | Returns one icon as SVG markup in the chosen style. Optionally writes it to an .svg file (use an absolute path), for example to upload into Figma. |
| compare_stylesA | Returns the same icon as SVG in every installed style, to choose between them. |
| list_stylesA | Shows which of the 10 styles are installed and how to add the missing ones. |
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 4 tools
Each tool serves a clearly distinct purpose: searching, retrieving a single SVG, listing styles, and comparing all styles. The boundary between get_icon and compare_styles is well defined by the latter returning every installed style for comparison.
All four tools follow a consistent verb_noun convention: get_icon, list_styles, search_icons, compare_styles. There is no mixing of camelCase, vague verbs, or inconsistent patterns.
Four tools are well scoped for an icon lookup server: search, inspect installed styles, retrieve an icon, and compare styles. Each tool earns its place without redundancy.
The core workflow of finding, inspecting, and retrieving icons is covered, including style discovery and comparison. Minor gaps such as explicit category/tag enumeration or richer icon metadata exist, but agents can work around them via search.