AI Development

    MCP Web Search for Agent Tools (Desearch)

    By Desearch Editorial Team8 min read

    A web search MCP is a Model Context Protocol server that lets an AI agent call live search as a tool during a session, instead of relying on training data or pasted results. Desearch MCP is a hosted MCP server at https://mcp.desearch.ai/mcp that exposes web and X search tools, including web-search, ai-search, x-search, web-links-search, x-links-search and extract. Connect it in Claude Code, Cursor or VS Code by adding that URL and your Desearch API key as an Authorization header. Usage is billed per API; see https://www.desearch.ai/pricing.

    JSON
    {
      "url": "https://mcp.desearch.ai/mcp",
      "headers": {
        "Authorization": "Bearer <DESEARCH_API_KEY>"
      }
    }

    Create the key at https://console.desearch.ai/api-keys. Cursor wraps this in mcpServers, VS Code in servers with "type": "http".

    Desearch MCP is available over hosted Streamable HTTP. The documented path is the hosted server at https://mcp.desearch.ai/mcp. Create an API key in Console, add that URL plus an auth header in your client, then call tools from the live tools list.

    Canonical reference: Desearch MCP guide. Re-check that page before you ship internal runbooks; tool inventory can change.

    Without MCP you usually:

    • call the Desearch REST API from your backend, or
    • paste search results into the chat yourself

    With hosted MCP, a compatible client can:

    • connect to Desearch as an MCP server over HTTP
    • call search and related tools during a session
    • keep DESEARCH_API_KEY in client config / headers instead of in the transcript

    That shift matters for day-to-day builder work. The model can decide when to search, you stay out of the copy-paste loop, and secrets stay out of chat history if you configure them correctly.

    Source of truth = live MCP docs

    Use the live docs page as the install contract:

    • Endpoint: https://mcp.desearch.ai/mcp
    • Auth for tool calls: Authorization: Bearer <DESEARCH_API_KEY> or x-api-key: <DESEARCH_API_KEY>. Some clients accept a raw key in Authorization with no Bearer prefix.
    • initialize and tools/list work without a key; tools/call without a key returns 401 (-32001).

    GET https://mcp.desearch.ai/health returns 200 JSON when the host is up. That is useful for a quick connectivity check. The MCP session itself runs at /mcp.

    Do not treat local npm / stdio install as the documented default. Live docs keep local npm out of the page until a signed smoke exists. Do not claim an official MCP Registry listing.

    Prerequisites

    • A Desearch API key from Console API keys
    • A client that supports MCP over HTTP URLs (Claude Code, Cursor, VS Code, or another HTTP-capable host)

    Never commit live keys to git. Never paste keys into public prompts or shared notes.

    Hosted endpoint + auth

    Minimum shape:

    JSON
    {
      "url": "https://mcp.desearch.ai/mcp",
      "headers": {
        "Authorization": "Bearer <DESEARCH_API_KEY>"
      }
    }

    The hosted MCP server accepts Authorization: Bearer <DESEARCH_API_KEY>, a raw key in Authorization, or x-api-key: <DESEARCH_API_KEY>. Clients should send the Bearer form.

    Desearch MCP tools

    Names and titles below are copied from the Desearch MCP guide (https://www.desearch.ai/docs/guide/sdk/mcp). Your client's live tools/list is the source of truth.

    Tool nameTitle (as in docs)Searches
    ai-searchAI Searchweb and X (tools: web, twitter)
    web-searchWeb Searchweb
    web-links-searchWeb Links Searchweb only (docs: "This tool does not search X")
    x-searchX SearchX
    x-links-searchX Links SearchX
    x-posts-by-urlsGet X Posts by URLsX
    x-post-by-idGet X Post by IDX
    x-posts-by-userSearch X Posts by UserX
    x-post-retweetersList X Post RetweetersX
    x-user-postsGet X User TimelineX
    x-user-repliesGet X User RepliesX
    x-post-repliesGet X Post RepliesX
    x-trendsGet X TrendsX
    extractExtract Page Contenta given URL
    web-crawlCrawl Web Page (Legacy)a given URL

    Claude Code

    BASH
    claude mcp add --transport http desearch https://mcp.desearch.ai/mcp \
      --header "Authorization: Bearer ${DESEARCH_API_KEY}"

    If your CLI build expects a different header flag, use the equivalent custom-header option and keep the same key value.

    Cursor

    Open your MCP config (often ~/.cursor/mcp.json) and add:

    JSON
    {
      "mcpServers": {
        "desearch": {
          "url": "https://mcp.desearch.ai/mcp",
          "headers": {
            "Authorization": "Bearer <DESEARCH_API_KEY>"
          }
        }
      }
    }

    Fully quit and restart Cursor after edits. Partial reloads can leave a stale MCP session.

    VS Code

    VS Code uses a servers key (not mcpServers):

    JSON
    {
      "servers": {
        "desearch": {
          "type": "http",
          "url": "https://mcp.desearch.ai/mcp",
          "headers": {
            "Authorization": "Bearer <DESEARCH_API_KEY>"
          }
        }
      }
    }

    Verify with tools/list

    After reload:

    1. Confirm the Desearch server shows as connected.
    2. Confirm tools appear from live tools/list. Do not hard-code a tool count. Inventory can change.
    3. Call a simple tool such as web-search with {"query":"desearch"} or ai-search with {"prompt":"desearch docs"}.

    Docs currently document deep examples for several tools (including ai-search, web-search, x-search, extract, and web-crawl) plus additional X helpers. Always prefer your client's live schema over any frozen list in a blog post.

    MCP vs REST / SDK

    Use hosted MCP whenUse REST / SDK when
    You want search inside Claude Code / Cursor / VS Code as toolsYou are building a backend, worker, or product API
    Setup should live in the agent hostYou need custom retries, batching, or multi-tenant keys
    Operators connect once per machine / profileYou need server-side logging and SLAs you control

    Many teams use both: MCP for builder workflows, REST/SDK for production agents. MCP does not replace Desearch API docs; it is another way to call the product from agent hosts.

    Troubleshooting

    SymptomCheck
    401 / unauthorizedKey present on every request; send Authorization: Bearer <DESEARCH_API_KEY>
    Server missingConfig path for that client; full restart
    Tools list emptyNetwork to mcp.desearch.ai; key validity
    npm install failuresOut of scope here; hosted HTTP is the documented path

    Claims we are not making

    • Desearch is not claimed here as listed in the official MCP Registry.
    • Local npm / stdio is not claimed as a proven default.
    • Tool counts and schemas are not frozen forever; use live tools/list.
    • No invented latency or cost benchmarks.

    Next steps

    1. Create a key in Console.
    2. Add https://mcp.desearch.ai/mcp with your auth header in Claude Code, Cursor, or VS Code.
    3. Confirm tools from live tools/list, then run a simple search call.
    4. Keep the canonical reference open: Desearch MCP guide.

    FAQ

    Is this the official MCP Registry?

    Do not assume that. This article does not claim an official Registry listing. Use the hosted HTTP endpoint documented by Desearch.

    Do I need npm install?

    Not for the documented path. Hosted Streamable HTTP is what the live MCP guide documents. Local npm stays out until Desearch publishes a signed smoke.

    Which tools can I call?

    Whatever your client receives from live tools/list. Docs include examples for web / AI / X search and extract-style tools; treat those as illustrations, not a permanent inventory.

    Does this replace the REST API?

    No. MCP is for agent/IDE tool wiring. REST/SDK remains the path for app backends.

    Related examples: Reddit search with no code via MCP, Content ideas from questions people ask.

    Put your next idea to work.

    Try a query in the playground, then use the docs to bring Desearch into your application.

    Browse more articles