MCP server

Keyline Icons MCP Server for AI Coding Agents

The Keyline Icons MCP server lets an AI coding agent search a 1,507-icon set, read SVG source and get the matching React import without guessing names.

Run
claude mcp add keyline-icons -- npx -y @keyline-icons/mcp
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is the Keyline Icons MCP server?

Keyline Icons MCP is a stdio server shipping with the full Keyline Icons set: 1,507 names across stroke, two-tone, duotone and fill styles, rounded or sharp corners. An agent searches by name, reads full SVG source for a style and corner treatment, or gets the React import line, all offline with no API key.

The Keyline Icons MCP server is the package @keyline-icons/mcp. It lets an agent search the Keyline Icons set, read an icon's full SVG source and get the matching React import, so a prompt names a real icon instead of guessing one.

The whole icon set ships inside the package. There is no API key and no network call, so a search or an SVG read returns instantly and works offline.

What the set covers

  • 1,507 names drawn on one 24x24 grid, each in stroke, two-tone, duotone and fill styles.
  • Every drawing comes in rounded and sharp corners, for 12,056 SVGs in total.
  • Containers: 64 icons also exist in a square- form and 69 in a circle- form, wrapping the base drawing.
  • A glyph with nothing to fill, such as bar-chart, still returns its stroke drawing in the filled styles.

How naming and search work

Compound names read base-first, so a mail icon with a tick is mail-check, not check-mail. Search ranks exact matches over prefix, word-boundary and substring matches, and a miss falls back to edit distance, so chekc still suggests check.

Who it is for

Best for

  • Projects already using shadcn/ui that want an agent to pull a verified icon name and SVG instead of inventing one.
  • Teams who want a React import returned alongside the icon, including the sharp and duotone entry points.
  • Anyone who wants icon search to work with no account, no key and no network round trip.

Not for

  • If your job is turning an SVG into Android Vector Drawable XML, SVG to Android Vector is the better fit for that job.
  • When the task is turning a folder of SVG icons into icon fonts, SVG to icon fonts is the better fit for that work.
  • When you want a shadcn look without any React at all, Basecoat UI MCP is the better fit for that stack.
  • When you build with shadcn-svelte and need live component docs, shadcn-svelte MCP is the better fit for that stack.