MQTT.Agent

SDK

Reference implementations of MQTT.Agent v0.1, in TypeScript / Node. MIT licensed. Compatible with any conforming MQTT 5 broker.

The SDKs are one set of reference implementations. The specification does not require their use; it just defines the wire format they implement.

Packages

PackageLayerVersion
@cloudsignal/agentA2A over MQTTv0.1.x
@cloudsignal/mcp-over-mqttMCP over MQTTv0.1.x
@cloudsignal/mqtt-clientunderlying MQTT 5 clientv2.2.x

Install

npm install @cloudsignal/agent @cloudsignal/mcp-over-mqtt

The MQTT 5 client is a transitive dependency. Install it directly only if you need low-level access.

Examples

The home page walks two complete deployments end to end:

  • Standalone with Mosquitto: planned standalone experience using a local broker with no account. Requires a future SDK release adding vanilla-MQTT auth; see the home-page callout.
  • With a claim-enforcing broker: broker that enforces identity-bound ACL at the wire level (working today). CloudSignal MQTT is one such implementation.

Working code for both will live alongside the SDKs in the forthcoming public spec repository. Until it lands, the Run MQTT.Agent on a local Mosquitto broker guide walks through the standalone variant end to end.

Roadmap

  • v0.1.x (current). Tracks spec v0.1. Node-only.
  • v0.2.0 (planned). Identity-bound ACL profile support, claim refresh on long-lived sessions, broker-list discovery.
  • Python parity. On the roadmap, no fixed date.
  • Multi-broker / regional failover. Out of scope until the spec covers it.

Pin to an exact spec and SDK version in production. Breaking changes are possible during the v0.x window.

License

SDKs are MIT. Specification is CC-BY-4.0. The public spec repository carrying the full LICENSE files is being prepared.

Issues and contributions

  • Spec issues, PRs, RFC comments: a public spec repository is being prepared. Until it lands, write to efi@cloudsignal.io.
  • Adoption, partnership, broker integrations: efi@cloudsignal.io
Next
@cloudsignal/agent