Oleksandr Kuzmenko, EditorPublished 5 min readAI-assisted · editor-reviewed
TL;DR
- AgentSearch MCP provides a zero-key free tier with 25 queries per day per IP.
- Requires Node.js 20+ and communicates locally over stdio transport.
- Project-level MCP configurations require explicit authorization via CLI before running.
Key facts
- Free search limit
- 25 queries/day per IP
- Paid search/extract cost
- $0.005 per call
- Node runtime requirement
- Node.js 20 or newer
Source: Key facts — Paid search/extract cost
Source: Key facts. Paid search/extract cost: $0.005 per call. Each figure is copied from the story.
- Paid search/extract cost$0.005 per call
Configuration via mcp.json
Cursor reads Model Context Protocol configurations either globally from ~/.cursor/mcp.json (or %USERPROFILE%\.cursor\mcp.json on Windows) or per repository at .cursor/mcp.json. Running the server requires Node.js 20 or newer.
To configure web search globally, register the @agentsearchhq/agentsearch-mcp package with stdio transport. When defining project-level configurations, team members must explicitly authorize the server using the CLI via agent mcp enable agentsearch to prevent untrusted process execution.
Tool Execution and Daily Limits
The server registers the agentsearch_web_search tool, returning up to five relevant text passages with titles and URLs. The free tier accommodates up to 25 requests per day per IP address with zero authentication requirements. Cursor invokes the tool automatically during agent planning loops when current web context is needed.
Optional capabilities include paid page extraction via agentsearch_extract ($0.005 per call) and agentsearch_render for dynamic JavaScript-heavy sites with separate per-call rates, settling microtransactions in USDC using the x402 protocol.
When to use
- When local coding agents require real-time web documentation lookup.
What to do today
- Add @agentsearchhq/agentsearch-mcp to ~/.cursor/mcp.json to enable global web searches.