Iconify 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_all_icon_setsA | Browse all available icon collections from Iconify (200+ icon sets with 200,000+ icons). Returns a list of all icon sets with their metadata including name, total icons, author, license, and sample icons. |
| get_icon_setB | Retrieve detailed information about a specific icon set including all available icons in that set. Provide the icon set prefix (e.g., 'mdi', 'fa', 'bi'). |
| search_iconsB | Search through Iconify's icon collection with flexible query parameters. Returns matching icons from all icon sets or a specific set. |
| get_icon_dataB | Retrieve specific icon data with usage examples for popular frameworks (React, Vue, Svelte, etc.). Provide the full icon name in format 'prefix:icon-name' (e.g., 'mdi:home', 'fa:user'). |
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
get_all_icon_sets vs get_icon_set is clearly distinguished (all collections vs one collection), and search_icons is distinct. get_icon_data and get_icon_set both return icon-related info, so there is minor potential for confusion, but descriptions clarify the granularity.
All four names follow a clean verb_noun snake_case pattern (get_icon_set, get_all_icon_sets, search_icons, get_icon_data). The convention is highly predictable and consistent.
Four tools is a tight, well-scoped surface covering browse, search, set detail, and single-icon retrieval. It is slightly lean, but each tool earns its place for the icon-lookup domain.
The surface covers browsing sets, listing all sets, searching, and fetching icon data with framework usage examples, which handles the core icon-discovery lifecycle. Minor gaps exist (e.g., batch/multi-icon retrieval), but agents can work around them.