Hub Repositories#

MEGA Hub repositories provide one revisioned storage model for model, dataset, space, and mcp content. Every file mutation creates an immutable commit, while branches and tags provide readable revision names.

Use a repository for reviewable history and pinned releases. For mutable files that are synchronized in place, use a Storage Bucket instead; Buckets do not provide commits, branches, or tags. For large working trees, prefer the CLI or HTTP upload paths before cloning the entire repository locally.

Repository identity#

A repository ID has the form owner/name:

1mega/qwen-release2research/evaluation-corpus3alice/demo-space

Repository type is selected at creation and is one of model, dataset, space, or mcp. Visibility can be public or private.

Use the type-specific guides for recommended layouts and publication checks:

• Model Repositories
• Dataset Repositories
• Spaces
• MCP Marketplace
• Repository Cards

Clone and push with Git#

HTTPS works for public clone and bearer-backed credential helpers; SSH is the recommended interactive write transport after registering a public key:

Use git.tensorplay.cn directly for HTTPS Git and ssh.tensorplay.cn for SSH. Existing mega.tensorplay.cn Git remotes remain compatible through a streamed fallback, but new clones should use the dedicated Git data plane for performance.

1curl -sSfL https://mega.tensorplay.cn/git-xet/install.sh | sh2git clone https://git.tensorplay.cn/mega/qwen-release.git3git clone git@ssh.tensorplay.cn:mega/qwen-release4 5cd qwen-release6git add .7git commit -S -m "Publish signed release"8git push origin main

MEGA validates repository authorization and commit integrity before publishing a new revision. A rejected push does not partially advance the branch.

Create and inspect#

1mega repos create mega/qwen-release --type model --private2mega repos create mega/search-tools --type mcp --private3mega repos info mega/qwen-release4mega repos list --owner mega --type model

Typed command groups provide the common list, info, files, upload, and download workflows:

1mega models list2mega datasets list research/evals --revision main3mega spaces download alice/demo --local-dir ./space

Upload and download#

Upload one file or a directory:

1mega upload mega/qwen-release ./config.json config.json2mega upload mega/qwen-release ./model --revision main --commit-message "Publish model"

For large directories, use the resumable uploader:

mega upload-large-folder mega/qwen-release ./model --revision main

Both upload commands use the Hugging Face-compatible commit workflow. Use the resumable uploader for large release trees and the regular upload command for small, reviewable changes.

Download selected files or a complete snapshot:

1mega download mega/qwen-release config.json tokenizer.json --local-dir ./release2mega snapshot mega/qwen-release --revision main --local-dir ./release

Copy with MEGA URIs#

mega cp accepts local paths and typed Hub URIs:

1mega cp mega://models/mega/source@main/config.json ./config.json2mega cp ./README.md mega://models/mega/source@main/README.md

Use models, datasets, spaces, or mcps to make the repository type explicit:

mega cp ./README.md mega://mcps/mega/search-tools@main/README.md

Branches, tags, and history#

1mega repos branch list mega/qwen-release2mega repos branch create mega/qwen-release staging --revision main3mega repos tag create mega/qwen-release v1.0 --message "First release"4mega repos history mega/qwen-release --limit 205mega repos commit mega/qwen-release v1.0

History and commit output includes signature_status, signer_fingerprint, signer_subject, and author_email. Use JSON output for a release gate:

mega repos commit mega/qwen-release v1.0 --format json

Tags are immutable revision pointers until explicitly deleted. Use a branch for ongoing work and a tag for a release boundary.

Move, duplicate, and delete#

1mega repos move mega/old-name mega/new-name2mega repos duplicate mega/source research/copy --private3mega repos delete mega/obsolete

Moving can rename a repository or transfer it into an administered namespace. Duplicating copies repository history and metadata without transferring the underlying object bytes.

Discussions and pull requests#

Repository community operations use mega discussions:

1mega discussions list mega/qwen-release2mega discussions create mega/qwen-release --title "Release notes" --body-file ./RELEASE.md3mega discussions comment mega/qwen-release 3 --body "Verified on CUDA 13."

Fine-grained tokens need community:write for mutations. Repository discussions and pull requests share numbering, message history, attachments, reactions, and moderation boundaries.

See Discussions and Pull Requests for branch-backed proposals, diff review, fast-forward merge, and moderation commands.

Python SDK#

1from megatensors.hub import MegaHubClient2 3client = MegaHubClient()4repo = client.create_repo(5    "mega/qwen-release",6    repo_type="model",7    private=True,8    exist_ok=True,9)10 11client.upload_file(12    "mega/qwen-release",13    "./config.json",14    path_in_repo="config.json",15)16 17for file in client.list_files("mega/qwen-release", revision="main"):18    print(file.path, file.size, file.sha256)

Use the Python SDK for the typed method map and the live OpenAPI Explorer for direct HTTP integration.

Operational guidance#

• Pin deployments to a commit or tag instead of a mutable branch.
• Use --dry-run and include/exclude filters before large downloads.
• Keep repository type stable; create a separate repository when content semantics change.
• Prefer mega upload-large-folder for large release trees; see Xet for large-artifact guidance.
• MCP repositories support the same native Xet upload, deduplication, download, and maintenance paths as other repositories. Marketplace runtime CPU, memory, request, and package limits remain independent of repository storage.
• Require explicit confirmation for destructive branch, tag, file, and repository deletion.
• Keep discovery metadata short and use README.md for detailed release context.