Overview
Web access for Claude, Cursor or any MCP client — search the web, fetch any URL with GET or POST and map sites, as clean Markdown or structured data.
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 and get clean, LLM-ready Markdown back.
Works with the agent you already use
Any MCP client that supports remote Streamable HTTP servers works with String. These are the ones people reach for most.
- and more
The hosted server, https://mcp.usestring.ai, lists eight tools when you sign in or send an API key, and three of
them with no key. Each is annotated for exactly what a call can do:
| Tool | Description |
|---|---|
web_access_fetch | Fetch any webpage as clean, LLM-ready Markdown (or raw / JSON). |
web_access_request | Send a POST, PUT, or PATCH with a body to a URL you supply. |
web_access_search | Search the web from one query: ranked organic results plus the knowledge panel, AI overview, local pack and other surfaces Google rendered — a snippet is not the page. |
web_access_sitemap_quote | Quote a crawl of a site's URLs. Nothing is crawled or billed. |
web_access_sitemap_start | Start a quoted crawl once its cost is approved. |
web_access_sitemap_status | Read a crawl's progress, then the URLs it found. |
web_access_balance | Read your organization's balance in USD: the total funded, what is spent, what is held for pending crawls, and what remains. Takes no input. |
web_access_product_help | Answer a question about String's products from String's public site, with the pages it used. |
With no key, the address lists web_access_fetch and web_access_search, which work within a daily allowance, and
web_access_product_help, which does not count against it; see Remote (hosted) MCP.
MCP /v3 endpoint documents six of them: web_access_fetch, web_access_request, web_access_search
and the three web_access_sitemap_* tools. For site integrations, connect to https://mcp.usestring.ai/integration;
see Site integrations. For browser actions, or to cancel or list crawl jobs, use
/v2/mcp, whose tools are on MCP tools.
Getting started
Remote (hosted) — recommended
Point your client at https://mcp.usestring.ai, which fetches and searches with no key. For every tool, sign in
with String at https://mcp.usestring.ai?login if your client supports it — Claude, Claude Code, ChatGPT, Codex,
and OpenCode v2 do — or authenticate with your API key. Nothing to install, nothing to keep updated.
For agents — start with no key
Add https://mcp.usestring.ai and nothing else: an agent can fetch and search within a daily allowance before it
has a key or an account.
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.
Signed in or with a key, it uses your own String API key — there is no shared server key. Clients that sign in with String never handle the key itself: you pick which of your keys the app may spend on a consent screen, and you can see or revoke every connected app from settings. Get a key 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: web operations go to the Web Access API over
HTTPS with your key, while product-help calls read String's public site pages at usestring.ai without sending the
key there.