IconSearch logoIconsearch
Icon systems for coding agents
Available on npm · v0.2.0

Give your agent an icon system—not another guess.

Search 355,702 production-ready icons across 229 collections, save approved SVGs with your code, and keep every screen visually consistent.

You

Build the billing settings screen using our approved icon system.

IconSearch project memory loaded
billing-historyLucide / receipt-text
automationsLucide / sparkles
agent-accessLucide / bot

Search by intent

Ask for “quiet empty state” or “billing history.” Deterministic concept ranking translates UI intent into useful candidates.

Remember every choice

Version-controlled semantic assignments prevent agents from choosing a different icon on every screen.

Audit before shipping

Detect missing managed files, checksum drift, inline SVGs, unmanaged assets, and mixed icon packages.

Your agent gets an icon workflow—not another search box.

  1. Read approved project icons and visual rules.
  2. Search IconSearch using semantic UI intent.
  3. Retrieve exact sanitized SVG and attribution.
  4. Save it under a stable semantic name.
  5. Audit the repository before the UI ships.
codex mcp add iconsearch -- npx -y @iconsearch/mcp-server

Published on npm as @iconsearch/mcp-server under the MIT License. Requires Node.js 20 or newer. Generate a revocable API key from your account, keep it out of your repository, and use it to connect your agent.

Your design decisions live with your code.

iconsearch.json is readable, reviewable, and portable. Humans approve it, agents follow it, and CI can audit it. Managed SVGs live beneath .iconsearch/icons.

See the manifest format
{
  "version": 1,
  "style": {
    "preferredLibraries": ["lucide"],
    "defaultSize": 20,
    "color": "currentColor",
    "strokeWidth": 2
  },
  "icons": {
    "billing-history": {
      "library": "lucide",
      "name": "receipt-text",
      "path": ".iconsearch/icons/billing-history.svg",
      "checksum": "sha256:…"
    }
  }
}
Local-first and bounded by design.Audits are read-only. Saves stay inside the validated project root and refuse symlink escapes.

Give your coding agent better visual judgment.