IconMCP accepts icon requests and redraws from people and agents
IconMCP now accepts icon requests, reports and redraws from people or their agents. Community revisions face voting and blind judging, alongside automated spacing checks and comparisons at actual display sizes.

TL;DR
- IconMCP now accepts missing-icon requests, reports and redraws from people or their agents, as creativedash announced.
- Community redraws face voting and blind comparison against the current icon; winners ship with agent credit, according to the contribution announcement.
- Small-size consistency gets explicit checks: creativedash describes fixed 1px padding, neighbour previews at 16px and judging at actual display sizes.
The live gallery, shared by creativedash, tracks agents refining everything from fries to cheque-deposit icons. The agent setup page provides a one-command Claude Code connection to its MCP endpoint.
Requests and community revisions
People and their agents can contribute through three named actions:
request_icon: ask for an icon that does not exist yet.report_icon: flag an existing icon that looks wrong.fix_icon: draw a better version of an existing icon.
Each submitted fix appears as a community revision on the icon. From there, the review process runs through three steps:
- People can upvote or downvote the revision.
- A judge compares it blind against the current icon.
- If the revision wins, it becomes the published icon, credited to the agent that drew it.
Grid and duplicate checks
The agents build icons within a shared design system, with checks extending across the library:
- Construction: the same grid, keylines, stroke and corner rules, often using shared parts.
- Duplicate detection: every change goes through a near-duplicate scan of the whole library.
- Validation: weight and size checks accompany a judge that rejects off-system designs.
16-pixel judging
Optical sizing gets a separate set of controls:
- Shared keylines and fixed 1px padding are checked automatically on every change.
- Before submitting, each agent sees its icon beside neighbouring icons at 16px and is told to match them.
- The judge compares versions at 64, 24 and 16 actual pixels, a welcome bit of pixel-level fussiness.
MCP access
IconMCP's original launch set a goal of 100,000 icons, with 12 agents drawing and refining around the clock. The announcement offered coding agents access to every icon through MCP and described the license as “Do what you wish.”
The setup page supplies this Claude Code command: