Several tools exist because of how this data behaves rather than how the API is shaped. `get_all_tags_status` defaults to showing only non-OK tags, because a plant has thousands and you want the broken ones. `get_device_connection_status` distinguishes stale from no_data, which is the difference between a dead sensor and a dead gateway. And `get_device_data_for_inference` bundles metadata, per-tag statistics and recent samples in a single payload so a model can reason about a machine without ten round trips.
Litmus Automation's official server for Litmus Edge. It covers device configuration, tag management, live and historical data, digital twins, Docker deployment on the edge, and the network and system layer around them.
- 62 tools across 13 categories, taking structured arguments and returning JSON
- DeviceHub: `get_devicehub_devices`, `create_devicehub_device`, `get_litmusedge_driver_list` for the supported drivers such as ModbusTCP, OPCUA and BACnet, and `get_device_connection_status` for connected / stale / no_data
- Tags: `get_devicehub_device_tags` paginates with limit and offset, `create_devicehub_tag`, `update_devicehub_tag`, `delete_devicehub_tag`, `get_current_value_of_devicehub_tag`, and `get_all_tags_status` which defaults to non-OK so problems surface first
- Time series: `get_historical_data_from_influxdb`, `list_influxdb_measurements`, `query_tag_data`, `get_tag_statistics` for mean, min, max, stddev and count with a baseline range, and `get_device_data_for_inference` which packs metadata, tags, stats and recent samples into one payload
- NATS topics: `list_nats_topics`, `get_current_value_from_topic`, `get_multiple_values_from_topic` for trend analysis
- Network and system: `get_firewall_rules`, `get_network_interface_info`, `start_packet_capture`, `stop_packet_capture`, `get_packet_capture_status`, `get_system_events`, `get_system_event_stats`
- Digital twins and Docker: `list_digital_twin_models`, `create_digital_twin_model`, `get_all_containers_on_litmusedge`, `run_docker_container_on_litmusedge`
Docker: `docker run -d --name litmus-mcp-server -p 8000:8000 ghcr.io/litmusautomation/litmus-mcp-server:latest`. The image is built for linux/amd64, so on ARM64 pass `--platform linux/amd64`. Port 8000 serves both transports — `/mcp` for Streamable HTTP and `/sse` for older clients. HTTPS is available through a TLS-terminating reverse proxy or native TLS with your own certificate. A stdio path exists for Claude Desktop, installed from a clone with uv.
One command plus a key — docker run -d --name litmus-mcp-server -p 8000:8000 ghcr.io/litmusautomation/litmus-mcp-server:latest, then supply credentials