developer-tools

MCP Advisor

istarwyh

by istarwyh

MCP Advisor helps you discover and understand MCP services quickly with natural language queries and advanced semantic s

Discovery and recommendation service that helps find and understand available MCP services based on natural language queries, supporting multiple search backends for exploring servers by semantic similarity.

github stars

82

0 commentsdiscussion

Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.

best for

  • / General purpose MCP workflows

capabilities

  • / recommend-mcp-servers
  • / install-mcp-server

what it does

Discovery and recommendation service that helps find and understand available MCP services based on natural language queries, supporting multiple search backends for exploring servers by semantic similarity.

about

MCP Advisor is a community-built MCP server published by istarwyh that provides AI assistants with tools and capabilities via the Model Context Protocol. MCP Advisor helps you discover and understand MCP services quickly with natural language queries and advanced semantic s It is categorized under developer tools. This server exposes 2 tools that AI clients can invoke during conversations and coding sessions.

how to install

You can install MCP Advisor in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport. This server supports remote connections over HTTP, so no local installation is required.

license

MIT

MCP Advisor is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.

readme

MCP Advisor

Model Context Protocol npm version License: MIT DeepWiki Install with VS Code smithery badge

<!-- DeepWiki badge generated by https://deepwiki.ryoppippi.com/ -->

Verified on MseeP MCP Badge

<a href="https://glama.ai/mcp/servers/@istarwyh/mcpadvisor"> <img width="380" height="200" src="https://glama.ai/mcp/servers/@istarwyh/mcpadvisor/badge" alt="Advisor MCP server" /> </a>

English | 简体中文

Introduction

MCP Advisor is a discovery and recommendation service that helps AI assistants explore Model Context Protocol (MCP) servers using natural language queries. It makes it easier for users to find and leverage MCP tools suitable for specific tasks.

User Stories

  1. Discover & Recommend MCP Servers

    • As an AI agent developer, I want to quickly find the right MCP servers for a specific task using natural-language queries.
    • Example prompt: "Find MCP servers for insurance risk analysis"
  2. Install & Configure MCP Servers

    • As a regular user who discovers a useful MCP server, I want to install and start using it as quickly as possible.
    • Example prompt: "Install this MCP: https://github.com/Deepractice/PromptX"

Demo

https://github.com/user-attachments/assets/7a536315-e316-4978-8e5a-e8f417169eb1

Usage

Once configured, the Nacos provider will be automatically enabled and used when searching for MCP servers. You can query it using natural language, for example:

Find MCP servers for insurance risk analysis

Or more specifically:

Search for MCP servers with natural language processing capabilities

Documentation Navigation

Quick Start

Installation

The fastest way is to integrate MCP Advisor through MCP configuration:

{
  "mcpServers": {
    "mcpadvisor": {
      "command": "npx",
      "args": ["-y", "@xiaohui-wang/mcpadvisor"]
    }
  }
}

Add this configuration to your AI assistant's MCP settings file:

  • MacOS/Linux: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %AppData%\Claude\claude_desktop_config.json

Installing via Smithery

To install Advisor for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @istarwyh/mcpadvisor --client claude

For more installation methods and detailed configuration, see the Quick Start Guide.

Optional: Local Meilisearch (improves recommendations)

To boost recommendation quality, you can run a local Meilisearch instance:

pnpm meilisearch:start

This starts Meilisearch at http://localhost:7700, bootstraps the mcp_servers index from local data, and persists environment variables to ~/.meilisearch/env. Load them in your current shell with:

source ~/.meilisearch/env

Or enable it automatically with a single flag when launching MCPAdvisor (no manual env needed):

{
  "mcpServers": {
    "mcpadvisor": {
      "command": "npx",
      "args": ["-y", "@xiaohui-wang/mcpadvisor", "--local-meilisearch"]
    }
  }
}

Developer Guide

Architecture Overview

MCP Advisor adopts a modular architecture with clean separation of concerns and functional programming principles. The codebase has been recently refactored (2025) to improve maintainability and scalability:

graph TD
    Client["Client Application"] --> |"MCP Protocol"| Transport["Transport Layer"]
    
    subgraph "MCP Advisor Server"
        Transport --> |"Request"| SearchService["Search Service"]
        SearchService --> |"Query"| Providers["Search Providers"]
        
        subgraph "Search Providers"
            Providers --> MeilisearchProvider["Meilisearch Provider"]
            Providers --> GetMcpProvider["GetMCP Provider"]
            Providers --> CompassProvider["Compass Provider"]
            Providers --> NacosProvider["Nacos Provider"]
            Providers --> OfflineProvider["Offline Provider"]
        end
        
        OfflineProvider --> |"Hybrid Search"| HybridSearch["Hybrid Search Engine"]
        HybridSearch --> TextMatching["Text Matching"]
        HybridSearch --> VectorSearch["Vector Search"]
        
        SearchService --> |"Merge & Filter"| ResultProcessor["Result Processor"]
        
        SearchService --> Logger["Logging System"]
    end

Project Structure

The codebase follows clean architecture principles with organized directory structure:

src/
├── services/
│   ├── core/                    # Core business logic
│   │   ├── installation/        # Installation guide services
│   │   ├── search/             # Search providers
│   │   └── server/             # MCP server implementation
│   ├── providers/              # External service providers
│   │   ├── meilisearch/        # Meilisearch integration
│   │   ├── nacos/              # Nacos service discovery
│   │   ├── oceanbase/          # OceanBase vector database
│   │   └── offline/            # Offline search engine
│   ├── common/                 # Shared utilities
│   │   ├── api/                # API clients
│   │   ├── cache/              # Caching mechanisms
│   │   └── vector/             # Vector operations
│   └── interfaces/             # Type definitions
├── types/                      # TypeScript type definitions
├── utils/                      # Utility functions
└── tests/                      # Test suites
    ├── unit/                   # Unit tests
    ├── integration/            # Integration tests
    └── e2e/                    # End-to-end tests

