jschoubben 80b02740ab The console: mesh serve on loopback, and every runtime answers tools ...

The runtime serves a tools verb per module with names, descriptions and schemas (design 34 §3), and
refuses a module naming its own tool tools. Discovery asks catalog_modules then each module, naming
what did not answer. One MCP handler over two transports: stdio (mesh mcp) and loopback HTTP (mesh
serve, the mesh-console module, novox/hq ADR 0152); serve refuses any bind but loopback. tools/call
may go through a running console with --console and no credential.

2026-09-30 16:19:22 +02:00

..

fixtures

The console: mesh serve on loopback, and every runtime answers tools

2026-09-30 16:19:22 +02:00

client.test.ts

The console: mesh serve on loopback, and every runtime answers tools

2026-09-30 16:19:22 +02:00

conformance.mjs

Hold the runtime's NATS client to the shared fixtures

2026-09-26 23:40:59 +02:00

http.test.ts

The console: mesh serve on loopback, and every runtime answers tools

2026-09-30 16:19:22 +02:00

mcp.test.ts

The console: mesh serve on loopback, and every runtime answers tools

2026-09-30 16:19:22 +02:00

patient-connect.test.ts

One consumer, one reader, however many patterns a module registers

2026-09-28 16:25:42 +02:00

roundtrip.mjs

The tool runtime's client on NATS, behind the unchanged contract

2026-09-26 23:29:17 +02:00

runtime-tools.test.ts

The console: mesh serve on loopback, and every runtime answers tools

2026-09-30 16:19:22 +02:00