modelscope-studio

ModelScope Studio Deployment

Verified live against ModelScope OpenAPI ｜ modelscope 1.37.1 / modelscope_hub 0.1.2 (2026-06-29)

Deploy a local project to a ModelScope Studio. This Skill uses OpenAPI as the source of truth, with the ms CLI as an equivalent convenience alias, modelscope_hub.HubApi as the API-first Python client, and MCP tools as optional.

Quick Decision Guide

User wants to...
│
├── Deploy a local project to a Studio
│   └── Follow the 10 steps in "Full Deployment Workflow" below
│
├── Update an already-deployed Studio
│   └── Modify code → git push → POST /studios/{o}/{r}/deploy (or ms deploy)
│
├── View Studio status/logs
│   └── GET /studios/{o}/{r}/logs/run (or ms logs --log-type run)
│
├── Manage variables
│   ├── Plaintext variables: GET/POST/PUT/DELETE /studios/{o}/{r}/variables
│   └── Secrets: GET/POST/PUT/DELETE /studios/{o}/{r}/secrets (or ms secret ...)
│
└── Repository file management / model & dataset operations
    └── hand off → ms-hub

Prerequisites

1. MODELSCOPE_API_KEY

The entire workflow depends on this token (API authentication, Git push, variable/secret configuration); it must be confirmed first.

If the environment variable is empty but the git remote contains an address of the form https://oauth2:<token>@www.modelscope.cn/studios/... (or www.modelscope.ai/... for the international site), extract <token> from it as MODELSCOPE_API_KEY. If neither is available, guide the user:

1. Visit $MODELSCOPE_ENDPOINT/my/myaccesstoken to obtain a token
2. export MODELSCOPE_API_KEY=your_token

