Skip to main content

StudioTwin Web MCP

StudioTwin Web MCP provides host-agnostic, editor-free access to StudioTwin cloud operations from an MCP-compatible client. It can be used on its own and is also the cloud connection required by the Blender workflow.

Connection contract​

  • Endpoint: https://api.studiotwin.ai/mcp
  • Transport: stateless Streamable HTTP
  • Method: POST only, with one JSON-RPC message per request; there is no session or server-sent event stream
  • Surface: MCP tools only
  • Authentication: set STUDIOTWIN_API_KEY to a StudioTwin API key with the st_... prefix in the environment that launches your MCP client or agent harness

First create an account, then create an API key. The secret is shown only once. Set STUDIOTWIN_API_KEY securely in the environment that launches your MCP client or agent harness. Never paste the value into chat or place it in source control, logs, Blender, an addon, or command-line arguments that may be logged.

Connect an MCP client​

  1. In the MCP client, add a remote Streamable HTTP MCP connection using the production endpoint.
  2. Make STUDIOTWIN_API_KEY available in the environment that launches your MCP client or agent harness.
  3. Save the connection, then reconnect or use the client's supported hot-load mechanism. If the new MCP tools remain unavailable, restart or reconnect your harness session, then resume the task or conversation.
  4. Run MCP initialization and discover the live tools.
  5. Confirm the server identifies itself as StudioTwin and exposes its current generation, job, and asset operations.

MCP client configuration fields and secret interpolation syntax differ. This guide intentionally does not provide unverified client-specific configuration blocks. Follow your client's remote Streamable HTTP documentation while preserving the connection contract above.

Tool discovery is a no-cost connection check. Do not run a paid generation only to verify setup. Treat the live tool definitions as authoritative for names, input schemas, costs, limits, and status values.

Use Web MCP​

The discovered tools determine the operations available at the time you connect. Expected operation families include:

  • estimate generation cost and read the available credit balance;
  • submit generation and poll, list, or cancel owned jobs;
  • list and resolve owned assets;
  • create and complete an upload session for local source files; and
  • download generated environment, material, mesh, motion, and audio outputs from returned asset data.

You can also create and refine Concepts, review their image history, and choose the image to use for downstream work. Use ConceptLab when you prefer a visual workspace.

Do not hardcode tool names, schemas, prices, polling intervals, or terminal job states from this page. Reconnect and discover the live tools before operating, then inspect the selected tool definition immediately before use.

Generation and asset workflow​

  1. Discover the live tools and inspect the definitions needed for the request.
  2. Estimate the cost and confirm authorization before a credit-consuming call.
  3. For a local input, create an upload session, transfer the file as directed, complete the upload, and preserve the completed asset identifier separately from the upload-session identifier.
  4. Submit generation once and preserve every returned identifier by role.
  5. Poll that same job until the live response reports a terminal state. Do not resubmit because a response was delayed or ambiguous.
  6. Resolve and download the authorized outputs. An expired presigned URL should be refreshed by resolving the existing asset, not by regenerating it.
  7. Verify the downloaded files or resolved assets. A successful job state alone is not verification of the deliverable.
  8. Redact API keys, upload credentials, cloud URIs, and presigned URLs from logs and reports.

Motion generation and download are available through Web MCP. StudioTwin Blender motion import is Coming soon.

Use Web MCP with Blender​

Web MCP owns every StudioTwin cloud operation in the Blender workflow, including uploads, cost estimates, generation, jobs, asset resolution, and downloads. The supported Blender import operations through the official Blender MCP and StudioTwin Blender addon begin only after outputs exist at persistent local paths. Setup verification and authorized read-only inspection of Blender may occur earlier; they do not import or mutate an output.

After connecting Web MCP, continue with Blender-specific MCP setup, then follow the StudioTwin Blender addon workflow.

Troubleshooting​

  • Authentication error: confirm STUDIOTWIN_API_KEY is set in the environment that launches your MCP client or agent harness, and that the key is active, belongs to the intended organization, and has no copied whitespace.
  • No StudioTwin tools: reconnect the client and run initialization and tool discovery again. Confirm the client is using remote Streamable HTTP and the production endpoint.
  • Insufficient credits: inspect the live cost and balance tools, then see How Credits Work.