Skip to main content

pyrunir-mcp

pyrunir-mcp is a typed Python API for planning-and-learning agents. Callers keep domains, tasks, candidates, validation results, and history in memory; filesystem artifacts are written only at the dump boundary.

See docs/api.md for the API and docs/index.md for workflow/output tables.

Basic Flow

from pyrunir_mcp import (
    ValidationHistory,
    create_domain_context,
    create_policy,
    create_task_context,
    dump_result,
    find_solution,
    generate_tasks,
)

domain = create_domain_context("domain.pddl")
task = create_task_context(domain, "problem.pddl")
policy = create_policy(domain, "policy.txt")
history = ValidationHistory()

result = find_solution(task, policy)
feedback = history.fold(result.observation)
dump_result(result, "artifacts/find-solution")

Entry Points

Context/candidates:

  • create_domain_context(domain_file)
  • create_task_context(domain_context, problem_file, num_threads=1)
  • create_policy(domain_context, policy_file); pass None for an empty policy
  • write_empty_policy(domain_context, policy_file) for canonical empty policy text
  • create_module_program(domain_context, module_program_file); pass None for the built-in empty module program
  • create_classifier(domain_context, classifier_file); pass None for an empty classifier

runir.task_generation:

  • describe_generator(domain_name)
  • get_generator_path(domain_name) / get_generator_domain_path(domain_name)
  • generate_tasks(domain_name, output_dir, batch_name, configs, allow_invalid=False)

Validation:

  • find_solution(task_context, policy_or_module_program, classifier=None, universal=False, ...)
  • prove_termination(domain_context, policy_or_module_program, ...)
  • prove_classifier(task_context, classifier, ...)

Dumping:

  • dump_result(result, output_dir, formats=(DumpFormat.JSON,), include_witness=True, include_witness_trace=True, include_plan_trace=True, include_successors=True)
  • dump_validation_history(history, output_dir, formats=(DumpFormat.JSON,))

DumpFormat.PSV, DumpFormat.MD, and DumpFormat.JSON request LLM-readable PSV, human-readable Markdown, and machine-readable JSON. Validation calls do not write files.

Release files for pyrunir-mcp 0.0.34

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pyrunir-mcp 0.0.34
File Size Uploaded
pyrunir_mcp-0.0.34.tar.gz 92.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for pyrunir-mcp 0.0.34
File Interpreter ABI Platform
pyrunir_mcp-0.0.34-py3-none-any.whl Python 3 none any Details

Total release size: 161.2 kB

Release files / pyrunir_mcp-0.0.34.tar.gz

Download URL pyrunir_mcp-0.0.34.tar.gz
Size 92.4 kB
Tags Source
SHA-256 checksum
How to use checksums
4dacd84a16bf0fd118bfef4858730ab29a6bd793d03785d0de191c9547e7c19b
BLAKE2b-256 checksum
How to use checksums
c07128ebcd4c4a529379917e893c8f1ddc43c3e0092e2cf8800d5a62147c0d7f
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 log

Release files / pyrunir_mcp-0.0.34-py3-none-any.whl

Download URL pyrunir_mcp-0.0.34-py3-none-any.whl
Size 68.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f5cb7ca6fef3b7c9cac24ff347e6a9b61039c763466c55accea8767fda3f4d59
BLAKE2b-256 checksum
How to use checksums
0f029e64aec4a40d1a420d8e12bfd2ddde607edda680f5b0c33b0620b4c341d0
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 log

Release history Release notifications | RSS feed

This release

0.0.34 This release

2 release files

0.0.33

2 release files

0.0.31

2 release files

0.0.30

2 release files

0.0.29

2 release files

0.0.28

2 release files

0.0.27

2 release files

0.0.26

2 release files

0.0.25

2 release files

0.0.24

2 release files

0.0.23

2 release files

0.0.22

2 release files

0.0.21

2 release files

0.0.20

2 release files

0.0.19

2 release files

0.0.18

2 release files

0.0.17

2 release files

0.0.16

2 release files

0.0.15

2 release files

0.0.14

2 release files

0.0.13

2 release files

0.0.12

2 release files

0.0.11

2 release files

0.0.10

2 release files

0.0.9

2 release files

0.0.8

2 release files

0.0.7

2 release files

0.0.6

2 release files

0.0.5

2 release files

0.0.4

2 release files

0.0.3

2 release files

0.0.2

2 release files

0.0.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page