Remote (hosted) MCP

The recommended way to use the String Web Access API MCP server — nothing to install.

The hosted MCP server runs at mcp.usestring.ai over Streamable HTTP, and is the recommended way to connect. Point your client at the endpoint and authenticate with your String API key; nothing to install, and you are always on the current tool set. There is no shared server key; your key is forwarded to the API per request, so a valid key is the access control.

Endpoint

https://mcp.usestring.ai/v1/mcp

You can present your API key two equivalent ways:

Send Authorization: Bearer YOUR_API_KEY to /v1/mcp. Use this with clients that support custom headers on a remote MCP server.

https://mcp.usestring.ai/v1/mcp
Authorization: Bearer YOUR_API_KEY

Put the key in the path — /<key>/v1/mcp — for clients that can only configure a URL. The server lifts the leading path segment into the bearer header.

https://mcp.usestring.ai/YOUR_API_KEY/v1/mcp

Client configuration

Clients with native remote/HTTP MCP support can use the URL directly. For clients that only speak stdio, bridge to the remote endpoint with mcp-remote:

mcpServers

{
  "mcpServers": {
    "string-ai": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.usestring.ai/YOUR_API_KEY/v1/mcp"]
    }
  }
}

Legacy SSE

An SSE transport is also available at /sse and /<key>/sse for older clients. Prefer the Streamable-HTTP /v1/mcp endpoint for new setups.

If your client cannot reach a remote MCP server, the same server can run locally over stdio.

Endpoint

Client configuration

On this page