SearchX Documentation — AI-Powered E-Commerce Search

Connect any MCP-compatible assistant to the SearchX MCP server. Every client uses the same endpoint and the same two credentials.

Before you start

You need your API key and Application ID from the dashboard. See Authentication. Every connection sends:

Authorization: Bearer <your API key>
X-SearchX-App-Id: <your application id>

Endpoint: https://mcp.searchxengine.ai/mcp

Fastest: one-click install

Open https://mcp.searchxengine.ai/install?app_id=YOUR_APP_ID for ready-to-copy configurations and a downloadable .mcp.json for Claude Code.

Claude Code (CLI)

claude mcp add --transport http searchx https://mcp.searchxengine.ai/mcp \
  --header "Authorization: Bearer YOUR_API_KEY" \
  --header "X-SearchX-App-Id: YOUR_APP_ID"

Or commit a .mcp.json to your project so Claude Code offers a one-click approve:

{
  "mcpServers": {
    "searchx": {
      "type": "http",
      "url": "https://mcp.searchxengine.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY",
        "X-SearchX-App-Id": "YOUR_APP_ID"
      }
    }
  }
}

Claude Desktop

Claude Desktop runs local servers, so reach the remote endpoint through the mcp-remote bridge in claude_desktop_config.json:

{
  "mcpServers": {
    "searchx": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.searchxengine.ai/mcp",
        "--header",
        "Authorization: Bearer YOUR_API_KEY",
        "--header",
        "X-SearchX-App-Id: YOUR_APP_ID"
      ]
    }
  }
}

OpenAI (Responses API / Agents)

client.responses.create(
    model="gpt-5",
    input="Find running shoes under €120",
    tools=[{
        "type": "mcp",
        "server_label": "searchx",
        "server_url": "https://mcp.searchxengine.ai/mcp",
        "headers": {
            "Authorization": "Bearer YOUR_API_KEY",
            "X-SearchX-App-Id": "YOUR_APP_ID",
        },
        "require_approval": "never",
    }],
)

Claude API (Messages connector)

The Messages API MCP connector accepts only a single token (no custom headers), so pass the application id in the URL query instead:

client.beta.messages.create(
    model="claude-opus-4-8",
    max_tokens=1024,
    messages=[{"role": "user", "content": "Find running shoes under €120"}],
    mcp_servers=[{
        "type": "url",
        "url": "https://mcp.searchxengine.ai/mcp?app_id=YOUR_APP_ID",
        "name": "searchx",
        "authorization_token": "YOUR_API_KEY",
    }],
    tools=[{"type": "mcp_toolset", "mcp_server_name": "searchx"}],
    betas=["mcp-client-2025-11-20"],
)

Other clients (LM Studio, Cursor, …)

Any MCP-compatible client works the same way: add an HTTP MCP server pointing at https://mcp.searchxengine.ai/mcp with the Authorization and X-SearchX-App-Id headers. For example, in LM Studio add to its mcp.json:

{
  "mcpServers": {
    "searchx": {
      "url": "https://mcp.searchxengine.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY",
        "X-SearchX-App-Id": "YOUR_APP_ID"
      }
    }
  }
}

Clients that can't send custom headers

A few clients accept only a single bearer token. For those, put the application id in the URL query (https://mcp.searchxengine.ai/mcp?app_id=YOUR_APP_ID) and send only the Authorization header.