Site routing: this skill targets whichever site $MODELSCOPE_ENDPOINT points to (default domestic https://modelscope.cn; international https://www.modelscope.ai). Export MODELSCOPE_ENDPOINT plus a site-scoped token before deploying — the OpenAPI base and the git remote host below both derive from it. Full guidance: ms-hub → "Site selection & endpoint routing".

2. Runtime Environment

OpenAPI basic conventions:

3. Git Environment

Studio code is synced via Git; ensure Git is installed and user information is configured.

Operations Overview: OpenAPI (source of truth) ↔ CLI ↔ Python

HubApi is the same engine that drives the ms CLI and is the API-first Python entry point:

from modelscope_hub import HubApi
api = HubApi(); api.login("$MODELSCOPE_API_KEY")

Note it is a different pair of classes from the legacy modelscope.hub.api.HubApi: the legacy version has not yet wired up Studio methods such as deploy/stop, whereas the new modelscope_hub.HubApi has (its deploy_repo/stop_repo/get_repo_logs/secret series default to repo_type="studio").

MCP tools (optional) — the last column of the table above lists the equivalent tools provided by the studio-mcp service, with the same semantics as the OpenAPI call in the same row; when the agent has this service configured it can be called directly, and when it is not configured this column can be ignored. See the appendix at the end for first-time setup.

Full Deployment Workflow

Each step leads with OpenAPI and provides an equivalent one-line CLI command. ${owner}/${repo} are the Studio's owner and name.

Step 1: Check the local Git repository

[ -d .git ] && git remote -v 2>/dev/null | grep -E 'modelscope\.(cn|ai)/studios'

• Already has a Studio remote address → extract owner and repo from the URL, skip to Step 3
• None → continue to Step 2

Step 2: Analyze the project and get user info

2.1 Determine the SDK type

Selection advice: static does not support a build step and the files must already be built; use docker for frontend projects that need building; use docker when unsure.

The docker type requires first completing Alibaba Cloud account binding and passing real-name verification on the ModelScope platform: https://modelscope.cn/docs/studios/docker , otherwise the image cannot be built.

2.2 Get user info

curl "$MODELSCOPE_ENDPOINT/openapi/v1/users/me" -H "Authorization: Bearer $MODELSCOPE_API_KEY"
# Equivalent CLI: ms whoami

The repo is taken from the project directory name or specified by the user.

Step 3: Create or update the Studio

Before creating or changing settings, query the available options to avoid hardcoding outdated configuration:

curl "$MODELSCOPE_ENDPOINT/openapi/v1/studios/hardware?sdk_type=${sdk_type}" \
  -H "Authorization: Bearer $MODELSCOPE_API_KEY"
curl "$MODELSCOPE_ENDPOINT/openapi/v1/studios/sdk-versions?sdk_type=gradio" \
  -H "Authorization: Bearer $MODELSCOPE_API_KEY"
curl "$MODELSCOPE_ENDPOINT/openapi/v1/studios/base-images" \
  -H "Authorization: Bearer $MODELSCOPE_API_KEY"

For an existing Studio, you can append &studio=${owner}/${repo} to the hardware query so that free resources are returned according to that Studio's available quota. When selecting hardware, use the returned item's name; the paid resource format is paid/<InstanceType>. When selecting a Gradio sdk_version, use the returned item's version. When selecting base_image, use the returned item's name.

Paid-resource authorization requirement: If you intend to set hardware to paid/<InstanceType> or the returned item has resource_type=paid, you must first explicitly tell the user that this will incur charges on the Alibaba Cloud account bound to their ModelScope account, and only create, update settings, or redeploy after obtaining the user's explicit authorization. Without authorization, only free resources may be selected.

Check whether it already exists:

curl "$MODELSCOPE_ENDPOINT/openapi/v1/studios/${owner}/${repo}" -H "Authorization: Bearer $MODELSCOPE_API_KEY"
# Equivalent CLI: ms info ${owner}/${repo} --repo-type studio

Does not exist → create (before creating, proactively ask the user "public or private?", defaulting to private):

curl -X POST "$MODELSCOPE_ENDPOINT/openapi/v1/studios" \
  -H "Authorization: Bearer $MODELSCOPE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "owner": "'"${owner}"'",
    "repo_name": "'"${repo}"'",
    "sdk_type": "gradio",
    "visibility": "private",
    "hardware": "platform/2v-cpu-16g-mem",
    "display_name": "My App"
  }'
# Equivalent CLI: ms create ${owner}/${repo} --repo-type studio --sdk-type gradio --private

Already exists → update settings as needed:

curl -X PATCH "$MODELSCOPE_ENDPOINT/openapi/v1/studios/${owner}/${repo}/settings" \
  -H "Authorization: Bearer $MODELSCOPE_API_KEY" -H "Content-Type: application/json" \
  -d '{"sdk_type": "gradio", "sdk_version": "6.2.0", "base_image": "ubuntu22.04-py311-torch2.9.1-modelscope1.35.0"}'
# Equivalent CLI: ms settings ${owner}/${repo} --repo-type studio sdk_type=gradio sdk_version=6.2.0

