Remote (hosted) MCP
Search the web, fetch any URL and map a site from the hosted MCP server. Connect with no key, sign in with String, or send an API key.
The hosted MCP server runs at https://mcp.usestring.ai over Streamable HTTP, and is the recommended way to
connect. Nothing to install or keep updated.
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
Connect to this address:
https://mcp.usestring.aiThere are three ways to use it:
| Way to connect | URL to add | Credential |
|---|---|---|
| No key | https://mcp.usestring.ai | None |
| Sign in with String | https://mcp.usestring.ai?login | A sign-in to String in your browser |
| An API key | https://mcp.usestring.ai | Authorization: Bearer YOUR_API_KEY |
Use it with no key to get started: add the address and nothing else. For agents says what that gives you.
Sign in with String if your client supports it — Claude, Claude Code, ChatGPT, Codex, Grok, and OpenCode v2 do. You add
https://mcp.usestring.ai?login, sign in to String in your browser, pick which of your Web Access keys the app should
use, and that is it. No key is ever pasted into the app. Keep the ?login on the URL: it makes the server ask your
client to sign in, and without it the client connects with no key.
Present an API key for everything else. The key is forwarded to the API per request; there is no shared server key.
Signed in or with a key, the address lists eight tools, each annotated for exactly what a call can do. Six are the
tools that MCP /v3 endpoint documents; the other two are web_access_balance and
web_access_product_help, and the overview lists all eight. For site integrations, connect to
https://mcp.usestring.ai/integration, as in Site integrations. For browser actions, or to
cancel or list crawl jobs, connect to https://mcp.usestring.ai/v2/mcp instead; its tools are on
MCP tools. Apps you install from a connector directory or marketplace use
https://mcp.usestring.ai/v1/mcp, which keeps the four core tools, and the String plugin for ChatGPT and
Codex connects to /v3/mcp.
For agents
An agent, or anyone setting one up, can start with no key and no account. Add the address as a remote MCP server and nothing else:
https://mcp.usestring.aiweb_access_fetchandweb_access_searchwork with the fields and the daily allowance of a request without a key.web_access_product_helpanswers questions about String's products from String's public site. It does not count against that allowance.
For every field and the full tool list, sign in at https://mcp.usestring.ai?login or send an API key, as below.
Sign in with String (OAuth)
Claude (web, desktop, mobile), Claude Code, ChatGPT, Codex, Grok, and OpenCode v2 can authenticate without handling your key at all. Each client's own steps are under Client configuration: Claude, Claude Code, ChatGPT, Codex, Grok and OpenCode. In all of them, signing in goes like this:
Add the connector
In your client's connector settings, add a custom connector pointing at:
https://mcp.usestring.ai?loginSign in
Open String in your browser using your client's sign-in link or prompt. If you are not already signed in, sign in as normal.
Choose the key it may use
The consent screen asks to grant web_access, and opens on Create a new key for this app, named for you and the
app — SAM_CLAUDE_CODE_MCP_KEY, say. Edit the name, tick Allow CAPTCHA solving if the key may solve captchas (it starts off), and click Allow:
the key is created for your organization and bound to this app in one step. Its value is never shown, here or later,
because the connection spends it through that binding — there is nothing to paste anywhere.
To spend a key you already hold instead, pick it under Or use an existing key; the list shows each key's name and whether it solves captchas. An app you have connected before opens on the key it is already bound to, so re-consenting does not rotate it.
Nothing is created or saved until you click Allow — filling the form in and then denying leaves your organization's keys and this connection unchanged.
The app is connected. Requests it makes use the key you chose and bill your organization, exactly as if you had pasted that key in.
One key per app
Each connected app is bound to one specific key, so you can give a client a captcha-solving key and another a plain one, and tell their spend apart. Reconnecting the same app replaces its choice rather than adding a second one.
Managing connected apps
Every app your organization has connected is listed under Connected apps in settings — the client, the key it uses, who connected it, and when it was last used. Connections are visible to your whole organization, because the key they spend belongs to the organization rather than to one person.
Disconnect removes the app's access to the key within a minute. The app stays signed in to String, so reconnecting takes one step, and your key itself is unchanged — other apps using it keep working.
Revoking a key disconnects its apps
Revoking a Web Access key immediately breaks every app connected with it. The revoke confirmation tells you how many apps that is. To move an app to a different key, reconnect it and pick the new key.
Present an API key
For clients without OAuth support, authenticate with your key directly. Send Authorization: Bearer YOUR_API_KEY to
the main address, from a client that supports custom headers on a remote MCP server.
https://mcp.usestring.ai
Authorization: Bearer YOUR_API_KEYThe address takes a key in the header only; a key in the URL path returns 404. A client that can only configure a
URL signs in at https://mcp.usestring.ai?login, or connects with no key.
Site integrations
To run site integrations from an MCP client, connect to this address in place of the main one:
https://mcp.usestring.ai/integrationIt lists the main address's eight tools and two more: web_access_integrations, which lists the sites and describes
each action's input and output, and web_access_integration_run, which runs an action and returns its rows. A run is
billed to your organization; see Pricing.
This address needs a credential. A client that signs in adds the URL as it is, with no ?login, and a client with an
API key sends Authorization: Bearer YOUR_API_KEY to it. A request with no credential returns 401.
Client configuration
Claude, Claude Code, ChatGPT, Codex, Grok and OpenCode v2 sign in with String, at https://mcp.usestring.ai?login. The
other clients here connect to https://mcp.usestring.ai with an API key.
Claude
Claude on the web, Claude Desktop and the Claude mobile apps share your connectors, so add String once, on the web or in Claude Desktop:
- Open Customize → Connectors, click + Add, then Add custom connector.
- Name it
string, enterhttps://mcp.usestring.ai?loginas the server URL, and click Continue. - Continue through the sign-in settings Claude detects. Under OAuth client, keep Use Claude's published identity; String does not accept the other two options. Click Add.
- Sign in with String when Claude asks, and choose the key Claude may use.
In a chat, turn String on from the + menu, under Connectors.
On Team and Enterprise plans, an owner adds the connector once for everyone: Organization settings → Connectors,
Add, then Custom → Web, with the same URL and OAuth client setting. Each member then finds
string under Customize → Connectors and clicks Connect to sign in with String.
Claude Code
Add the server, then sign in:
claude mcp add --transport http --scope user string "https://mcp.usestring.ai?login"
claude mcp login stringKeep the quotes, so your shell passes the ? through. The first command's confirmation shows the URL without
?login; the saved configuration keeps it. The second command opens String's consent screen in your browser. Choose or
create the key Claude Code may use. In a running session, /mcp does the same: select string and choose
Authenticate. --scope user adds String to every project; without it, the server is added to the current project
only.
To use it with no key instead, add https://mcp.usestring.ai and skip the second command.
ChatGPT
Install String from the OpenAI Plugins Directory:
- Open the String plugin and select + to install it.
- Sign in with String when ChatGPT asks, and choose the key it may use.
Start a new chat, then type @ and select String to use it. The plugin works in ChatGPT on the web, desktop and
mobile.
To add the server yourself instead, create a custom MCP server. OpenAI makes these available on Business, Enterprise and Edu workspaces, and on Business only admins and owners can add one; see Connecting custom MCP servers in ChatGPT.
- Open Plugins, select +, then Add custom MCP server.
- Name it
string. The description is optional. - Under Connection, enter
https://mcp.usestring.ai?loginas the server URL, not a Tunnel. - Set authentication to OAuth and leave its other fields empty: ChatGPT reads String's sign-in settings from the URL.
- Tick I understand and want to continue, select Create as a plugin, and sign in with String when ChatGPT asks.
Install the plugin, then type @ in a conversation and select string to use it.
Codex
Codex installs plugins from the same directory as ChatGPT. In the ChatGPT desktop app, open the
String plugin and select +; in Codex
CLI, run /plugins and install String. Start a new session afterwards. The Codex IDE extension doesn't support
plugins, so use the command below there.
Codex also adds the hosted server and starts String sign-in in one command:
codex mcp add string --url "https://mcp.usestring.ai?login"It prints a link to String's consent screen. Open it and choose or create the key Codex may use. To sign in again
later, run codex mcp login string. The Codex IDE extension reads the same ~/.codex/config.toml, so String
is available there too.
Grok
Add String as a custom connector on grok.com:
- Open Connectors, select New Connector, then Custom.
- Name it
stringand enterhttps://mcp.usestring.ai?loginas the server URL. - Leave the OAuth fields blank and click Connect.
- Sign in with String and choose the key Grok may use.
OpenCode
Run opencode --version to check your installed version. Sign-in needs OpenCode v2; OpenCode 1.x can't sign in with
String. If you have 1.x, install v2 with:
curl -fsSL https://opencode.ai/v2/install | bashThen add the hosted server globally and sign in, without putting an API key in a project configuration:
opencode mcp add string --url "https://mcp.usestring.ai?login" --global
opencode mcp auth stringThe second command opens String's consent screen. Choose or create the key OpenCode may use; OpenCode stores the OAuth
credentials outside project configuration. web_access_search and web_access_fetch are then available in every
project.
Run opencode mcp list to check the connection. If it shows needs authentication, reconnect:
opencode mcp logout string
opencode mcp auth stringOn OpenCode 1.x, use an API key instead. This adds the server to your global configuration with the key in a header:
opencode mcp add string --url https://mcp.usestring.ai \
--header "Authorization=Bearer YOUR_API_KEY"opencode mcp list then shows it as connected.
Kiro
Kiro takes a one-click install link. This one carries the endpoint and the bearer header already, and reads the key
from a STRING_API_KEY environment variable — set that, or open Kiro's MCP settings after installing and paste the key
into the header directly.
To do it by hand instead, add this to ~/.kiro/settings/mcp.json:
{
"mcpServers": {
"string": {
"url": "https://mcp.usestring.ai",
"headers": { "Authorization": "Bearer YOUR_API_KEY" },
"disabled": false,
"autoApprove": []
}
}
}Zed
Zed supports remote MCP servers natively. Open Settings → AI → MCP Servers, choose Add Server, then
Add Remote Server. Or put it in settings.json directly:
{
"context_servers": {
"string": {
"url": "https://mcp.usestring.ai",
"headers": { "Authorization": "Bearer YOUR_API_KEY" }
}
}
}Zed's MCP extensions only wrap servers that ship as a binary or an npm package, so the remote endpoint is added this way rather than by installing an extension.
goose
Run goose configure, choose Add Extension, then Remote Extension (Streamable HTTP), and give it
https://mcp.usestring.ai with an Authorization header of Bearer YOUR_API_KEY. In the desktop app the same thing
lives under Extensions → Add custom extension.
Muse Code
Muse Code reads MCP servers from ~/.config/muse/settings.json. Add this to its mcp_servers block — if the file
already exists, put the entry inside the mcp_servers block it already has:
{
"schema_version": 1,
"mcp_servers": {
"string": {
"transport": "streamable_http",
"url": "https://mcp.usestring.ai",
"headers": { "Authorization": "Bearer YOUR_API_KEY" },
"mode": "optional"
}
}
}Keep "schema_version": 1 in the file: without it, every muse command fails with malformed settings file.
"mode": "optional" lets a run carry on with a warning if the server is unreachable, where Muse Code's default,
required, aborts the whole run. Muse Code expands ${VAR} in server configs, so "Bearer ${STRING_API_KEY}" keeps
the key itself out of the file. Muse Code connects with an API key, as above.
Other clients
A client with native remote MCP support takes the URL directly. If it cannot sign in with String, send an API key in a
header, as in Present an API key, or use it with no key. A client that only speaks stdio bridges
to the remote endpoint with mcp-remote, which sends the key in a header:
{
"mcpServers": {
"string": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.usestring.ai", "--header", "Authorization:${STRING_AUTH_HEADER}"],
"env": { "STRING_AUTH_HEADER": "Bearer YOUR_API_KEY" }
}
}
}Keep the key in env, as here: some clients split an argument that contains a space.
SSE endpoints (/sse and /<key>/sse) are not supported. Use https://mcp.usestring.ai, which speaks Streamable
HTTP.
If your client cannot reach a remote MCP server, the same server can run locally over stdio.