RemixIcon MCP
OfficialClick on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@RemixIcon MCPfind icons for user, profile, and account"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
RemixIcon MCP
English | 简体中文
A lightweight Model Context Protocol (MCP) server that maps icon-focused keywords directly to Remix Icon metadata. Provide concise keywords (up to 20), receive the top 5 matching icon names and metadata – clean architecture with FlexSearch-powered local search.
Features
Smart Keyword Input – Supports up to 20 comma-separated keywords while rejecting natural-language sentences for optimal search quality.
Fixed Top-5 Results – Returns exactly 5 most relevant icons for focused decision-making.
FlexSearch-backed Index – Uses FlexSearch v0.8's document index for high-performance token lookup over the local Remix Icon catalog.
Clean Architecture – Domain entities, application use cases, infrastructure adapters, and MCP interface remain isolated for easy testing.
CLI Ready – Can be run as a standalone CLI tool via
npx remixicon-mcpor integrated into MCP clients.LLM-ready Responses – Returns ranked candidates, matched tokens, and explicit guidance instructing the model to choose exactly one icon.
Related MCP server: CodeRAG
Quick Start
Installation
# Install as CLI tool globally
npm install -g remixicon-mcp
# Or run directly with npx
npx remixicon-mcp
# For development
pnpm install
pnpm typecheck
pnpm testUsage
As a Standalone CLI Tool
You can run the MCP server directly via stdio for testing or integration:
# Run with npx
npx remixicon-mcp
# Or if installed globally
remixicon-mcpPlatform Setup
Claude Desktop
Configuration
Add the following to your claude_desktop_config.json:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"remix-icon": {
"command": "npx",
"args": ["-y", "remixicon-mcp"]
}
}
}Setup Steps
Save the configuration file
Completely quit and restart Claude Desktop
The
search_iconstool will be available in your conversations
Claude Code
Option 1: Marketplace Plugin (Recommended)
# In Claude Code, add the marketplace plugin
/plugin marketplace add Remix-Design/remixicon-mcpBenefits:
Automatic installation and updates
Complete plugin metadata and versioning
Rich discovery with keywords and categorization
Full integration with Claude Code's plugin ecosystem
Option 2: Manual Configuration
# Quick command-line setup
claude mcp add --transport stdio remixicon -- npx -y remixicon-mcpOr manually add to your project's .claude/settings.json:
{
"mcp": {
"servers": {
"remix-icon": {
"command": "npx",
"args": ["-y", "remixicon-mcp"]
}
}
}
}Setup Steps
Choose one of the installation methods above
Restart Claude Code for the changes to take effect
The
search_iconstool will be available in your sessions
Codex
Configuration
# Quick command-line setup
codex mcp add remixicon -- npx -y remixicon-mcpSetup Steps
Run the installation command above
Restart Codex for the changes to take effect
The
search_iconstool will be available in your conversations
Available Tools
The server communicates over stdio using JSON-RPC 2.0 via the official @modelcontextprotocol/sdk and exposes a single tool:
search_icons
Input: keywords string (comma-separated, up to 20 keywords)
Output: Top 5 most relevant icons with metadata
Format: Human-readable summary + structured metadata
Example Usage
JSON-RPC Call:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "search_icons",
"arguments": {
"keywords": "layout, grid, design"
}
}
}Sample Response: The server returns the top 5 icons that match your keywords, complete with names, categories, and usage information.
Project Structure
.
├── bin/
│ └── run.cjs # CLI entry point for npx execution
├── src/
│ ├── cli/ # CLI runner implementation
│ ├── bootstrap/ # Dependency wiring for Clean Architecture boundaries
│ ├── domain/ # Icon entities and keyword parser
│ ├── application/ # Search use case orchestrating validation and ranking
│ ├── infrastructure/search/ # FlexSearch-backed repository implementation
│ ├── interface/mcp/ # MCP server built with @modelcontextprotocol/sdk
│ └── data/tags.json # Remix Icon tags for search functionality
├── tests/ # Vitest suites covering parser and use case behaviour
├── .claude-plugin/
│ └── marketplace.json # Marketplace metadata for Claude Code plugin discovery
├── package.json # pnpm-friendly manifest and scripts
└── tsconfig.json # Strict TypeScript configuration with Node typingsImplementation Notes
Keywords are parsed with Unicode-aware boundaries, supporting up to 20 comma-separated keywords while rejecting sentence-style inputs.
Enhanced detection differentiates between keyword lists (with delimiters) and natural language sentences (space-separated phrases).
FlexSearch indexes icon names, tags, usage, and categories; field weights plus token matches drive deterministic scores.
Fixed top-5 results provide focused, relevant matches without configuration complexity.
The application layer combines parser validation, repository queries, and response formatting so the interface only handles transport concerns.
MCP responses include natural-language guidance and machine-readable matches so LLM clients can choose exactly one icon.
CLI runner enables standalone execution via
npxor global installation for easy integration.
Development Scripts
pnpm typecheck # Strict TypeScript check (tsc --noEmit)
pnpm test # Run Vitest suites
pnpm exec biome check --write --unsafe # Format + fix code with BiomeLicense
Available Tools
1 toolsearch_iconsSearch Remix Icons by keywordA
Search Remix Icon metadata using comma-separated keywords (up to 20 keywords). Returns top 5 most relevant icons. Supports both single keywords and keyword lists. Avoid natural language sentences. Returns format: 'icon-name (score)'. Example: 'sun-fill (46.00)'.
| Name | Required | Description | Default |
|---|---|---|---|
| keywords | Yes | Comma-separated keywords to search for icons (e.g., 'summer, sun, beach') |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, but description fully covers behavior: returns top 5 results, formatted output, keyword constraints. It implies read-only search, sufficient for the tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Four concise sentences, no redundant information, front-loaded with essential use case.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Single parameter with full schema description, no output schema needed; description covers constraints, usage, and expected output format. Complete for the tool's complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers parameter description (100%), but description adds value: keyword limit, natural language avoidance, output format example. Adds meaning beyond schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool searches Remix Icon metadata using keywords, with specific verb 'search' and resource 'Remix Icon metadata'. It also details output format and constraints.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides explicit guidance on using comma-separated keywords, limit of 20, avoiding natural language, and that it returns top 5 results. No need for exclusions due to lack of sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v1.2.0- Changed
search_icons1 field changed- removed
Input schema / additionalPropertiesRemoved value: -false
1 tool update
- First observed
search_icons
TDQS
With only one tool, there is no possibility of confusion between tools. The single tool 'search_icons' is uniquely defined.
Only one tool exists, so naming consistency is perfect by definition. The name 'search_icons' follows a clear verb_noun pattern.
A single tool for an icon library is far too few. Expected tools would include retrieving icon details, metadata, or categories, making this feel incomplete and overly thin.
The server only offers search functionality with no way to access actual icon data, details, or categories. This is severely incomplete for a domain that clearly requires more operations.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Capability registry for the agentic economy. Semantic search over verified MCP server listings.
Search 77,000+ MCP servers ranked by real adoption data to find the right one for any task.
Token-free MCP server for structured RevoGrid Core, Pro, and Enterprise knowledge retrieval.
Related MCP Servers
- AlicenseBqualityDmaintenanceMCP server that allows FE/UI/Designers to retrieve SVG icons via the Iconify API by simply asking LLMs rather than manually searching websites.3304MIT
- AlicenseNot gradedqualityAmaintenanceA high-performance MCP server providing lightning-fast hybrid code search using TF-IDF and vector embeddings for AI assistants. It enables real-time codebase indexing and semantic retrieval with sub-50ms latency and offline support.12MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server for semantic SVG icon search. Generate infographic SVG icons by keyword — over 100,000 icons with semantic search support.120MIT
- AlicenseNot gradedqualityCmaintenanceLocal, free MCP server for brand logo search and shadcn/ui component search & source lookup, requiring no API keys or login.MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Remix-Design/RemixIcon-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server