tenaxisos-sdk
Python SDK and CLI for building, testing, signing, and publishing TenaxisOS packages — agents, MCP servers, and playbooks that install into a TenaxisOS kernel and can be shared through the Tenaxis Hub.
What this is
tenaxisos-sdk is the toolkit for building community capabilities for
TenaxisOS:
- Author agents and MCP servers as plain Python, using
AgentandMCPServerbase classes with host-brokered LLM/tool/file access — no network calls, secrets, or infrastructure of your own to manage. - Test locally against
LocalMockHost, a fake host that lets you drive and assert on agent/tool behavior entirely offline. - Build a signed, versioned package manifest from your code.
- Publish to the Tenaxis Hub (or import straight into a kernel you control for local development) so others can discover and install it.
Getting started
The fastest way in is
examples/ — three runnable,
heavily-commented examples, one per authoring surface (native agent, MCP
server, LangChain framework adapter). Each has its own tests you can run
immediately, no kernel or network required:
pip install -e ".[dev,mcp,langchain]"
pytest examples/minimal_text_agent/test_agent.py -v
See
examples/README.md
for which one to start with.
Documentation
Prose tutorials — go here once you know which capability you're building and want more depth than the examples give:
- Writing a native agent
- Writing an MCP server
- Local testing with
LocalMockHost - Publishing and installing
- Runtime permission outcomes
What this contains
| Directory | Purpose |
|---|---|
src/tenaxisos_sdk/core/ |
Manifest validation, JSON Schema loading, Ed25519 signing/verification |
src/tenaxisos_sdk/agents/ |
Agent/RunContext/Finding authoring surface, manifest generation |
src/tenaxisos_sdk/host/ |
The host-brokered contract (Host protocol, ToolOutcome) every agent runs against |
src/tenaxisos_sdk/testing/ |
LocalMockHost — no-kernel local test host |
src/tenaxisos_sdk/tools/ |
Tool/MCPServer authoring surface, MCP manifest generation, [mcp] extra for the real stdio protocol bridge |
src/tenaxisos_sdk/cli/ |
The tenaxis CLI: validate, build, sign, verify, test, publish, import, keygen, run, agent build, mcp init/test/build, workflow import |
src/tenaxisos_sdk/runtime/adapters/ |
Agent framework adapters (LangChain today, [langchain] optional extra) |
src/tenaxisos_sdk/importers/ |
External-workflow importers (n8n today) used by tenaxis workflow import |
tenaxisos-sdk is published on PyPI:
https://pypi.org/project/tenaxisos-sdk/. Version 0.3.0 is the current
package release; 0.2.0 remains the SDK API contract version.
Prerequisites
- Python 3.11 or 3.12.
- No database, no server, no
.envfile — the CLI is stateless and takes everything (hub URL, API keys, key paths) as command-line flags.
Installation
python3 -m venv .venv && source .venv/bin/activate # optional but recommended
pip install tenaxisos-sdk
tenaxis --help
Install optional extras only when needed:
pip install "tenaxisos-sdk[langchain]" # LangChain agent adapter
pip install "tenaxisos-sdk[mcp]" # run MCP servers as real stdio processes
For local development against this checkout, use an editable install:
pip install -e ".[dev,mcp,langchain]"
The optional extras are kept separate so the base SDK never requires heavy adapter-specific dependencies.
Everyday usage
tenaxis keygen # once — generates an Ed25519 signing key pair
tenaxis validate <manifest.json> # schema + structural validation
tenaxis test <manifest.json> # runs the package's declared tests
tenaxis build <manifest-dir> --out <out.package.json> # produces a distributable package artifact
tenaxis sign <manifest.json> --key <private-key-path> # signing ceremony (human-reviewed, not run in CI)
tenaxis verify <manifest.json> --pubkey <public-key-b64> [--require]
tenaxis publish <manifest.json> --hub <hub-url> --api-key <publisher-api-key>
tenaxis import <n8n-export.json> --out <package-dir> # n8n → native workflow package
tenaxis keygen writes your private signing key to disk (permissions locked
to owner-only) — keep it out of version control and treat it like any other
private key material; the CLI never transmits or stores it for you.
Tests
pip install -e ".[dev]"
pytest tests/ -v
ruff check src/ tests/
License
MIT — see LICENSE.
Metadata
Release files for tenaxisos-sdk 0.3.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 | |
|---|---|---|---|
| tenaxisos_sdk-0.3.0.tar.gz | 113.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tenaxisos_sdk-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 211.0 kB
Release files / tenaxisos_sdk-0.3.0.tar.gz
| Download URL | tenaxisos_sdk-0.3.0.tar.gz |
|---|---|
| Size | 113.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a3565714acec4e8a44e03e0564bb4a168be171cd1b4de86fb5850d05c8f34401
|
|
BLAKE2b-256 checksum How to use checksums |
c048036ac81ba6fad27e53e685b53a5499a3eace158009e1b9187fb6ec15bdb9
|
| 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 14, 2026.
Transparency logRelease files / tenaxisos_sdk-0.3.0-py3-none-any.whl
| Download URL | tenaxisos_sdk-0.3.0-py3-none-any.whl |
|---|---|
| Size | 97.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2134d3933180594db9b50ea7692d3c970556563acfc516624975d48f213d416f
|
|
BLAKE2b-256 checksum How to use checksums |
f61576605c96925c4080273bf31a41c44af506d01ebecc617fc71bc5b797bb3f
|
| 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 14, 2026.
Transparency log