MCP tools

Both the remote and self-hosted servers expose the same three tools. Fetch and search are read-only; web_access_sitemap creates and manages billed crawl jobs.

web_access_fetch

Fetch any webpage and get clean, LLM-ready Markdown back. Handles proxy rotation, anti-bot protection, CAPTCHAs, and JavaScript-rendered content automatically. The common case is passing only a url.

Returns: Markdown by default; the verbatim body or a JSON envelope when format is set accordingly.

{ "url": "https://example.com/article" }

Browser actions

Pass actions when the content you want does not exist in the document until something happens to the page — a click past a consent gate, a search form submitted, a "load more" button, or rows that render only once scrolled into view. The sequence runs in a real browser session, and the page is captured after the last step.

Escalate in this order, cheapest first:

1. Plain url — always try this first.
2. executeJS: true — the page renders client-side but needs no interaction.
3. actions — the content requires interaction. Takes tens of seconds and holds a browser session.

If the data is missing at every rung, it is probably not in the HTML at all. Look for the JSON API the page itself calls and fetch that endpoint directly — it is faster and returns exact values.

{
  "url": "https://example.com/listings",
  "actions": [
    { "type": "wait", "selector": ".card", "timeout": 20000 },
    { "type": "scroll", "direction": "down" },
    { "type": "wait", "milliseconds": 1500 },
    { "type": "scroll", "direction": "down" },
    { "type": "wait", "milliseconds": 1500 }
  ]
}

Waiting on a selector rather than a fixed duration continues as soon as the content is there, so prefer it wherever you can name one. Up to 50 actions per request, one screenshot at most, and 30s caps any single wait. The full step vocabulary is in Browser actions.

Returns with actions: a JSON object — data (the final page, Markdown by default), finalUrl, statusCode, and screenshot when the sequence took one. A failed step still returns successfully, carrying error and failedActionIndex (0-based, into your actions array) with data holding the page as it stood at that point.

actions cannot be combined with method, body, headers, or format: "raw" — a browser session is always a GET.

web_access_search

Search the web and return structured organic results. Bypasses anti-bot protection on search engines.

Returns: the organic results, each with position, title, URL, snippet, and display URL.

{ "query": "latest developments in AI agents 2026" }

web_access_sitemap

Crawl a whole site and map its URLs. Starting from one URL the crawler follows same-domain links breadth-first (optionally seeded from the site's /sitemap.xml) and records every URL it reaches with fetch status, depth, and parent. Crawls run asynchronously as sitemap jobs: one tool drives the whole quote → approve → poll → read lifecycle through its action parameter, and nothing is crawled or billed until the quote is explicitly approved.

Returns: the JSON envelope for the chosen action (quote, status, URL page, or job list) alongside a one-line summary.

{ "action": "submit", "url": "https://example.com", "maxPages": 200, "maxDepth": 3 }

Recommended workflow

1. Call web_access_search to find relevant pages for a query.
2. Call web_access_fetch on the most relevant URLs to pull their full content.

To cover a whole site instead of single pages, run web_access_sitemap first (submit → approve → poll → results) to build the URL list, then web_access_fetch the pages you need.