Skip to main content
Glama
pipeworx-io

mcp-iconify

by pipeworx-io

mcp-iconify

Iconify MCP — wraps the Iconify public API (free, no auth)

Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.

Tools

Tool

Description

search_icons

Search for icons by keyword across all collections. Returns icon names in prefix:name format (e.g., "mdi:home"). Use get_icons to fetch SVG data for results.

get_icons

Get SVG code and dimensions for specific icons. Input icon names in prefix:name format (e.g., "mdi:home", "fa:star"). Returns SVG markup, width, and height.

list_collections

Browse available icon collections. Returns prefix, name, icon count, author, license, and category. Use the prefix with search_icons or get_icons.

Related MCP server: Iconify MCP Server

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "iconify": {
      "url": "https://gateway.pipeworx.io/iconify/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/iconify/mcp returns the tools in the table above plus the shared Pipeworx meta-toolsask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1476+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Iconify data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Related MCP Connectors

Related MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    Provide access to Iconify's MCP server with over 200,000 open-source vector ICONS, supporting icon set browsing, searching, and obtaining multi-framework usage examples.
    4
    2
    Apache 2.0
  • A
    license
    Not graded
    quality
    D
    maintenance
    Provides access to over 200,000 open-source vector icons from more than 200 icon sets via the Iconify API. It enables users to browse, search, and retrieve specific icon data along with usage examples for popular web frameworks like React, Vue, and Tailwind CSS.
    256 npm
    15
    GPL 3.0
  • A
    license
    A
    quality
    D
    maintenance
    Provides access to Iconify's 200,000+ open source vector icons from 200+ icon sets, enabling search, browsing, and retrieval of icon data with framework usage examples.
    4
    6 npm
    MIT