Search1API MCP
The official Search1API MCP: web search, news, page crawling, sitemaps and trends with OAuth sign-in or an API key.
- 175 ★ on the repository
- Last commit
Extended access
Why this level
- Agent queries and crawled addresses go to the Search1API cloud and consume account credits.
Install
- Works in
Manual install
claude mcp add --transport http search1api https://mcp.search1api.com/mcp --header "Authorization: Bearer YOUR_SEARCH1API_KEY"Hosted server. OAuth-aware clients connect without a key.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Agent queries and crawled addresses go to the Search1API cloud and consume account credits.
This is third-party code. Review the repository files before installing.
What it does
Search1API combines search, news, page content retrieval, site link discovery and trending topics in one API. The MCP server is available as the hosted `https://mcp.search1api.com/mcp` (OAuth 2.1 or an `Authorization: Bearer` header) and as the local `search1api-mcp` package through npx. Tools: `search` (Google, Bing, DuckDuckGo, Yahoo, Yandex, X, Reddit, GitHub, YouTube, arXiv, Wikipedia and other engines, site and time filters, `crawl_results` to load full text of top results), `news`, `crawl` for one page, `sitemap`, `trending` (GitHub, Hacker News) and `ask` for agentic search. `render_results` draws source cards in clients with MCP Apps and returns a text list elsewhere.
Who it is for. Developers and analysts who need search and page reading from Claude, Cursor, VS Code or Claude Code through one connection.
Good fit when
- Find fresh news on a topic and load the full text of the three best articles right away.
- See what is discussed on Hacker News and in GitHub trends.
- Get all site links through `sitemap` before going through documentation.
- Ask `ask` when a ready agentic answer with sources is needed.
Not a fit when
- Search without sign-up or billing is needed: every request needs credentials, even the tool list.
- Your own index is mandatory: Search1API returns results of external engines.
- Work happens inside a closed internal network: the server calls an external cloud API.
Example request
Using Search1API, find fresh news about the Next.js release, load the full text of the two best sources and give a summary.MCP
- Transport
- http, stdio
- Authentication
- OAuth
Environment variables
SEARCH1API_KEYsecret- Search1API key for the local mode and the Bearer header
Limitations
Every MCP request, including `initialize` and `tools/list`, requires credentials: the client goes through OAuth or sends an API key from the app.s1.dev dashboard. An API key in the URL (`?apiKey=`) is supported as a legacy option because it leaks into logs and history. A `search` request costs one credit and each successful `crawl_results` load adds another. The local mode needs Node.js 20 or newer. The repository license is not detected in GitHub data (NOASSERTION).
How to disable. Remove the search1api entry from the client configuration and revoke access or the key in the Search1API dashboard.
FAQ
How do I connect Search1API MCP to Claude Code?
With `claude mcp add --transport http search1api https://mcp.search1api.com/mcp --header "Authorization: Bearer YOUR_SEARCH1API_KEY"`.
Which engines does search support?
Google, Bing, bingcn, DuckDuckGo, Yahoo, Yandex, X, Reddit, GitHub, YouTube, arXiv, WeChat, Bilibili, IMDb, Wikipedia and Grokipedia.
Is there a local mode?
Yes, `npx -y search1api-mcp` with the `SEARCH1API_KEY` variable.
How much does a request cost?
A search costs one credit and each load through `crawl_results` adds another.
Is a separate install needed for Claude.ai?
No, the connector is installed from the Claude directory and you sign in with a Search1API account. Adding the address as a custom connector is discouraged.
Discussion
No questions or reviews yet.
Related
MCP serversA local MCP server with no API keys: multi-engine web search, page fetching and document reading tuned for LLMs.
Metasearch for agents: one MCP server and HTTP API merge results from many search providers into unified JSON with deduplication.
A unified search MCP server: one interface to Tavily, Brave, Kagi, Exa, Linkup, Firecrawl and GitHub search
Official SerpApi MCP server: the agent gets results from Google, Bing, YouTube, Amazon and other engines as JSON or Markdown
MCP server for real-time web search: general and vertical search, batch queries and page content extraction
Brave's official MCP server: web, news, image, video and place search plus extracted page content for model context
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Search1API MCP (this card) | yes | OAuth | 175 | |
| Brave Search MCP Server | yes | API key | 1,569 | searches through one search API; Search1API combines dozens of engines, news, page crawling and trends |
| Exa MCP Server | yes | OAuth | 5,228 | Exa neural search; Search1API works with classic search engines and topical sources |
README in short
The README explains authentication (OAuth, header, URL parameter), remote connection for Claude Desktop, Claude.ai, Cursor, Antigravity, VS Code, Claude Code and Windsurf, the `render_results` interface, the local npx mode, a skill in a separate repository and tool parameter tables.