Skip to main content
Glama
Leee62
by Leee62
README.md
# pickapicon-mcp

![logo](./media/logo.png)

[![smithery badge](https://smithery.ai/badge/@Leee62/pickapicon-mcp)](https://smithery.ai/server/@Leee62/pickapicon-mcp)
[![中文文档](https://img.shields.io/badge/中文文档-查看-orangered)](README_cn.md)
[![English](https://img.shields.io/badge/English-Read-greenyellow)](README.md)

## Description

This is a mcp for FE/UI/Designer to get SVG By Iconify API.

By using pickapicon-mcp, You just need to ask LLMs to get what you need instead of going to the website to find svg and copying stupidly.

It can make your workflow to get svg simplify, Dancing with MCP & LLMs 😎.

**👉👉 Icon Repo WebSite [Iconify](https://icon-sets.iconify.design/) 👈👈**

## Tools

- get_icon_repos

  - get all repo name, for other tools param `<prefix>`

- get_icons_by_desc_and_prefix

  - get icons by inputting desc what you want and prefix
  - inputs:
    - desc: desc what you want
    - prefix?: prefix <DEFAULT env.PREFIX>

- get_icon_detail_by_prefix_and_name
  - get icon detail (SVG code) by prefix and svg name
  - inputs:
    - svg_name: svg name
    - prefix?: prefix <DEFAULT env.PREFIX>

## QuickStart

### Installing via Smithery

To install Pickapicon MCP for Claude Desktop automatically via [Smithery](https://smithery.ai/server/@Leee62/pickapicon-mcp):

```bash
npx -y @smithery/cli install @Leee62/pickapicon-mcp --client claude
```

this is MCP Server Config

```json
  "mcpServers": {
    "pickapicon-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "pickapicon-mcp@latest"
      ],
      "env": {
        "PREFIX": "<LIKE ant-design>"
      }
    }
  }
```

## Case

- Quickly get svgs about COMPONENT / PAGE
  ![case2](./media/en_case_2.jpg)
- get svg with Modern Design Color
  ![case1](./media/en_case_1.jpg)

## License

MIT

TDQS

B3/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: one retrieves details for a specific icon, one lists all icon repositories, and one searches icons by description and prefix. There is no overlap in functionality, making it easy for an agent to select the correct tool.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with 'get_' prefix and descriptive suffixes (e.g., get_icon_detail_by_prefix_and_name, get_icon_repos, get_icons_by_desc_and_prefix). The naming is uniform and predictable throughout.

Tool Count4/5

With 3 tools, the count is appropriate for a focused icon retrieval service, though it feels slightly minimal. Each tool serves a distinct function, but the scope might benefit from additional utilities like listing icons by repository or updating metadata.

Completeness3/5

The tools cover basic retrieval (details, repos, search), but there are notable gaps for a full icon management system, such as creating, updating, or deleting icons or repositories. The surface is functional but incomplete for advanced workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues