TrueIcon
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRUEICON_CACHE | No | Where downloaded packages and indexes are stored | ~/.trueicon/cache |
| TRUEICON_PROJECT_DIR | No | Project root holding `.iconmcp.json` and `package.json` | working directory |
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 |
|---|---|
| pingB | Health check |
| search_iconsA | Search icons in the icon packages installed in the project. Returns ranked matches with ready-to-paste import statements. |
| list_providersA | List the icon providers configured for this project and all providers trueicon supports. |
| get_iconA | Get the full record and exact import statement for an icon whose name is already known, e.g. Trash2 from lucide. |
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
Each tool serves a clearly distinct purpose: ping for health, search_icons for discovery, get_icon for exact retrieval, and list_providers for configuration. There is no ambiguity between searching and fetching a known icon, as the descriptions explicitly state when to use each.
Three of four tools follow a consistent verb_noun pattern (search_icons, list_providers, get_icon). The exception is 'ping', which is a standard health-check verb and not confusing, but it does deviate from the naming convention.
With only 4 tools, the server is tightly scoped to its purpose of searching and retrieving icons. Each tool is essential and there is no bloat or redundancy, making the count ideal for this domain.
The tool surface covers the core read operations: searching, retrieving exact icons, and listing providers. A minor gap is the lack of a way to browse all icons in a provider without a search query, but this is a workable limitation given the search functionality.