Skip to directory

About Icons8 MCP

A hosted MCP server for searching and retrieving Icons8 icons and animations for design and coding workflows.

What you can use it for

  • Search icons by concept, category, platform, or style
  • Retrieve PNG icon URLs and animations
  • Build consistent icon selections for interfaces
Connection and setup
Hosting
Remote hosted
Transport
Streamable HTTP
Endpoint
https://mcp.icons8.com/mcp/
Authentication
OAuth; account plan governs asset formats.

Requirements

  • MCP client supporting remote Streamable HTTP, or Node.js for the documented mcp-remote bridge
  • Icons8 account for OAuth/API key flows

Setup steps

  1. For native remote HTTP clients, add https://mcp.icons8.com/mcp/ as a Streamable HTTP server.
  2. Complete Icons8 sign-in when the client opens the OAuth browser flow.
  3. For a stdio-only client, use npx mcp-remote https://mcp.icons8.com/mcp/ as the bridge and complete browser sign-in.
  4. If OAuth is unavailable, use a protected API key as an Authorization Bearer header; do not store it in shared source-controlled config.
Tools 5+

Names are representative and the available output depends on account plan: PNG is available on free accounts while SVG requires a paid plan. Current hosted endpoint uses OAuth at https://mcp.icons8.com/mcp/.

  • search_icons
    01
  • list_categories
    02
  • list_platforms
    03
  • get_icon_png_url
    04
  • get_icon_animation
    05

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

Limitations and notes
  • Older GitHub README describes SSE and plan details that conflict with the newer current product page. Use the product page endpoint and Streamable HTTP/OAuth instructions.
  • Some asset formats/features may require account entitlement; plan details can change.
Source discrepancies
  • The older repository README describes SSE, unauthenticated PNG access, and paid SVG access, while the current product page documents Streamable HTTP and OAuth 2.1/API-key authentication. This record follows the current product page for connection/auth and retains the discrepancy.
Original sources
  • official tool reference

    Current official docs use OAuth at the hosted MCP endpoint; account plan gates PNG versus SVG access. Stored tool names are representative; catalog breadth is accessed through search tools.

  • official documentation

    Current official docs use OAuth at the hosted MCP endpoint; account plan gates PNG versus SVG access. Stored tool names are representative; catalog breadth is accessed through search tools.

Documentation checked 2026-10-28T13:02:00.000Z. Connection has not been runtime tested.

Similar tools