Tools

5 min

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.