Hugeicons MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Hugeicons MCP Server?

Hugeicons MCP Server is a TypeScript-based server designed to facilitate the integration of Hugeicons into various platforms, providing tools and resources for developers.

how to use Hugeicons MCP Server?

To use the Hugeicons MCP Server, you can run it directly using npx or configure it with Claude Desktop by adding the server configuration to the appropriate JSON file.

key features of Hugeicons MCP Server?

  • Icon discovery and search functionality.
  • Platform-specific installation guides for React, Vue, Angular, Svelte, React Native, and Flutter.
  • Comprehensive documentation including usage examples and component props.

use cases of Hugeicons MCP Server?

  1. Integrating Hugeicons into web applications using various frameworks.
  2. Providing developers with easy access to icon resources and documentation.
  3. Facilitating the installation and usage of Hugeicons in different environments.

FAQ from Hugeicons MCP Server?

  • What platforms does Hugeicons support?

Hugeicons supports multiple platforms including React, Vue, Angular, Svelte, React Native, and Flutter.

  • Is there a way to debug the MCP server?

Yes! You can use the MCP Inspector for debugging, which provides a URL to access debugging tools in your browser.

  • How do I install the Hugeicons MCP Server?

You can install it by running npm install and then build the server using npm run build. Alternatively, you can run it directly with npx @hugeicons/mcp-server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
MIT license

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)

a day ago