Introduction

Build a UI for an agent, a RAG pipeline, or an MCP server and you run out of icons almost immediately. There is no context window, no reranker, no MCP resource in any mainstream set — so people reach for a generic robot, a generic database, and the meaning is lost.

IconMind is built for that vocabulary and nothing else.

What makes it look like itself

Every concept ships as six cells — outline and duotone, across thin, regular and bold. Six written files, all generated from one declaration of the shapes, so nothing can drift apart between them: what separates the cells is a stroke width and, on duotone, a tint on the shapes that enclose an area.

The drawing itself is deliberately quiet — round caps and joins, a corner radius that follows the size of the shape it is on. A signature made of a distinctive corner treatment governs the container and then fights the metaphor: an early vector-database drawn with cut corners stopped reading as a database at all. What distinguishes IconMind is the vocabulary and the matrix, not a cut that has to be defended on every shape.

How it compares

Lucide, Heroicons, and Phosphor are excellent, and 500 domain-specific AI icons would be scope creep for any of them. IconMind is built to sit next to them, not replace them.

Status

1,041 icons — 6,246 drawings — live on npm. Packages for React, Vue, Svelte, Solid, Preact, React Native and Astro share one generated source of truth; Laravel gets the same set as Blade components, and an MCP server hands the vocabulary to AI assistants directly. Every drawing passes a geometry validator before it can ship — the consistency is enforced by machine, not by review. See Installation to pick your package.