lucide-svg-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 | Lists available Lucide icons with pagination. |
| search_iconsA | Searches for Lucide icons by name or keywords. |
| retrieve_iconA | Retrieves the source of the icon in SVG format. |
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 3 tools
Each tool has a clearly distinct purpose: listing all icons, searching by name/keyword, and retrieving a specific icon's SVG source. There is no meaningful overlap that would cause an agent to select the wrong tool.
All tool names follow a consistent verb_noun pattern: list_icons, search_icons, retrieve_icon. The naming is predictable and uniform.
Three tools is a well-scoped size for an icon library MCP server. Each tool provides essential functionality without unnecessary bloat or missing essentials.
For an icon retrieval service, listing, searching, and fetching SVG source cover the full lifecycle of icon access. There are no obvious dead ends or missing operations that would hinder an agent.