pictogrammers-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| init_project_icons | Pin this project to ONE Pictogrammers icon library so every icon you add stays visually coherent. Writes pictogrammers.config.json at the project root. Call this once before adding icons. |
| project_icon_statusA | Show the pinned icon library for this project, its defaults, and the inventory of icons used so far. |
| list_libraries | List the available Pictogrammers icon libraries with their style, grid size, icon count and npm packages. |
| list_tags | List the category tags for a library, so you can browse/filter icons by category. |
| search_icons | Search icons by keyword. Returns ranked matches (name, aliases, tags, codepoint). Defaults to the project's pinned library and variant for coherence. Use get_icon to fetch the actual SVG. |
| get_icon | Fetch one icon and render it in the format you need instead of hand-writing SVG. Formats: svg (default), svg-path, jsx, react-mdi, js-constant, data-uri. Records the icon in the project inventory and warns if it breaks coherence with the pinned library. |
| download_icons | Download one or more icons to disk as .svg files (or a JSON map of svg/data-uri) into outputDir. Enforces the pinned library for coherence and records them in the project inventory. |
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 1 tool
With only one tool, there is no risk of confusion between tools. The single tool has a clear, distinct purpose.
With only one tool, there are no inconsistencies. The name 'project_icon_status' follows a clear pattern of resource_action.
A single tool is too few for a server presumably managing icon libraries. Users would expect additional operations like adding or removing icons, making the toolset feel incomplete.
The server only offers a status-checking tool, lacking any mutating operations (create, update, delete) for icons or projects. This severely limits usability and represents a major gap in the tool surface.