Use our MCP search engine directly inside Claude

Our MCP server is a hosted HTTP endpoint that exposes the claude-quiz search engine as a tool inside Claude. It indexes more than 4,700 MCP servers and 32,000 tools, with semantic search (embeddings + hybrid ranking).

It exposes four tools that Claude can call automatically when you need them:

• search_mcps : natural-language search
• get_mcp_details : full details for an MCP by slug
• analyze_mcps : AI rerank of search results to filter false positives
• start_login : sign-in instructions (rarely needed, OAuth opens on its own)

Paste this snippet into your client. On the first tool call, a sign-in tab opens in your browser (OAuth, 100% free). Sign in once, your client keeps the token, and that's it.

One-liner (Claude Code)

Run this in your terminal:

claude mcp add --transport http mcp-search https://claudequiz.app/api/mcp

Your client doesn't support OAuth (CI, headless scripts, older client)? Generate an API key instead →

Or edit your config manually

Claude Code

Edit ~/.claude.json:

{
  "mcpServers": {
    "mcp-search": {
      "type": "http",
      "url": "https://claudequiz.app/api/mcp"
    }
  }
}

Quit and relaunch Claude Code. The `/mcp` command in chat should list `mcp-search` as connected.

Claude Desktop

On macOS: ~/Library/Application Support/Claude/claude_desktop_config.json (Windows: %APPDATA%\Claude\claude_desktop_config.json).

{
  "mcpServers": {
    "mcp-search": {
      "type": "http",
      "url": "https://claudequiz.app/api/mcp"
    }
  }
}

Fully restart Claude Desktop (Quit, not just close the window).

Cursor

Edit ~/.cursor/mcp.json with the same format as Claude Code.

{
  "mcpServers": {
    "mcp-search": {
      "type": "http",
      "url": "https://claudequiz.app/api/mcp"
    }
  }
}

Reload the Cursor window (⌘⇧P → Reload Window) so the config is picked up.

If your client doesn't open a sign-in tab automatically (older client, CI, headless script), you can bypass OAuth by generating an API key and adding it as Bearer. Same service, still free, still unlimited.

Once the key is copied, edit your config: add a "headers" field with your key as Bearer. Here is the full config (replace `mcps_PASTE_YOUR_KEY_HERE` with your real key):

{
  "mcpServers": {
    "mcp-search": {
      "type": "http",
      "url": "https://claudequiz.app/api/mcp",
      "headers": {
        "Authorization": "Bearer mcps_PASTE_YOUR_KEY_HERE"
      }
    }
  }
}

Or as a one-liner

Instead of editing the JSON file, just run (replace `mcps_PASTE_YOUR_KEY_HERE` with your real key):

claude mcp add --transport http mcp-search https://claudequiz.app/api/mcp --header "Authorization: Bearer mcps_PASTE_YOUR_KEY_HERE"

In any Claude chat, ask something in natural language:

I found 5 relevant MCPs for managing Google Calendar:

1. **google-calendar-mcp** (1.2k stars, verified)
   Tools: list_events, create_event, update_event, delete_event…
2. **gcal-pro** (340 stars)
   …

I'd recommend google-calendar-mcp to start with: it's the most popular, verified by Smithery, and covers all standard use cases.

Want me to show you how to install it?

Claude calls search_mcps in the background, gets the structured data, then generates its own contextual explanation.

• OAuth: the access token is held and stored by your client (Claude Code, Desktop, Cursor). We never see it in plaintext on the server.
• API key: stored as a SHA-256 hash on the server. We can't recover the plaintext, so we can never re-show it. You can have up to 5 active keys, revocable from the setup page.
• No password ever transits through Claude. All authentication happens on claudequiz.app in your browser.
• Your searches are logged like normal site searches (for AI cost tracking), but we don't store the contents of the results.