mpak Python SDK
Python SDK for the mpak registry - search, download, and resolve MCPB bundles and Agent Skills.
Installation
pip install mpak
Quick Start
from mpak import MpakClient
# Create client
client = MpakClient()
# Resolve a bundle to download URL
download = client.get_bundle_download("@nimblebraininc/echo", version="latest")
print(f"Download URL: {download.url}")
print(f"SHA256: {download.sha256}")
# Download and extract a bundle
manifest = client.load_bundle("@nimblebraininc/echo", dest="/app/bundle")
print(f"Loaded: {manifest['name']} v{manifest['version']}")
CLI Usage
The package provides a mpak-loader CLI that replaces the standalone mcpb-loader.py script:
# Load from mpak registry
mpak-loader @nimblebraininc/echo /dest/dir
# Load specific version
mpak-loader @nimblebraininc/echo@1.0.0 /dest/dir
# Load from direct URL with SHA256 verification
mpak-loader https://example.com/bundle.mcpb /dest/dir abc123...
Development
Setup
# Install with dev dependencies
uv pip install -e ".[dev]"
# Generate types from OpenAPI spec
python scripts/generate-types.py
Testing
# Run tests
pytest
# Run with coverage
pytest --cov=mpak --cov-report=html
# Lint and format
ruff check .
ruff format .
Verification
Run all checks before submitting changes:
uv run ruff check src/ tests/ # lint
uv run ruff format --check src/ tests/ # format
uv run ty check src/ # type check
uv run pytest -m "not integration" # unit tests
uv run pytest -m integration # integration tests (hits live registry)
CI runs lint, format, type check, and unit tests on every PR via sdk-python-ci.yml.
Releasing
Releases are automated via GitHub Actions and PyPI trusted publishing (OIDC). No API tokens required.
Version is defined in one place: pyproject.toml. The runtime version (mpak.__version__) and User-Agent are derived automatically via importlib.metadata.
Steps
-
Bump version in
pyproject.toml:# Edit pyproject.toml version field, or use hatch: hatch version patch # 0.1.0 → 0.1.1 hatch version minor # 0.1.0 → 0.2.0 hatch version major # 0.1.0 → 1.0.0
-
Commit and push:
git commit -am "sdk-python: bump to X.Y.Z" git push
-
Tag and push (this triggers the publish):
git tag sdk-python-vX.Y.Z git push origin sdk-python-vX.Y.Z
CI will run the full verification suite, verify the tag matches pyproject.toml, build, and publish to PyPI. See sdk-python-publish.yml.
Type Generation
The SDK types are generated from the mpak registry OpenAPI spec. To regenerate:
python scripts/generate-types.py
This fetches the latest spec from https://registry.mpak.dev/docs/json and generates Pydantic models in src/mpak/generated/types.py.
License
Apache-2.0
Metadata
Release files for mpak 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mpak-0.1.1.tar.gz | 54.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mpak-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 66.2 kB
Release files / mpak-0.1.1.tar.gz
| Download URL | mpak-0.1.1.tar.gz |
|---|---|
| Size | 54.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
586669f130961c478e8cc0e340cbbd6ecd30f5f0a35298f0607ed661113910a3
|
|
BLAKE2b-256 checksum How to use checksums |
e0132becea7727535afc5fdd72fac6c59826c038c125ab0d3e750cddfd3c46c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 19, 2026.
Transparency logRelease files / mpak-0.1.1-py3-none-any.whl
| Download URL | mpak-0.1.1-py3-none-any.whl |
|---|---|
| Size | 11.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d3d4eae1acd29c455f15f0401fd220025dc216b5c17995d9be9df64ade50b2dc
|
|
BLAKE2b-256 checksum How to use checksums |
c22c807f35edefad262c81c0f963d647f996a33812e0ff919fed247d2d1ad367
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 19, 2026.
Transparency logSecurity for mpak 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for mpak-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.