Do I need an API key?
Not for OAuth clients: connect to the remote URL and sign in with your Search1API account. For header-based or local stdio setups, get a key from the [Search1API dashboard](https://dashboard.search1api.com).

@SuperAgents, LLC
Basic information
Web search, agentic search, news, page retrieval, sitemaps, and trending topics through Search1API.
https://mcp.search1api.com/mcpclaude mcp add search1api --transport http https://mcp.search1api.com/mcpSearch the live public web when the user needs current information, sources, or research. Returns citable results with id, title, URL, and text. Each result includes a URL that can be read in full.
Search current news when the user asks about recent events, announcements, or coverage. Returns citable article results with title, URL, snippet, and optional extracted text.
Extract the readable title and full text from a public URL supplied by the user or returned by search.
Discover related public links from a page or domain when the user wants to explore a site's structure or available pages.
List currently trending repositories or stories from GitHub or Hacker News when the user asks what is popular now.
Describe what you are looking for in natural language when you do not know which source to search. Search1API picks up to five engines (web, Hacker News, Reddit, GitHub, X, arXiv, Wikipedia, and more), infers a time window from phrases such as "this week", and returns at most 10 relevant results ranked by relevance. Costs 5 credits; use search when you already know the engine.
Present already retrieved source results as source cards when the host supports UI, with a complete readable text list otherwise. Use when the user wants to browse sources or a visual list helps the task. Pass existing results in the desired order; never invent source URLs or factual titles. Does not search, crawl, fetch URLs, verify sources, or consume search credits. Do not call for intermediate research results or when a text answer is sufficient.
Search1API is the official MCP server for Search1API: web search across many engines, agentic search, news, full-page retrieval, sitemap discovery, and GitHub / Hacker News trending in one server. It runs as a hosted Remote MCP server at https://mcp.search1api.com/mcp with OAuth sign-in, so there is nothing to install.
https://mcp.search1api.com/mcp and sign in when prompted. Clients without OAuth can send Authorization: Bearer YOUR_SEARCH1API_KEY instead (key from the dashboard).npx -y search1api-mcp with the SEARCH1API_KEY environment variable (Node.js 20+).Claude Code example:
claude mcp add --transport http search1api https://mcp.search1api.com/mcp
search: Google, Bing, DuckDuckGo, Yahoo, Yandex, and specialized sources including GitHub, Reddit, X, arXiv, Wikipedia, Grokipedia, YouTube, WeChat, Bilibili, and IMDb, with site filters, time ranges, and paginationask: agentic search that picks engines and a time window from a natural-language request and returns up to 10 relevant, citable resultsnews: news search, including Hacker News with points and comment countscrawl: full content of any URLsitemap: related links discovered from a URLtrending: GitHub and Hacker News trendsrender_results: shows selected results as interactive source cards in MCP Apps clients (a readable list elsewhere), without repeating a search or using creditsNot for OAuth clients: connect to the remote URL and sign in with your Search1API account. For header-based or local stdio setups, get a key from the [Search1API dashboard](https://dashboard.search1api.com).
Any client that speaks Streamable HTTP MCP, including Claude, Claude Code, Cursor, VS Code, and Windsurf. Local stdio is available through the `search1api-mcp` npm package.
Docs: [s1.dev/docs/integrations/mcp](https://s1.dev/docs/integrations/mcp). Source (MIT): [github.com/superagents-lab/search1api-mcp](https://github.com/superagents-lab/search1api-mcp). Updates: [@search1api_dev](https://x.com/search1api_dev) on X.
The Search1API remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.search1api.com/mcp, so AI assistants can connect to it without installing or running anything locally.
Add the endpoint https://mcp.search1api.com/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.
Yes. Search1API uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.
Search1API exposes a stdio endpoint, the transport used by remote MCP servers and supported by all major MCP clients.
AdaptlyPost: Schedule and publish social posts to Instagram, TikTok, YouTube, X, Facebook, LinkedIn, Pinterest, Threads, and Bluesky from any MCP client.
Manage your Adobe Experience Manager content
Read-only, source-backed AI model pricing, history, comparisons and cost calculations.
The 9apes MCP server lets an AI assistant read the GitHub Actions data 9apes already collects for your organization: runs, jobs, steps, and their durations. Ask it why a build got slower, which jobs take the longest, or
Email for long-term client relationships: ARVX reads each person first and remembers every pair.
Comments