MettleDeck Python SDK
Python client for MettleDeck's local automation API. It connects to the desktop application over the loopback interface; it does not expose MettleDeck to the local network.
Installation
pip install mettledeck
MettleDeck must be installed on the same computer. Enable Local automation API under Settings > General > Application. The first connection may ask for approval in the desktop application.
Quick start
from mettledeck import Client, Workspace
with Client.connect() as client:
task = client.create(title="New task", workspace=Workspace.KANBAN)
client.move(task.id, workspace=Workspace.PLANNING, planning_lane=2)
Client.connect() discovers a running application or starts the installed
application. The SDK and application negotiate the newest API version they both
support.
Task operations
| Method | Action |
|---|---|
list_projects() |
List available projects |
project() |
Read columns, tags, and the current revision |
list() |
List tasks, optionally filtered by workspace, column, lane, or tag |
get() |
Read one task, with optional history |
create() |
Create a task, with optional media and attachments |
update() |
Change supplied task fields and leave omitted fields alone |
move() |
Move or reorder a task |
watch_tasks() |
Poll for task snapshots when the project revision changes |
Projects, columns, and tags are read-only in API v1. There is no task or project
deletion endpoint. update() can clear nullable task fields and can remove media
or attachments when those options are supplied explicitly.
All returned models are frozen dataclasses. Unknown response fields are ignored so an older SDK can continue to work with compatible additions to API v1.
Examples
The examples directory contains six small scripts:
create_task.pyupdate_task.pymove_task.pylist_tasks.pyadd_media_and_attachments.pywatch_tasks.py
python -m pip install -e .
python examples/create_task.py
Development
python -m pip install -e ".[dev]"
python -m ruff check .
python -m pytest
python scripts/check_openapi.py
python -m build
python -m twine check dist/*
The API description is in openapi/mettledeck-v1.json.
License
MIT
Copyright 2026 Quantum Oblique.
Release files for mettledeck 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mettledeck-1.0.0.tar.gz | 15.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mettledeck-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 26.7 kB
Release files / mettledeck-1.0.0.tar.gz
| Download URL | mettledeck-1.0.0.tar.gz |
|---|---|
| Size | 15.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e45a84ce57e4109af84ecab6f852c859e16f42fe3352db52ac103e146d849288
|
|
BLAKE2b-256 checksum How to use checksums |
b5bc187afc3298608517819168a0e49027011afe5b4ae46007226ccd84264691
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 18, 2026.
Transparency logRelease files / mettledeck-1.0.0-py3-none-any.whl
| Download URL | mettledeck-1.0.0-py3-none-any.whl |
|---|---|
| Size | 11.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b225c8ca72b700637b845bdb7ee24236ffcdb85c641ea0b69309f9953419aa7f
|
|
BLAKE2b-256 checksum How to use checksums |
2127cae8731525250f441df96bbe24a190ce4e0d3ce9100b742717f51939c829
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 18, 2026.
Transparency log