heroicons-mcp

Created By
SeeYangZhia year ago
heroicons-mcp is a Model Context Protocol (MCP) server that exposes Heroicons. It allows LLMs and agentic applications to search, list, and generate usage examples of icons in React applications.
Overview

What is Heroicons MCP?

Heroicons MCP is a Model Context Protocol (MCP) server that provides access to Heroicons, a library of hand-crafted SVG icons, for Large Language Models (LLMs) and agentic applications. It enhances visual communication and design capabilities by allowing users to search for icons by name or category.

How to use Heroicons MCP?

To use Heroicons MCP, clone the repository, install Bun, and run the server in either HTTP or stdio mode. You can integrate it with clients like Claude Desktop by configuring the MCP server settings.

Key features of Heroicons MCP?

  • Exposes Heroicons as MCP resources (Outline and Solid styles)
  • Tools for searching icons by name or keywords
  • Listing all icons or icons within a specific style
  • Integration ready with Claude Desktop and other MCP clients
  • Can be run as an HTTP server or a stdio-based MCP server

Use cases of Heroicons MCP?

  1. Assisting developers in finding and using icons in their applications.
  2. Enhancing AI tools with visual resources for better user interaction.
  3. Streamlining design workflows by providing easy access to icon libraries.

FAQ from Heroicons MCP?

  • Can I use Heroicons MCP with any AI tool?

Yes! Heroicons MCP is designed to work with any tool that supports the Model Context Protocol.

  • Is there a cost to use Heroicons MCP?

No! Heroicons MCP is free to use.

  • What are the prerequisites for running Heroicons MCP?

You need Git and Bun installed to run the server.

Server Config

{
  "mcpServers": {
    "heroicons": {
      "command": "npx",
      "args": [
        "heroicons-mcp",
        "--stdio"
      ]
    }
  }
}
Project Info
Hosted
Created At
a year ago
Updated At
a year ago
Author Name
SeeYangZhi
Star
0
Language
TypeScript
License
MIT license
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

3 hours ago
Myrsu
@VidhiJav

2 days ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago