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.
9 lines
203 B
Makefile
9 lines
203 B
Makefile
CFLAGS ?= -O2 -Wall -Wextra
|
|
JANSSON := $(shell pkg-config --cflags --libs jansson)
|
|
|
|
example: example.c mesh_sdk.c mesh_sdk.h
|
|
$(CC) $(CFLAGS) -o $@ example.c mesh_sdk.c $(JANSSON)
|
|
|
|
clean:
|
|
rm -f example
|