Expand description
Internals of the mcpmesh binary. Not a supported SDK — no stability promise is
made for anything in this crate; modules are pub only so the binary’s integration
tests and the embedding shell can link them, and they may change or vanish in any
release without a major version bump.
Building on mcpmesh? Depend on mcpmesh-local-api
instead — that crate is the supported integration surface.
Modules§
- json
- Every value the porcelain prints under
--json— the machine face, as pure unit-tested builders. [crate::render] owns the human strings; this module owns the JSON mirror. Shapes serialize the mcpmesh-local/1 result types verbatim wherever one exists (additive discipline: an absent field means empty/none, same as the wire), plus small hand-built objects for verbs with no API result. One JSON value per invocation on stdout; a failure is one{"error":{"code":…,"message":…}}line on stderr.