jochen
78817c949e
The node's runtime launches a tools bundle as a process and speaks MCP over stdio to it, so a tool may be written in any language and the transport stays in the runtime (ADR 0039's refusal, kept). Each SDK is the loop and the tool type and nothing else: `@novox/mesh-sdk/stdio` (serveStdio, and serveRegisteredOverStdio for a bundle that already registers the in-process way), python/, go/, rust/ and c/ beside it, each with an example answering `greet` and the seat verb `node-lamp.on`. Skeletons, by the operator's direction: the bare minimum one bundle per language needs to be built and answer, proven here by each example answering tools/list and tools/call on stdio.
10 lines
253 B
TOML
10 lines
253 B
TOML
[project]
|
|
name = "novox-mesh-sdk"
|
|
version = "0.1.0"
|
|
description = "The Novox Mesh SDK for Python: a tools bundle over stdio (novox/hq ADR 0187)"
|
|
requires-python = ">=3.9"
|
|
|
|
[build-system]
|
|
requires = ["setuptools"]
|
|
build-backend = "setuptools.build_meta"
|