lucide-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 |
|---|---|
| list_iconsB | List all available Lucide icon names. |
| search_iconsA | Search Lucide icons by name using exact, partial, and fuzzy matching. |
| get_icon_metadataA | Get Lucide icon metadata such as tags, aliases, local SVG path, and suggestions for unknown icons. |
| get_icon_svgA | Get the raw SVG markup for a Lucide icon by name. |
| add_icon_to_projectB | Add a Lucide SVG icon file to the current project. |
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 5 tools
Each tool has a clear, distinct purpose: listing all icons, searching by name, retrieving metadata, retrieving SVG markup, and adding to a project. There is minimal overlap, and even list_icons vs search_icons are differentiated by exhaustive vs filtered retrieval.
All tool names follow a consistent verb_noun pattern (list, search, get, get, add). The naming is predictable and intuitive, making it easy for an agent to infer function from the name.
With exactly 5 tools, the set is well-scoped for managing Lucide icons. Each tool covers a necessary operation without unnecessary bloat or duplication.
The tool surface covers the complete lifecycle for working with icons: discovery (list/search), inspection (metadata/svg), and integration (add to project). No obvious gaps exist for the stated purpose.