Studio Apps
attachStudioAppArtifact
Attach Studio App Artifact
Attach a build output to a tagged release.
Ask Claude, ChatGPT, Cursor or any AI connected to The Cloud "attach the build", and it calls attachStudioAppArtifact.
Example call
The MCP tools/call params, with the required arguments only.
{
"arguments": {
"appId": "<appId>",
"path": "<path>",
"tag": "<tag>"
},
"name": "attachStudioAppArtifact"
}Arguments
appIdstringrequiredThe Studio app IDfilenamestringoptionalDownload name for the artifact. Defaults to the file's own name.pathstringrequiredThe binary file in the app to release, e.g. "dist/nimbus-parts.zip".tagstringrequiredThe release tag, e.g. "v1.0.0" or "nimbus-2026-08". Letters, numbers, dots, dashes and underscores; must start with a letter or number.
Returns
The registry does not declare a return shape.
Ask for it
The Cloud routes these requests to this verb.
- attach the build
- release this zip
- publish the STL files under v1.0.0
Pair it with
The verbs that finish the job.
Questions
What does attachStudioAppArtifact do?
Attach a build output to a tagged release. It is one of the tools The Cloud MCP server gives every connected AI.
How do I use attachStudioAppArtifact from Claude or ChatGPT?
Connect your AI to The Cloud at https://mcp.thecloud.so/mcp and sign in once. Then ask Claude, ChatGPT, Cursor or any AI connected to The Cloud "attach the build", and it calls attachStudioAppArtifact.
Is attachStudioAppArtifact safe to let an AI call?
attachStudioAppArtifact changes your workspace. What an AI creates is Private until you share it.
Connect
One endpoint gives your AI this tool and every other one: connect Claude, ChatGPT, Cursor or Gemini, read what The Cloud is, or see pricing.