Overview
Give any MCP client web fetch and search through the String Web Access API.
The String MCP server exposes the Web Access API as Model Context Protocol tools, so any MCP-compatible client (Claude Desktop, Cursor, VS Code, Windsurf) can fetch and search the web with automatic anti-bot bypass, CAPTCHA handling, and JavaScript rendering.
It exposes three tools:
| Tool | Description |
|---|---|
web_access_fetch | Fetch any webpage as clean, LLM-ready Markdown (or raw / JSON). |
web_access_search | Search the web and get structured organic results. |
web_access_sitemap | Map a whole site's URLs as an asynchronous, quote-then-approve crawl job. |
See Tools for parameters and return shapes.
Getting started
Remote (hosted) — recommended
Point your client at https://mcp.usestring.ai/v1/mcp and authenticate with your API key. Nothing to
install, nothing to keep updated.
The hosted endpoint is the right choice for almost everyone: new tools and improvements are available the moment we ship them, with no version to bump on your side.
It uses your own String API key — there is no shared server key. Get one at usestring.ai.
Running it yourself
If your client cannot reach a remote MCP server, or your environment requires the process to be local, the same server
is published on npm as @usestring/mcp and speaks stdio.
Worth knowing what that does and does not change. You take over the version and the upgrade cadence, so a stale install quietly misses new tools. It does not keep your traffic local: the package is a thin client that forwards every call to the Web Access API over HTTPS with your key, exactly as the hosted endpoint does.