LEM Bridge

lem bridge the lem bridge tools let you reach a specific edge through a litmus edge manager tenant, without switching the mcp server's active edge instance tool description lem bridge list devicehub devices list devicehub devices on a specific edge by tunneling through lem lem bridge get le info identity info (friendly name, cloud activation) for an edge via the lem bridge when to use which cross fleet inspection you have a lem tenant with many edges, and you want to inspect one of them without changing the active edge url / edge api client id / edge api client secret your mcp server is configured for fleet automation loop over devices returned by lem list devices , calling bridge tools per device bridge tools do not mutate the mcp server's active instance, so they're safe to run concurrently with normal tool calls required arguments every bridge tool takes project id lem project id device id lem device id (target edge) requirements edge manager url , edge api token see lem # for the full set validate certificate=true if the lem tenant uses a publicly verifiable cert and you want strict tls related litmus edge manager (lem) # fleet wide lem operations multi instance edge # alternative pattern when you control a small, named set of edges directly