Core Components

  1. Search Service Layer

    • Unified search interface and provider aggregation
    • Support for multiple search providers executing in parallel
    • Configurable search options (limit, minSimilarity)
  2. Search Providers

    • Meilisearch Provider: Vector search using Meilisearch
    • GetMCP Provider: API search from the GetMCP registry
    • Compass Provider: API search from the Compass registry
    • Nacos Provider: Service discovery integration
    • Offline Provider: Hybrid search combining text and vectors
  3. Hybrid Search Strategy

    • Intelligent combination of text matching and vector search
    • Configurable weight balancing
    • Smart adaptive filtering mechanisms
  4. Transport Layer

    • Stdio (CLI default)
    • SSE (Web integration)
    • REST API endpoints

For more detailed architecture documentation, see ARCHITECTURE.md.

Developer Quick Start

Development Environment Setup

  1. Clone the repository
  2. Install dependencies:
    pnpm install
    
  3. Build the project:
    pnpm run build
    
  4. Configure environment variables (see Quick Start Guide)

Testing

MCP Advisor includes comprehensive testing suites to ensure code quality and functionality. For detailed testing information including unit tests, integration tests, end-to-end testing, and manual testing procedures, see the Technical Reference.

Testing

Run compr


FAQ

What is the MCP Advisor MCP server?
MCP Advisor is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
How do MCP servers relate to agent skills?
Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
How are reviews shown for MCP Advisor?
This profile displays 72 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.6 out of 5—verify behavior in your own environment before production use.

Use Cases

Extended AI Capabilities

Add new capabilities to Claude beyond text generation

Example

Access external data sources, execute code, interact with tools and services

Transform Claude from chatbot to action-taking agent

Context Enhancement

Provide Claude with access to relevant context and data

Example

Load project documentation, access knowledge bases, query databases

Get more accurate, context-aware responses

Workflow Automation

Automate multi-step workflows combining AI and external tools

Example

Research → Summarize → Create document → Send notification

Complete complex tasks end-to-end without manual steps

Implementation Guide

Prerequisites

  • Claude Desktop 0.7.0+ or Cursor IDE with MCP support
  • Basic understanding of MCP architecture and capabilities
  • Access credentials for integrated services (if required)
  • Willingness to experiment and iterate on configuration

Time Estimate

15-60 minutes depending on server complexity

Installation Steps

  1. 1.Install MCP server: npm install -g [package-name] or via GitHub
  2. 2.Add server configuration to ~/.claude/mcp.json
  3. 3.Provide required credentials and configuration
  4. 4.Restart Claude Desktop to load new server
  5. 5.Test basic functionality with simple prompts
  6. 6.Explore capabilities and experiment with use cases
  7. 7.Document successful patterns for reuse

Troubleshooting

  • MCP server not loading: Check config syntax, verify installation
  • Connection errors: Check network, firewall, credentials
  • Feature not working: Read server docs, check required parameters
  • Performance issues: Monitor resource usage, check for network latency
  • Conflicts with other servers: Check port assignments, namespace collisions

Best Practices

✓ Do

  • +Read server documentation thoroughly before setup
  • +Start with simple use cases to validate functionality
  • +Test in non-production environment first
  • +Monitor resource usage and performance
  • +Keep servers updated for bug fixes and new features
  • +Document configuration for team members
  • +Use environment variables for sensitive configuration

✗ Don't

  • Don't grant overly permissive access to MCP servers
  • Don't skip reading security considerations in docs
  • Don't expose sensitive data without proper controls
  • Don't run untrusted MCP servers without code review
  • Don't ignore error messages—investigate root cause

💡 Pro Tips

  • Combine multiple MCP servers for powerful workflows
  • Create custom MCP servers for your specific needs
  • Share successful configurations with team
  • Use MCP inspector for debugging
  • Join MCP community for tips and troubleshooting

Technical Details

Architecture

Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.

Protocols

  • Model Context Protocol (MCP)
  • JSON-RPC 2.0
  • stdio or HTTP transport

Compatibility

  • Claude Desktop
  • Cursor IDE
  • Custom MCP clients

When to Use This

✓ Use When

Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.

✗ Avoid When

Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.

Integration

  • Tool composition: Chain multiple MCP tools in workflows
  • Context augmentation: Provide AI with relevant external data
  • Action delegation: Let AI execute tasks on external systems
  • Bidirectional sync: Keep AI context and external systems in sync

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.

List & Promote Your MCP Server

Share your MCP server with the developer community

GET_STARTED →
MCP server reviews

Ratings

4.672 reviews
  • Amelia Zhang· Dec 28, 2024

    We evaluated MCP Advisor against two servers with overlapping tools; this profile had the clearer scope statement.

  • Noah Sharma· Dec 20, 2024

    I recommend MCP Advisor for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.

  • Valentina Ghosh· Dec 20, 2024

    According to our notes, MCP Advisor benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.

  • Shikha Mishra· Dec 16, 2024

    MCP Advisor reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Amelia Abebe· Dec 16, 2024

    MCP Advisor reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Amelia Liu· Dec 12, 2024

    MCP Advisor is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.

  • Benjamin Zhang· Dec 8, 2024

    MCP Advisor has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Noah Shah· Dec 4, 2024

    MCP Advisor has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Mateo Gonzalez· Nov 23, 2024

    MCP Advisor is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.

  • Amelia Diallo· Nov 19, 2024

    We wired MCP Advisor into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.

showing 1-10 of 72

1 / 8