Changes to sdk_type, sdk_version, base_image, and hardware require redeployment to take effect. xGPU requires an application (https://modelscope.cn/docs/studios/xGPU).

Step 4: Handle sensitive information

Before pushing code, scan files for hardcoded sensitive information (API keys, tokens, passwords, etc.) and change them to read from environment variables instead:

# ❌ WRONG
api_key = "sk-xxxxxxxxxxxx"
# ✅ CORRECT
import os
api_key = os.environ.get("API_KEY")

Compile a list of variables for use in Step 6: put non-sensitive configuration in plaintext variables, and sensitive information such as API keys, tokens, and passwords in secrets.

Step 5: Sync code to the Studio ⚠️ The only non-API step

Code sync is done via Git; there is no corresponding OpenAPI/CLI endpoint. The default branch is master; force push is prohibited.

# 1. Configure the remote repository (skip init if .git exists, skip add if the modelscope remote exists)
[ -d .git ] || git init
git remote remove modelscope 2>/dev/null || true
MS_HOST="${MODELSCOPE_ENDPOINT:-https://modelscope.cn}"; MS_HOST="${MS_HOST#https://}"   # endpoint host (defaults to modelscope.cn)
git remote add modelscope https://oauth2:${MODELSCOPE_API_KEY}@${MS_HOST}/studios/${owner}/${repo}.git
 
# 2. Large file handling (files over 100MB must use LFS)
git lfs install
 
# 3. Fetch the remote and merge
git fetch modelscope master
git merge modelscope/master --allow-unrelated-histories -m "Merge remote"

On merge conflicts, keep the local version:

git checkout --ours . && git add . && git commit -m "Resolve conflicts, keep local version"

Commit and push:

git add . && git commit -m "Deploy to ModelScope Studio"
git push -u modelscope master

Step 6: Configure plaintext variables/secrets

Configure based on the list from Step 4 (API-first). Plaintext variables return both key and value and are only for non-sensitive configuration:

# List plaintext variables
curl "$MODELSCOPE_ENDPOINT/openapi/v1/studios/${owner}/${repo}/variables" \
  -H "Authorization: Bearer $MODELSCOPE_API_KEY"
# Add
curl -X POST "$MODELSCOPE_ENDPOINT/openapi/v1/studios/${owner}/${repo}/variables" \
  -H "Authorization: Bearer $MODELSCOPE_API_KEY" -H "Content-Type: application/json" \
  -d '{"key": "GRADIO_TEMP_DIR", "value": "/tmp/gradio"}'
# Update
curl -X PUT "$MODELSCOPE_ENDPOINT/openapi/v1/studios/${owner}/${repo}/variables" \
  -H "Authorization: Bearer $MODELSCOPE_API_KEY" -H "Content-Type: application/json" \
  -d '{"key": "GRADIO_TEMP_DIR", "value": "/mnt/workspace/tmp"}'
# Delete
curl -X DELETE "$MODELSCOPE_ENDPOINT/openapi/v1/studios/${owner}/${repo}/variables" \
  -H "Authorization: Bearer $MODELSCOPE_API_KEY" -H "Content-Type: application/json" \
  -d '{"key": "GRADIO_TEMP_DIR"}'

Secrets do not return the value and are used for sensitive information such as API keys, tokens, and passwords:

# List secrets (returns key only)
curl "$MODELSCOPE_ENDPOINT/openapi/v1/studios/${owner}/${repo}/secrets" \
  -H "Authorization: Bearer $MODELSCOPE_API_KEY"
# Add
curl -X POST "$MODELSCOPE_ENDPOINT/openapi/v1/studios/${owner}/${repo}/secrets" \
  -H "Authorization: Bearer $MODELSCOPE_API_KEY" -H "Content-Type: application/json" \
  -d '{"key": "API_KEY", "value": "sk-xxx"}'
# Update
curl -X PUT "$MODELSCOPE_ENDPOINT/openapi/v1/studios/${owner}/${repo}/secrets" \
  -H "Authorization: Bearer $MODELSCOPE_API_KEY" -H "Content-Type: application/json" \
  -d '{"key": "API_KEY", "value": "new-value"}'
# Delete
curl -X DELETE "$MODELSCOPE_ENDPOINT/openapi/v1/studios/${owner}/${repo}/secrets" \
  -H "Authorization: Bearer $MODELSCOPE_API_KEY" -H "Content-Type: application/json" \
  -d '{"key": "API_KEY"}'
# Equivalent CLI (secrets only): ms secret {list,add,update,delete} ${owner}/${repo}

⚠️ To delete a plaintext variable or a secret, use DELETE .../variables or DELETE .../secrets and pass {"key":"..."} in the body, not the DELETE .../{key} path form.

Step 7: Deploy the Studio

curl -X POST "$MODELSCOPE_ENDPOINT/openapi/v1/studios/${owner}/${repo}/deploy" \
  -H "Authorization: Bearer $MODELSCOPE_API_KEY"
# Equivalent CLI: ms deploy ${owner}/${repo} --repo-type studio

Step 8: Monitor status and logs

# Run logs
curl "$MODELSCOPE_ENDPOINT/openapi/v1/studios/${owner}/${repo}/logs/run" -H "Authorization: Bearer $MODELSCOPE_API_KEY"
# Build logs (Docker type)
curl "$MODELSCOPE_ENDPOINT/openapi/v1/studios/${owner}/${repo}/logs/build" -H "Authorization: Bearer $MODELSCOPE_API_KEY"
# Equivalent CLI: ms logs ${owner}/${repo} --log-type run|build

View logs by SDK type:

• docker: check build first, then check run after the build completes
• Other types: check run directly

Keep alternating between them until Running or an error is found.

Step 9: Automatic diagnosis and repair

Common errors:

Docker-specific errors:

Repair flow: analyze logs → modify code → git push → POST .../deploy (or ms deploy) → check logs again

Step 10: Complete the deployment

Provide the Studio URL: $MODELSCOPE_ENDPOINT/studios/${owner}/${repo}

If the Studio is private, prompt the user: "Deployment succeeded and it is currently private. Would you like to make it public?" After confirmation, PATCH .../settings with {"visibility": "public"} (or ms settings ${owner}/${repo} --repo-type studio private=false).

Docker Studio Reference

For applications that go beyond the scope of Gradio/Streamlit, such as FastAPI, Golang, and Node.js. Prerequisite: you must complete Alibaba Cloud account binding and pass real-name verification on the ModelScope platform; see https://modelscope.cn/docs/studios/docker for details. See references/docker-templates.md for details.

Key requirements:

• The port must expose 0.0.0.0:7860; using 8080 is prohibited (occupied by the platform)
• HTTP headers must not use Authorization, X-modelscope-*, or X-studio-*

Data Persistence

• By default, data is lost on every restart
• Persistence directory: /mnt/workspace
• Data is still lost when transferring/renaming a Studio
• For high-reliability needs, use external storage (OSS, databases)

Notes

1. The default branch is master; force push is prohibited
2. Files over 100MB must use Git LFS
3. The first Docker build takes about 3-5 minutes; other types start faster
4. Free quotas have time limits
5. Switching to paid hardware resources will incur charges on the Alibaba Cloud account bound to the user's ModelScope account; the user's explicit authorization must be obtained first
6. Hardcoding sensitive information in code is prohibited; it must be injected via secrets; non-sensitive configuration may use plaintext variables
7. A Studio cannot be deleted through a programmatic interface: OpenAPI DELETE /openapi/v1/studios/{id} returns 404; the SDK/CLI delete_repo is deprecated and does not support studio. Deletion is only possible via the web console at https://modelscope.cn (which uses a cookie-authenticated internal interface; a Bearer token call returns 401). Programmatically, you can only stop (stop).

Reference Documentation

Consult when you run into problems or need more detail:

• references/openapi-studio-endpoints.md — detailed Studios OpenAPI endpoint parameters (source-of-truth specification)
• references/docker-templates.md — Dockerfile templates for the Docker type (FastAPI, Node.js, Golang, etc.)
• references/troubleshooting.md — deployment-failure troubleshooting process, common errors, and fixes

curl -s "$MODELSCOPE_ENDPOINT/openapi/v1/mcp/servers/maasadmin/studio-mcp?get_operational_url=true" \
  -H "Authorization: Bearer ${MODELSCOPE_API_KEY}"

ms mcp deploy maasadmin/studio-mcp --transport-type streamable_http

{
  "mcpServers": {
    "modelscope-studio": {
      "type": "streamable_http",
      "url": "<deployment URL>",
      "name": "modelscope-studio"
    }
  }
}

Related Skills

• Hub repository management / models & datasets / MCP / skill management → ms-hub**