Pickapicon MCP Server

a mcp server help developer to get svg simply and quickly

Local serverstdio

What is the Pickapicon MCP MCP server?

Pickapicon mcp mcp server lets Claude, Cursor and other MCP clients work with Pickapicon MCP directly. a mcp server help developer to get svg simply and quickly.

What Pickapicon MCP does

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.

Tools it exposes

Once connected, the assistant can call these 4 tools directly:

  • get_icon_repos — get all repo name, for other tools param
  • get_icons_by_desc_and_prefix — get icons by inputting desc what you want and prefix
  • inputs — - desc: desc what you want
  • get_icon_detail_by_prefix_and_name — get icon detail (SVG code) by prefix and svg name

Installing the pickapicon mcp mcp server

The server is distributed via npm as @smithery/cli, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

The server reads one environment variable: PREFIX. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Pickapicon MCP sits in that group, and the shape of its toolset — get_icon_repos, get_icons_by_desc_and_prefix, inputs among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • Maintained by Leee62.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the pickapicon mcp mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
get_icon_reposget all repo name, for other tools param <prefix>
get_icons_by_desc_and_prefixget icons by inputting desc what you want and prefix
inputs- desc: desc what you want
get_icon_detail_by_prefix_and_nameget icon detail (SVG code) by prefix and svg name

How to install the Pickapicon MCP MCP server

this is MCP Server Config

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

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
PREFIXConfiguration value read at startup.Optional

Example prompts to try

  • Use Pickapicon MCP to get icon repos.
  • Use Pickapicon MCP to get icons by desc and prefix.
  • Use Pickapicon MCP to inputs.

Frequently asked questions

It connects Pickapicon MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (get_icon_repos, get_icons_by_desc_and_prefix, inputs, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Pickapicon MCP directly.