mcp-server-icon
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LANGUAGE | No | Interface language setting (en or zh-CN) | en |
| MCP_LOG_DIR | No | Log directory | ./logs |
| MCP_LOG_FILE | No | Log filename | mcp-icon.log |
| WEB_SERVER_AUTO_OPEN | No | Whether to auto-open browser (true or false) | true |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_iconsB | Search icons from iconfont.cn (single keyword search only) |
| get_cache_statsC | Get cache statistics |
| clear_cacheC | Clear icon cache |
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: searching icons, reading cache stats, and clearing the cache. There is no overlap or chance of misselection.
All three names use the same snake_case verb_noun convention (search_icons, get_cache_stats, clear_cache). The pattern is predictable and readable.
Three tools is on the thin side for an icon server, since only one delivers the core capability and the other two are cache maintenance. Still, each tool is justified and nothing is redundant.
Only single-keyword search is offered, with no way to fetch a specific icon's details or assets, no category/batch lookup, and no pagination or filtering. Cache lifecycle is covered, but the core icon domain surface is notably shallow.