---
title: LEM Bridge
slug: litmus-mcp-server/lem-bridge
docTags: 
createdAt: 2026-05-11T21:48:40.065Z
---

# 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.