pytyr-mcp
pytyr-mcp is a typed Python API for planning-and-learning agents. Callers keep parsed domains, task contexts, and search results in memory; filesystem artifacts are written only at the dump boundary.
Current release: 0.0.12.
See docs/api.md for the API and docs/index.md for workflow/output docs.
Basic Flow
from pytyr_mcp import (
DumpFormat,
SearchBudget,
create_domain_context,
create_task_context,
find_satisficing_plan,
)
domain = create_domain_context("domain.pddl")
task = create_task_context(domain, "problem.pddl")
result = find_satisficing_plan(task, search_budget=SearchBudget(100_000, 5.0))
dump = result.dump("artifacts/find-plan", formats=(DumpFormat.JSON,), include_plan_text=True)
Entry Points
Context:
create_domain_context(domain_file)create_task_context(domain_context, problem_file, num_threads=1)
Planning:
find_satisficing_plan(task_context, search_budget=PROVE_SEARCH_BUDGET)
Dumping:
result.dump(...)
Planning calls return typed result objects and do not write files.
Metadata
Release files for pytyr-mcp 0.0.12
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 | Actions |
|---|---|---|---|---|
| pytyr_mcp-0.0.12.tar.gz | 11.3 kB | With provenance | Details for pytyr_mcp-0.0.12.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pytyr_mcp-0.0.12-py3-none-any.whl | Python 3 | none | any | Details for pytyr_mcp-0.0.12-py3-none-any.whl |
Total release size: 20.5 kB
Release files / pytyr_mcp-0.0.12.tar.gz
| Download URL | pytyr_mcp-0.0.12.tar.gz |
|---|---|
| Size | 11.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c5c038076e1bcfe6154bc222489644771988b58346649a9ecb7a563d4f64caae
|
|
BLAKE2b-256 checksum How to use checksums |
dc55e702a37a115fe075d9a135a1fa5e4ea719c0821cb4ec34b8bf06bd06d562
|
| 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 Aug 23, 2026.
Transparency logRelease files / pytyr_mcp-0.0.12-py3-none-any.whl
| Download URL | pytyr_mcp-0.0.12-py3-none-any.whl |
|---|---|
| Size | 9.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1c6b229f28a24861f763e9e2397a7b82faab9213f02caa7c124614f41231e2b1
|
|
BLAKE2b-256 checksum How to use checksums |
977ae1b84e3ad39d230aac37536d2987734706949f5166c0a1cc62e78f783c86
|
| 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 Aug 23, 2026.
Transparency logSecurity for pytyr-mcp 0.0.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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for pytyr_mcp-0.0.12.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 Aug 23, 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.