MCP server

Search1API runs a hosted MCP server at:

https://mcp.search1api.com/mcp

Point an MCP client at it with your API key and the model can search the web, read pages and check what's trending — without you writing an integration.

Tools it exposes

Connect your client

Get a key from dashboard.search1api.com, then use the config for your client. The dashboard's MCP page generates these for you with the key already filled in.

claude mcp add --transport http search1api https://mcp.search1api.com/mcp \
  --header "Authorization: Bearer YOUR_SEARCH1API_KEY"

{
  "mcpServers": {
    "search1api": {
      "url": "https://mcp.search1api.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_SEARCH1API_KEY"
      }
    }
  }
}

{
  "mcpServers": {
    "search1api": {
      "url": "https://mcp.search1api.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_SEARCH1API_KEY"
      }
    }
  }
}

{
  "servers": {
    "search1api": {
      "type": "http",
      "url": "https://mcp.search1api.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_SEARCH1API_KEY"
      }
    }
  }
}

{
  "mcpServers": {
    "search1api": {
      "serverUrl": "https://mcp.search1api.com/mcp?apiKey=YOUR_SEARCH1API_KEY"
    }
  }
}

https://mcp.search1api.com/mcp?apiKey=YOUR_SEARCH1API_KEY

How auth works

The server takes your key from the Authorization: Bearer <key> header, and falls back to an ?apiKey=<key> query parameter for clients that cannot send headers. The header wins when both are present.

Query-parameter auth means your key travels in a URL, where it can end up in logs and shell history. Prefer the header whenever the client supports it.

Running it locally instead

The server also runs over stdio, straight from npm:

{
  "mcpServers": {
    "search1api": {
      "command": "npx",
      "args": ["-y", "search1api-mcp"],
      "env": {
        "SEARCH1API_KEY": "YOUR_SEARCH1API_KEY"
      }
    }
  }
}

Same tools, same key, no network hop to us for the MCP protocol itself — the API calls still go out to api.search1api.com.

Billing

MCP tool calls are ordinary API calls: they spend the same credits at the same rates as calling the endpoints yourself. See Credits and limits.

Source: github.com/fatwang2/search1api-mcp