Skip to main content

Check the connection

On a reverse proxy, forward the Authorization, Accept, Content-Type and any negotiated MCP headers. Keep the endpoint and its transfer subpaths on the same HTTPS origin. Configure request size and timeout limits for the intended binary uploads. Preserve provider transfer headers for direct S3 PUT requests. Avoid caching MCP or rewriting a binary response as JSON.

Diagnose an individual tool call

An HTTP 200 can carry a tool error. Check top-level JSON-RPC error and result.isError before reading a successful payload. The four browse tools return simpler messages for invalid arguments, access failures and unexpected errors. For paging errors, restart from the first page. Cursors belong to a particular query and access scope.

Diagnose a transfer

  • On a size or MIME error, call studio_get_upload_policy again. Check the workspace settings, PHP upload limits and the reverse proxy request limit.
  • If local chunks fail validation, compare the byte size, index and SHA-256 of the exact part. Resume from acceptedParts.
  • For S3, send the signed headers to the provider, preserve each quoted ETag and record it with Studio. A successful PUT alone does not complete the upload. Ask for a fresh signature if it has expired.
  • If a download URL is rejected, prepare it again from an accessible file and version. The download route performs a fresh permission check.
  • After token rotation reload config on every application instance. Resume with the same connection identity or start a new session.
See file transfers and credential lifecycle.