Lucide Icons 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_iconsB | Search for icons from lucide by name or category using partial matching |
| search_categoriesB | Search for icon categories by category name using partial matching |
| fuzzy_search_iconsB | Fuzzy Search for icons from lucide by icon name |
| fuzzy_search_categoriesC | Fuzzy Search for icon categories by category name |
| get_icon_usage_examplesC | Get usage examples for a Lucide React icon |
| list_all_icons_by_categoryC | List all icons in a specific category |
| list_all_categoriesA | List all available icon categories with their icon counts |
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 7 tools
There is significant overlap between fuzzy_search_categories and search_categories (both search categories by name, just with different matching algorithms), and between fuzzy_search_icons and search_icons (both search icons, with fuzzy vs partial matching). This creates ambiguity about which tool to use for similar tasks. However, the other tools (get_icon_usage_examples, list_all_categories, list_all_icons_by_category) have distinct purposes.
All tools follow a consistent snake_case naming pattern with clear verb_noun structure (e.g., fuzzy_search_categories, list_all_categories, get_icon_usage_examples). The naming is predictable and readable throughout the set, with no deviations in style or convention.
With 7 tools, the count is well-scoped for an icon library server, allowing coverage of categories, icons, and usage examples. It's slightly on the higher side due to redundant search tools, but overall reasonable and not excessive for the domain.
The tool set covers key operations for an icon library: listing categories and icons, searching icons and categories, and getting usage examples. There are minor gaps, such as no tool for getting detailed icon metadata (e.g., SVG data or tags) or managing icons, but core workflows for discovery and usage are well-covered.