String Web Access API
MCP Server

MCP tools

The web_access_fetch and web_access_search tools, with parameters.

Both the remote and self-hosted servers expose the same two tools. Both are read-only.

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.

ParameterTypeDefaultDescription
urlstringRequired. The full http/https URL to fetch.
formatmarkdown raw jsonmarkdownmarkdown for clean text, raw for the verbatim body, json for a { statusCode, headers, data } envelope.
methodGET POST PUT PATCHGETUse a write method to send a body.
bodystring | objectRequest body for non-GET. Objects are JSON-stringified.
headersobjectCustom request headers (max 50). Not supported with executeJS.
countryCodestring(2)ISO 3166-1 alpha-2 country for geolocated proxy routing.
executeJSbooleanfalseRender JavaScript for SPAs. Cannot be combined with headers.
solveCaptchabooleantrueSet false to fail fast instead of solving challenges.

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

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

Tool surface vs. the full API

The MCP web_access_fetch tool exposes the most common fetch options. Advanced /fetch features — structured extraction (jsonSchema), screenshots & browser actions, and requireWSS — are available on the HTTP API directly.

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

ParameterTypeDescription
querystringRequired. The search query. Be specific for best results.

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

Example call
{ "query": "latest developments in AI agents 2026" }
  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.