MCP Advisor for VS Code: Setup & Config

What you can do with MCP Advisor in VS Code

Pick it to discover task-relevant MCP servers without knowing their names in advance.

• Find task-specific MCP integrations from plain-language requests
• Add server discovery to a custom agent through SearchService

Before you start: MCP Advisor in VS Code

• npx
• An MCP-compatible client

Stdio is the default. Local Meilisearch is optional; the README also describes SSE and REST interfaces.

MCP Advisor VS Code configuration

1. Choose VS Code configuration scope

   For MCP Advisor, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

2. Add MCP Advisor to VS Code

   Use the mcpadvisor entry below in servers. Keep MCP Advisor's documented stdio connection fields and your other VS Code entries.

3. Check MCP Advisor in VS Code

   MCP Advisor: Start in VS Code’s MCP controls; inspect output and trust prompts.

{
  "servers": {
    "mcpadvisor": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@xiaohui-wang/mcpadvisor"
      ],
      "env": {}
    }
  }
}

MCP Advisor tools available to VS Code

MCP Advisor's stored tool list documents 2 tools; compare it with VS Code's connected tool list, because the stored list is not a live check.

recommend-mcp-servers

Look for recommend-mcp-servers among VS Code's agent-mode tools after starting MCP Advisor through the MCP controls.

Find candidate MCP servers for a task using registry and internal search sources.

install-mcp-server

Look for install-mcp-server among VS Code's agent-mode tools after starting MCP Advisor through the MCP controls.

MCP Advisor: full stored tool descriptions

Troubleshooting MCP Advisor in VS Code

• Make npx @xiaohui-wang/mcpadvisor (Node.js/npm) available in the workspace, container, or remote environment hosting MCP Advisor. Start through VS Code's MCP controls; inspect output and trust prompts.
• MCP Advisor uses stdio here: VS Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
• Known limitation: Registry API connectivity can affect search results
• Known limitation: Local Meilisearch adds a separate service to configure
• General VS Code troubleshooting lives in the /clients/vscode guide.

Frequently asked questions