Best for
- Developers who need reliable, high-quality search capabilities
- AI applications requiring multiple search functions with easy integration
- Remote MCP scenarios where OAuth simplifies authentication
S
Search1API MCP Server
Official
Web search, news, crawling, sitemaps, and trends in one MCP server.
GitHub source repository ↗
67FMRS · C
Search1API MCP server is officially maintained, feature-rich with search, news, crawl, sitemap, and trending tools. It offers both remote and local modes with flexible authentication, but users should be mindful of API key security and associated costs.
The official MCP server for Search1API, providing web search, news search, page crawling, sitemap discovery, and trending topics. Supports remote MCP via Streamable HTTP with OAuth 2.1 or API key authentication, and local stdio mode requiring a SEARCH1API_KEY.
Tools
search
Perform web searches using Search1API, with customizable search engines, result count, crawling top results, site filters, and time range.
news
Search for news articles from multiple sources, with options for result count, crawling, site filters, and time range.
crawl
Extract content from a given URL.
sitemap
Get all related links from a URL (sitemap discovery).
trending
Get trending topics from popular platforms like GitHub and Hacker News.
Setup
Remote mode: configure your MCP client with URL https://mcp.search1api.com/mcp and use OAuth or Authorization: Bearer <API_KEY>. Local mode: run npx -y search1api-mcp with SEARCH1API_KEY environment variable. See README for client-specific configs.
claude_desktop_config.json
{
"mcpServers": {
"search1api": {
"command": "npx",
"args": ["-y", "search1api-mcp"],
"env": {
"SEARCH1API_KEY": "YOUR_SEARCH1API_KEY"
}
}
}
}
Fit and risk
Not for
- Users who need fully offline or external-API-free operation
- Scenarios where searching private data or keeping data local is required
- High-volume crawling due to extra credit costs per crawl
Required permissions
- Requires Search1API API key (local) or OAuth authorization (remote)
- Remote mode trusts mcp.search1api.com and localhost by default; self-hosted deployments can configure MCP_ALLOWED_HOSTS and MCP_ALLOWED_ORIGINS
- Search and crawl actions may consume API credits
Risks and side effects
- API key leakage: passing key via URL query parameter can expose it in logs; prefer OAuth or Authorization header
- Network dependency: remote mode requires access to mcp.search1api.com
- Data privacy: search queries and crawled content are sent to third-party API
- Rate limits and costs: high-frequency requests may incur charges or be throttled
Troubleshooting
- Verify SEARCH1API_KEY is set and valid. Check network connectivity. For self-hosted HTTP, ensure MCP_ALLOWED_HOSTS includes the required hosts, and browser clients need MCP_ALLOWED_ORIGINS configured. Inspect MCP client logs for detailed errors.
Use cases
AI assistants needing up-to-date web search results
Fetching latest news updates
Deep crawling web pages for full content
Quickly discovering website structure or related links
Tracking trending topics
Supported clients
Claude DesktopFull support
Claude.ai (Web)Full support
CursorFull support
VS CodeFull support
Claude CodeFull support
WindsurfFull support