pyside-iconify-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
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_referenceA | Read the authoritative, version-matched usage of pyside-iconify: exact signatures, accepted values, working examples and a table of common mistakes. Call it before writing pyside-iconify code; start with topic 'overview'. Call without a topic to list the topics. |
| search_iconsA | Find real icons by keyword (use this instead of guessing an icon name). Returns 'prefix:name' strings that exist in Iconify, plus the icon sets they belong to. A query with several words must match all of them; narrow with 'prefix' (e.g. 'mdi', 'lucide'). status 'unavailable' means the lookup failed (for example no network), not that nothing exists. |
| check_iconsA | Verify icon names before using them in code. For each name returns whether it exists (status 'ok', 'not_found', 'invalid_name' or 'unavailable'), and for existing icons whether they are monotone or multi-color (fixed_colors), whether they animate themselves, and notes about what that means for color and animation arguments. For missing icons returns similar real icons. 'unavailable' means the check failed (for example no network), not that the icon is missing. |
| check_codeA | Check the pyside-iconify usage in a piece of Python code without running it. Finds unknown imports, unknown or misplaced parameters (for example hover_color on get_icon), invalid values (size, color, opacity, rotate, animation), conflicting options, malformed or non-existent icon names, and multi-color or animated icons used in ways that do not work. 'ok' is true when there are no errors. Only values written literally in the code are checked; anything else is listed under 'skipped' instead of being guessed. Run it on finished code and fix every error. |
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 has a clearly distinct role: documentation lookup, icon discovery, icon-name validation, and static code checking. Although search_icons and check_icons both involve icon names, their descriptions make the distinction explicit: one finds icons, the other verifies them before use.
All tool names use consistent snake_case with a verb_noun pattern: get_reference, search_icons, check_icons, check_code. The convention is predictable throughout.
Four tools is well-scoped for a focused pyside-iconify assistance server. Each tool covers a necessary part of the workflow without redundant operations.
The surface covers the full assistance lifecycle: reference documentation, icon discovery, icon validation, and code validation. There are no obvious dead ends for an agent writing pyside-iconify code.