Connect another MCP client

Your client must support a remote Streamable HTTP MCP server and bearer authentication. A client that supports only local command-based servers cannot connect directly through that transport.

Create a connection

1. In Studio, open Settings → Connections and enable connections after completing private draft setup.
2. Select Other MCP client. Give the connection a useful name, such as the client name and the website.
3. Choose Read the site for an initial check. Select the intended account and expiry.
4. Choose Create credential and save the one-time credential.
5. In your client, add the exact Studio MCP endpoint as a remote HTTP server.

Configure authentication through the client’s secret settings. The request header must be:

Authorization: Bearer <credential>

This shows the header format, not text to paste into a conversation. Use the client’s supported secret store or environment-variable configuration. Environment-variable syntax differs between clients; copying a ${VARIABLE} reference does not ensure that a client expands it.

VoxelSite’s private endpoint uses a bearer credential. Do not assume an OAuth login button or a public /mcp.php URL can replace it.

Request a small read

Ask the client to discover the available tools, read the site context and summarize its pages without changing anything. In Studio, choose Check result.

Tool discovery is filtered by access. Fewer tools may be correct for the selected credential. Copying configuration does not mark a connection as used; a successful server request does. See Troubleshooting for waiting, authentication and permission states.

Check client limitations

VoxelSite supports the MCP protocol profiles 2026-07-28 and 2025-11-25. The client must negotiate a supported version and handle the discovered input and output schemas. Its own limits may affect large catalogs, context responses or repeated continuation calls.

Start with a narrow permission set and one small task. If a client truncates a response, ask it to use the returned pagination or byte ranges. Do not treat omitted source as an empty file or a complete review.

The Other MCP client option supplies setup information. It does not certify every client that implements some part of MCP.