mthds
The Python implementation of the MTHDS Protocol — a typed client for any MTHDS runner, plus the base structures that methods are defined in.
Learn more at mthds.ai and browse the Hub at mthds.sh.
Looking for the command line? The
mthdsCLI ships as the npm package (mthds-js). This Python package is a library — it has no CLI.
Installation
pip install mthds
What's in the box
- The protocol (
mthds.protocol) —MTHDSProtocol, the five-route interface every runner implements (execute,start,validate,models,version); the wire models (RunResult,ModelDeck,ValidationReport,VersionInfo); the domain shapes methods are built from (concept,stuff,working_memory,pipe_output,pipeline_inputs); and the catalog serialization of a stored method's source (method_files). - Runners (
mthds.runners) —MthdsAPIClient(mthds.runners.api.client), the HTTP client for any MTHDS-Protocol server plus the hosted run-lifecycle (polling) extension; andPipelexRunner(mthds.runners.pipelex.runner), which shells out to a locally installedpipelexCLI. - Package management (
mthds.package) — read, lock, and resolveMETHODS.tomlmanifests.
See docs/runners.md for the protocol + runners reference. See docs/inputs-template.md for the inputs-template projection. See docs/versioning.md for the MTHDS standard and protocol versions this package carries.
Quick start
Run a method against any MTHDS-Protocol server with the API runner, MthdsAPIClient:
import asyncio
from mthds.runners.api.client import MthdsAPIClient
async def main() -> None:
async with MthdsAPIClient() as client:
# Discovery handshake
version = await client.version()
print(version.protocol_version)
# Run a method and wait for the result — start → poll → result in one call
result = await client.start_and_wait(pipe_code="my_pipe", inputs={"topic": "owls"})
print(result.main_stuff)
asyncio.run(main())
execute runs synchronously; start returns immediately with a pipeline_run_id; start_and_wait does the whole async lifecycle in one call. validate, models, and version round out the protocol surface.
Need local execution instead of an API? PipelexRunner (mthds.runners.pipelex.runner) implements the same MTHDSProtocol by shelling out to an installed pipelex CLI — no API key.
Configuration
MthdsAPIClient() reads its config from ~/.mthds/config — the same file the mthds CLI (npm) reads and writes, so configuring either configures both. Environment variables take precedence:
| Variable | Description | Default |
|---|---|---|
MTHDS_API_KEY |
API authentication key | (empty) |
MTHDS_BASE_URL |
API base URL — any MTHDS Protocol server | http://localhost:8081 |
This client targets the open-source pipelex-api runner, so it defaults to a local instance (http://localhost:8081, pipelex-api's default port). Point MTHDS_BASE_URL at any other MTHDS-Protocol server to use it instead. You can also pass api_key / base_url straight to MthdsAPIClient(...).
To set the config from a terminal, use the npm CLI (mthds config set api-key …) or edit ~/.mthds/config directly.
Related packages
1 maintainer
Metadata
1 maintainer
Release files for mthds 0.18.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 | |
|---|---|---|---|
| mthds-0.18.0.tar.gz | 275.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mthds-0.18.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 387.3 kB
Release files / mthds-0.18.0.tar.gz
| Download URL | mthds-0.18.0.tar.gz |
|---|---|
| Size | 275.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
589dfde53672966030b454f099979f91dcc1bd67958585c46ed6c8f89bf0e08c
|
|
BLAKE2b-256 checksum How to use checksums |
48baa9b2a7902ccea184c4589f7c9eedeef66aa46a9bd1c8f099a7240669f833
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 3, 2026.
Transparency logRelease files / mthds-0.18.0-py3-none-any.whl
| Download URL | mthds-0.18.0-py3-none-any.whl |
|---|---|
| Size | 111.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a2778e43b943b9aa3d3ab4f0422d57a6dc1245abe4ce84435c821f26a4d3f599
|
|
BLAKE2b-256 checksum How to use checksums |
44b09868dba5ca03b23ba54b7636ebd194e8c16b2eb90a5631f8ad2cb19a5947
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 3, 2026.
Transparency log
