One API for Search, Crawling, and Sitemaps
Search1API MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. One API for Search, Crawling, and Sitemaps.
The official MCP server for Search1API — web search, news, page retrieval, sitemap discovery, and trending topics in one API.
Once Search1API is connected, these are the calls the assistant has available:
Authentication — Three methods are supported — use whichever your client supports:Cursor — The Cursor tool exposed by this serverWindsurf — The Windsurf tool exposed by this serversearch — Search the web using Search1API. Results include a citable id/title/url structure. Pass a result URL to crawl when you need the full pagenews — The news tool exposed by this servercrawl — The crawl tool exposed by this serversitemap — The sitemap tool exposed by this servertrending — The trending tool exposed by this serverBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 2 environment variables: SEARCH1API_KEY, YOUR_SEARCH1API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of search and retrieval servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Search1API's toolset — Authentication, Cursor, Windsurf and 5 more — is a fair guide to whether it matches your workflow.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Authentication | Three methods are supported — use whichever your client supports: |
| Cursor | The Cursor tool exposed by this server. |
| Windsurf | The Windsurf tool exposed by this server. |
| search | Search the web using Search1API. Results include a citable id/title/url structure. Pass a result URL to crawl when you need the full page. |
| news | The news tool exposed by this server. |
| crawl | The crawl tool exposed by this server. |
| sitemap | The sitemap tool exposed by this server. |
| trending | The trending tool exposed by this server. |
{
"mcpServers": {
"search1api": {
"url": "https://mcp.search1api.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_SEARCH1API_KEY"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SEARCH1API_KEY | Credential the server authenticates with. | Yes |
| YOUR_SEARCH1API_KEY | Credential the server authenticates with. | Yes |
The simplest web tool that matters — fetch any URL and get model-ready markdown back.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Put 6,000+ pre-built scrapers at your assistant's fingertips through one MCP endpoint.