
AgentSearch (agentsearchhq.com)
io.github.agentsearchhq-coderv1.1.1Updated Oct 3, 2026
AgentSearch web search, page extract and JS page render for agents. Self-hosted API via stdio.
Overview
Lets an assistant run web search, page extraction, and JavaScript page rendering through your own self-hosted AgentSearch-compatible API.
- What it does
- Exposes three read-only tools over stdio: agentsearch_web_search for queries, agentsearch_extract for pulling content from a URL you already have, and agentsearch_render, which renders JavaScript-heavy pages in headless Chromium and returns title, status, meta, and markdown, text, HTML, or links, with an optional screenshot. All three call your own AgentSearch-compatible backend over HTTP.
- When to use it
- Use it when you already run an AgentSearch-compatible backend and want Cursor, Claude Desktop, or another MCP host to search the web, extract pages, or render single-page apps. Prefer extract for static pages and render when extract returns empty or partial content.
- Requirements
- Node.js 20 or later, plus your own AgentSearch-compatible API. AGENTSEARCH_BASE_URL is required and has no default; the process exits at startup if it is missing. AGENTSEARCH_API_KEY is optional and sent as a Bearer token. Network access to your backend is needed.
Installation
In SourceWeft
- Open AgentSearch (agentsearchhq.com) in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
agentsearch-mcp
MCP (Model Context Protocol) server for people running their own AgentSearch-compatible backend. It exposes web search, page extract, and JavaScript page rendering (headless browser) to Cursor, Claude Desktop, and other MCP hosts over stdio.
AGENTSEARCH_BASE_URL is required and points at that API. There is no built-in default host.
For pay-per-call access with no backend of your own, use Pocket's official MCP server instead:
That server calls agentsearch-web-search-v1 and agentsearch-web-extract-v1 at $0.005/call over x402. Details: https://agentsearchhq.com/?utm_source=github&utm_medium=readme&utm_campaign=mcp
This package calls your API directly:
- Search:
POST {AGENTSEARCH_BASE_URL}/v1/searchwith body{ "query": "...", "max_results": 5 } - Extract:
POST {AGENTSEARCH_BASE_URL}/v1/extract - Render:
POST {AGENTSEARCH_BASE_URL}/v1/render(headless Chromium; OpenAPI spec)
Tools
For agentsearch_render, target-site failures (DNS/TLS errors, timeouts, bot walls, robots.txt) come back as a normal result whose JSON has a non-null error object (code, message, retryable); bad input (400), oversize body (413), rate limits (429) and backend faults (500) are MCP errors. The backend enforces a ~4.2 s render deadline.
Requirements
- Node.js 20+
- Your own AgentSearch-compatible API. Set
AGENTSEARCH_BASE_URLto its base URL. The process exits at startup if that variable is missing.
Install
From a local checkout:
Scripts: build → tsc, start → node dist/index.js, test → build + node --test test/*.mjs, prepare → runs build.
Binary: agentsearch-mcp → dist/index.js
Environment variables
See .env.example. Never commit a real .env.
Cursor
Project (.cursor/mcp.json) or user (~/.cursor/mcp.json / Cursor Settings → MCP):
Optional API key:
Claude Desktop
Edit Claude Desktop config (claude_desktop_config.json):
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Restart Claude Desktop after saving.
Local run
If AGENTSEARCH_BASE_URL is unset, the process prints an error and exits.
License
MIT
Source: README.md at commit 9654fc0
Tools
0Version history
1- v1.1.1LatestOct 3, 2026


