Desearch MCP server

    Desearch MCP is a hosted MCP server over Streamable HTTP. Create an API key in Desearch Console, then add the server in your agent. You do not need to install a package: the hosted endpoint is the recommended setup.

    Endpoint: https://mcp.desearch.ai/mcp

    1. Get your API key

    1. Open Desearch Console.
    2. Go to API Keys.
    3. Create a key and copy it once. Store it as DESEARCH_API_KEY.

    Send the key in the Authorization header as the raw key. Authorization: Bearer <key> and x-api-key: <key> also work.

    2. Connect your client

    Claude Code

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

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

    Claude Desktop

    Claude Desktop: use the hosted URL if your client supports URL servers.

    Clients that support OAuth

    Use the remote connector URL https://mcp.desearch.ai/mcp. MCP clients that support OAuth can connect to that URL and sign in through OAuth. On the Desearch sign-in page you paste your Desearch API key.

    Cursor

    Add this to ~/.cursor/mcp.json:

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

    VS Code

    VS Code uses the servers key, not mcpServers. Add this to your user mcp.json:

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

    For a step-by-step tested setup, see Use Desearch MCP in VS Code.

    Any other MCP client

    Use the hosted URL and match your client's header settings:

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

    3. Check the connection

    1. Restart or reload the MCP session in your client.
    2. Confirm the Desearch server shows as connected.
    3. Confirm the tools appear from the live tools/list.
    4. Call a simple tool, such as search-api with {"query":"desearch"} or ai-search with {"prompt":"desearch docs"}.

    Listing tools works without a key: initialize and tools/list are public. Calling a tool (tools/call) needs your key. GET https://mcp.desearch.ai/health returns 200 JSON when the host is up; it is a probe only, not a substitute for a keyed tool call.

    Tools

    Always go by your client's live tools/list: the inventory and titles can change, so do not hard-code a tool count.

    Search

    X (Twitter) data

    Page content

    Social platforms

    People Search

    Company Search

    Credits and rates: Pricing.

    Troubleshooting

    SymptomCheck
    Unauthorized error on tools/callSend Authorization: <key> (Bearer <key> or x-api-key also work). Listing tools does not need a key.
    Server missingThe config path for that client; restart the client.
    Tools list emptyNetwork access to mcp.desearch.ai; key scope.
    npm install failsUse the hosted endpoint https://mcp.desearch.ai/mcp.

    FAQ

    Do I need to install a package to use Desearch MCP?

    No. The recommended setup is the hosted endpoint at https://mcp.desearch.ai/mcp. You add it in your agent with a Desearch API key.

    Where do I get the API key?

    Create it in Desearch Console under API Keys: https://console.desearch.ai/api-keys.

    Can I list the tools without a key?

    Yes. initialize and tools/list work without an API key. Calling a tool needs the key.

    How many tools does the server have?

    Check your client's live tools/list. The inventory can change, so do not hard-code a tool count.