MCP Server
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.
Two ways to run it
Remote (hosted)
Point your client at our hosted endpoint and authenticate with your API key. There is nothing to install.
Self-hosted (npm)
Run the open-source @usestring/mcp server locally over stdio.
| Remote | Self-hosted | |
|---|---|---|
| Install | None | npx @usestring/mcp |
| Transport | Streamable HTTP | stdio |
| Endpoint | https://mcp.usestring.ai/v1/mcp | local process |
| Auth | API key (bearer or path) | STRING_AI_API_KEY env |
| Best for | Quick setup, hosted clients | Local control, air-gapped configs |
Both expose the same three tools and use your own String API key — there's no shared server key. Get a key at usestring.ai.