Tools

tools reference the litmus mcp server exposes 57 tools across 11 categories tools accept structured json arguments and return json results categories category tools page devicehub, devices 4 devicehub devices # devicehub, tags 7 devicehub tags # device identity 2 device identity # cloud / lem activation 1 cloud activation # docker management 2 docker management # nats topics 2 nats topics # influxdb / time series 6 influxdb timeseries # system, events 2 system events # system, network 6 system network # digital twins 9 digital twins # litmus edge manager (lem) 14 litmus edge manager # lem bridge 2 lem bridge # marker conventions requires nats access (see headers reference # ) requires influxdb access open port 8086/tcp under system > network > firewall talks to a litmus edge manager tenant, not a litmus edge needs lem headers tool call contract every tool receives a request object containing the connection headers and returns list\[textcontent] with a json payload error responses use mcp's invalid params and internal error codes successful responses follow the shape produced by format success response() { "ok" true, "data" { " " " " } } errors { "ok" false, "error" { "code" " ", "message" " " } } header requirements at a glance header set required for edge url , edge api client id , edge api client secret almost all non system tools nats nats topic tools influx influxdb tools (and get device connection status ) edge manager url , edge api token , edge manager project id lem and lem bridge tools see headers reference # for the full list