Mcp Advisor

Created By
istarwyha year ago
Overview

What is MCP Advisor?

MCP Advisor is a discovery and recommendation service designed to assist AI assistants in exploring Model Context Protocol (MCP) servers through natural language queries. It simplifies the process of finding and utilizing MCP tools tailored for specific tasks.

How to use MCP Advisor?

To use MCP Advisor, you can query it using natural language, such as asking it to find MCP servers for a specific application. For example, you can input: "Find MCP servers for insurance risk analysis". The service will then recommend relevant MCP servers based on your query.

Key features of MCP Advisor?

  • Service Discovery: Automatically discovers MCP servers registered in Nacos.
  • Vector Search: Utilizes semantic search to identify the most relevant MCP servers for a given query.
  • Real-time Updates: Keeps the server list up-to-date by periodically syncing with Nacos.
  • Fallback Search: Provides keyword search as a backup if vector search is unavailable.

Use cases of MCP Advisor?

  1. Quickly finding the right MCP servers for specific tasks.
  2. Assisting AI developers in integrating MCP servers into their applications.
  3. Enabling users to install and configure MCP servers efficiently.

FAQ from MCP Advisor?

  • Can MCP Advisor help with all types of MCP servers?

Yes! MCP Advisor is designed to assist with a wide range of MCP servers across various applications.

  • Is MCP Advisor free to use?

Yes! MCP Advisor is free to use for everyone.

  • How accurate are the recommendations?

The accuracy of recommendations depends on the specificity of the queries and the availability of registered MCP servers.

Server Config

{
  "mcpServers": {
    "mcpadvisor": {
      "command": "npx",
      "args": [
        "-y",
        "@xiaohui-wang/mcpadvisor"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
istarwyh
Star
-
Language
-
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